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>
1.4 KiB
1.4 KiB
<module/subsystem> 완전 해부
상태: IN_PROGRESS | COMPLETE
기준 revision:
분석 범위: <path/module>
0. 커버리지와 숫자 지도
- production files:
- production LOC:
- packages/directories:
- tests by lane:
- migrations/config/build files:
- runtime membership:
Coverage ledger
| scope/file group | count | disposition | reason |
|---|---|---|---|
| FULL_READ / STRUCTURAL_ONLY / EXCLUDED |
1. 모듈의 정체와 경계
2. 의존성과 런타임 배선
3. 패키지/컴포넌트 지도
4. 계약·불변식·상태 모델
5. 주요 실행 경로
6. 실패 경로와 복구/번역
7. 트랜잭션·동시성·수명주기
8. 설정·기능 플래그·환경 차이
9. 퍼시스턴스/외부 시스템 세부
10. 테스트 레인과 실제 증명 범위
11. 빌드/ArchUnit/CI 강제 지점
12. 실제 사용 여부와 dead/unwired/duplicate 경로
13. Git/설계 문서에서 확인한 변화와 실패 기록
14. 런타임·터미널·브라우저 Evidence
15. 명시적 설계 이유와 추론을 구분한 정리
16. 확인한 것 / 확인하지 못한 것
17. 손볼 것
각 항목: 우선순위 → 사실 → 근거 → 왜 문제인가 → 확인 방법 → 후보/다음 단계.
Source anchors
모든 핵심 주장에 source-index의 파일/심볼/테스트/evidence anchor를 연결한다.