DongHyeonkaandClaude Opus 5
b2963105a8
The keycloak project ended with four open questions that design could not
settle. A two-VM lab was built to answer them by measurement, and this is
that material: 26 experiments, 125 raw command outputs, 22 browser captures.
Follows the import procedure in README.md.
source/ the originating repository verbatim — 78 documents, 28 SVGs,
8 manifests, plus .source-revision recording the commit
final/ the SSOT
document.md 729 lines written from the 29 experiment documents, not
concatenated: what was predicted, what was measured, and
where the measurement itself was wrong
evidence/raw 125 outputs, flattened to <experiment>__<file> because
the originals collided (01-baseline.txt appeared three
times) and the audit only globs the top level
evidence/meta one per raw file; command and exitCode are null and the
README says why rather than inventing them
evidence/browser 22 captures
assets/ three diagrams through techviz
.techviz/ their VizSpecs
A separate project rather than an addition to keycloak: the B-layer answers
that project's four questions, but the A, C and D layers are about cluster
failure, SSO and operations, and one document.md should hold one subject.
The four question records there can point here through 관계.
Recorded rather than papered over: only three of the 28 diagrams were
remade. The repository forbids hand-drawn SVG and forbids titles inside the
canvas; all 28 originals carry both, so converting them is redrawing, not
reformatting. They stay in source/ and the gap is written into the document.
verify-pipeline.py passes. audit-records.py reports no issues.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
36 lines
1.4 KiB
Markdown
36 lines
1.4 KiB
Markdown
# Material production FULL_READ completion gate
|
|
|
|
- reopened at: `2026-08-31T23:30:00+09:00`
|
|
- affected leaves: **23**
|
|
- reason: behavior-bearing production implementation remained `STRUCTURAL_ONLY` or was explicitly recorded as not fully read.
|
|
- COMPLETE rule: behavior-bearing `src/main` implementation must be read and incorporated into the SSOT.
|
|
- `STRUCTURAL_ONLY` remains valid only for generated/declarative/non-semantic repetitive artifacts when the ledger records the reason.
|
|
- tests may be selectively read when the document explicitly states what was and was not inspected, but tests supporting a material claim must be read at the assertion/fixture path used by that claim.
|
|
- downstream order remains: all module SSOTs COMPLETE -> `99-cross-scope` -> `final/document.md` -> candidate ledger/source manifest -> Root Tree.
|
|
|
|
## Reopened leaves
|
|
|
|
- `messaging-kafka`
|
|
- `messaging-rabbit`
|
|
- `messaging-pulsar-experimental`
|
|
- `messaging-nats-experimental`
|
|
- `messaging-spring-boot-starter`
|
|
- `grpc-core-api`
|
|
- `grpc-proto-contract`
|
|
- `grpc-codegen`
|
|
- `grpc-policy`
|
|
- `grpc-server`
|
|
- `grpc-client`
|
|
- `grpc-discovery`
|
|
- `grpc-admin`
|
|
- `grpc-observability`
|
|
- `grpc-operation-ledger-jpa`
|
|
- `grpc-spring-boot-starter`
|
|
- `grpc-testkit`
|
|
- `grpc-advanced-bootstrap`
|
|
- `grpc-advanced-edition`
|
|
- `grpc-advanced-streaming`
|
|
- `grpc-advanced-resilience`
|
|
- `grpc-advanced-compat`
|
|
- `grpc-advanced-diagnostics`
|