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>
16 lines
1.6 KiB
Plaintext
16 lines
1.6 KiB
Plaintext
### 3.2 (8.2) 조건 형제 비교 — off 계약의 두 절반
|
|
|
|
| 절반 | 무엇을 막는가 | 검증 |
|
|
|---|---|---|
|
|
| `GraphQlRootAutoConfiguration`의 `@ConditionalOnProperty` | 이 leaf의 39개 빈 | `GraphQlShippedAndGatedTest.graphQlOffHoldsNothing` — 빈 인벤토리 |
|
|
| `GraphQlOffAutoConfigurationImportFilter` | 프레임워크가 발행하는 `/graphql` 라우트 | `GraphQlShippedAndGatedTest.graphQlOffPublishesNoEndpoint` — 실제 포트 |
|
|
|
|
두 번째 테스트가 특히 정교하다. 리터럴 404를 단언하지 않고, 매핑된 적 없는 경로의 상태 코드와 **같은지**를 본다 — 주석이 그 이유를 적는다: "Asserting a literal 404 would have been wrong: the security filter chain runs before ...". 그리고 그 테스트는 이 leaf가 아니라 app-bootstrap에 있다. off 계약은 출하 조립에서만 검증할 수 있으므로 옳은 위치다.
|
|
|
|
### 3.3 (8.3) 중복 메커니즘 — 마스터 스위치를 읽는 세 지점
|
|
|
|
`backend.graphql.enabled`를 읽는 곳이 셋이다: `GraphQlRootAutoConfiguration`의 `@ConditionalOnProperty`, `GraphQlOffAutoConfigurationImportFilter.match`, `GraphQlRetiredSafetyAxis.problems`. 셋 다 문자열 리터럴로 키를 갖는다.
|
|
|
|
같은 키를 세 곳이 문자열로 갖는 것은 드리프트 위험이지만, 세 지점이 서로 다른 생애주기(자동설정 조건 · import 필터 · 환경 후처리)에 있어 공유 상수를 두기 어렵다. 그리고 셋 중 하나라도 어긋나면 `GraphQlShippedAndGatedTest`의 두 단언 중 하나가 깨진다. 중복이되 검증으로 묶여 있다.
|
|
|