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.3 KiB
Plaintext
16 lines
1.3 KiB
Plaintext
### 8.3 P3 — `messaging-admin-api`는 main 25파일 · 1,613 LOC에 테스트 파일이 1개다
|
|
|
|
```
|
|
messaging-admin-api main=25 test=1 (DestructiveOperationGuardTest)
|
|
messaging-admin-runtime main=12 test=6
|
|
```
|
|
|
|
`messaging-admin-api`가 담고 있는 것은 승인·다이제스트·토폴로지 계약이다 — `ApprovalVerifier`, `HmacApprovalVerifier`, `ApprovalGrant`, `VerifiedApproval`, `PlanDigest`, `ApprovedRedrivePlan`, `ApprovedReplayPlan`, `DestructiveOperation`, `TopologyManifest`, `TopologyValidationReport` 등 보안에 직결되는 타입들이다.
|
|
|
|
**다만 이것은 보이는 것보다 덜 나쁘다.** 실제 검증은 `messaging-admin-runtime`의 테스트 6개가 수행한다 — `ApprovalForgeryTest`(위조 승인 거부), `ApprovedPlanExecutionTest`, `RedriveResumptionTest`, `AdminOperationJournalTest`, `TopologyValidationRuntimeTest`, `TopologyValidatorTest`. `HmacApprovalVerifier`의 test 참조가 4건인 것이 그 증거다.
|
|
|
|
즉 계약 leaf에 테스트가 없는 것이 아니라 **테스트가 소비자 leaf에 있다.** 계약 자체의 경계 조건(예: `PlanDigest`의 정규화, `ApprovalGrant`의 만료)이 별도로 고정돼 있는지는 확인되지 않는다. 기록으로 남긴다.
|
|
|
|
### 8.4 검증된 설계 — actuator 엔드포인트가 읽기 전용이고 재식별 표면을 만들지 않는다
|
|
|