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.8 KiB
1.8 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-core-api-c05 | 코드가 실제로 도는 네 지점 | schema-and-wire-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:messaging-core-api-c05 | 2026-09-01 |
|
|
|
messaging-core-api |
코드가 실제로 도는 네 지점
이 leaf에는 실행 경로가 거의 없다. 실제로 코드가 도는 지점은 넷이다.
본문
이 leaf에는 실행 경로가 거의 없다. 실제로 코드가 도는 지점은 넷이다.
이 기록이 다루는 범위
:::evidence key="messaging-core-api-c05" alt="코드베이스에서 파일 목록을 만든 출력 25줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 25줄 · exit 0" zoom="true" :::
네 지점
- 봉투 생성 —
new MessageEnvelope<>(...)→ 14개 non-null 검사 + partitionKey/orderingKey wire 검사 - 헤더 생성 —
MessageHeaders.application/platform(Map)→ 개수(≤64) → 이름별 예약/자격증명/중복 검사 → 총 바이트(≤32,768) - 식별자 생성 —
MessageId.newId()→UuidV7.next()→AtomicLong.updateAndGet(advance) - 결과 조립 —
new PublishResult(...)/new SettlementResult(...)→ 조합 검증
나머지가 있는 곳
나머지는 전부 인터페이스 선언이고, 구현은 messaging-runtime-core·messaging-kafka·messaging-rabbit 등 다른 leaf가 소유한다.