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
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-observability-c05 | 손상된 traceparent 는 이 leaf 의 실패 어휘 밖에서 터진다 | delivery-and-settlement-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:messaging-observability-c05 | 2026-09-01 |
|
|
|
messaging-observability |
손상된 traceparent 는 이 leaf 의 실패 어휘 밖에서 터진다
이 leaf는 MessagingException을 하나도 던지지 않는다. 실패를 값으로 표현한다.
관계
- 타입이 문서화한 불변식은 타입이 강제한다 같은 분석 리프에서 끌어낸 규칙이다.
본문
이 leaf는 MessagingException을 하나도 던지지 않는다. 실패를 값으로 표현한다.
MessagingException 참조 위치
:::evidence key="messaging-observability-c05" alt="코드베이스에서 MessagingException 를 검색한 출력 36줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="MessagingException 코드베이스 검색 — 36줄 · exit 0" zoom="true" :::
던지는 곳은 전부 호출자의 프로그래밍 오류다
IllegalArgumentException을 던지는 곳은 넷 — CardinalityGuard 생성자(limitPerDimension < 1), MessagingMetrics.recordDelivery(attempt < 1), MessagingTracer.shouldLinkRatherThanContinue(batchSize < 1), MessagingAuditEvent 생성자(빈 필드).
extract 가 W3C 검증에 걸릴 수 있다
new TraceContext(traceparent, tracestate, baggage)가 core-api의 정규식·바이트 상한·all-zero 검사를 돌리므로(그쪽 §4.11), 다른 시스템이 보낸 손상된 traceparent는 IllegalArgumentException이 된다. 그 예외는 MessagingException이 아니고 extract는 그것을 잡지 않는다. messaging-cloudevents의 id 파싱과 같은 형태다(analysis/messaging/messaging-cloudevents.md §17). §17.