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>
2.2 KiB
2.2 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | |||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | messaging-schema-api-c04 | 진화 검사 경로는 이 저장소에서 실행되지 않는다 | schema-and-wire-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:messaging-schema-api-c04 | 2026-09-01 |
|
|
|
messaging-schema-api |
진화 검사 경로는 이 저장소에서 실행되지 않는다
- 경계 있는 인코딩 — codec이 BoundedByteSink.of(maxBytes, code)를 만들고 → 포맷 라이브러리가 sink에 쓰고 → 한도를 넘는 write에서 MessageTooLargeException → 아니면 sink.toByteArray()로 EncodedMessage 조립 2.
관계
- port 계약은 동시성 요구를 적는다 같은 분석 리프에서 끌어낸 규칙이다.
- 도달성 판정은 단어가 아니라 import로 확인한다 같은 분석 리프에서 끌어낸 규칙이다.
본문
세 경로가 있다.
- 경계 있는 인코딩 — codec이
BoundedByteSink.of(maxBytes, code)를 만들고 → 포맷 라이브러리가 sink에 쓰고 → 한도를 넘는 write에서MessageTooLargeException→ 아니면sink.toByteArray()로EncodedMessage조립 - 계약 조회 —
new MessageContractKey(type, version)→ registry lookup → 미스면 "타입 미등록" vs "버전 미등록" 구분 - 진화 검사 —
registry.compatibilityOf(subject)→versionsToCheck→ (포맷별 게이트가 실제 비교)
MessageTooLargeException 참조 위치
:::evidence key="messaging-schema-api-c04" alt="코드베이스에서 MessageTooLargeException 를 검색한 출력 13줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="MessageTooLargeException 코드베이스 검색 — 13줄 · exit 0" zoom="true" :::
셋째만 실행되지 않는다
3번은 이 저장소에서 실행되지 않는다(§12.1).