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>
48 lines
2.0 KiB
Markdown
48 lines
2.0 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: messaging-claim-check-c05
|
|
title: 만료와 불일치를 다른 카테고리로 가른다
|
|
topic: state-machines-and-ownership
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:messaging-claim-check-c05
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: messaging-claim-check-c05
|
|
file: ../../../final/evidence/rendered/messaging-claim-check-c05.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/messaging-claim-check-c05.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/messaging/messaging-claim-check.md#L270 이다.
|
|
module: messaging-claim-check
|
|
---
|
|
|
|
# 만료와 불일치를 다른 카테고리로 가른다
|
|
|
|
분류가 두 단계로 정확하다 — 만료·부재는 운영 문제(`PERMANENT_BUSINESS`), 크기·digest 불일치는 오염(`POISON_MESSAGE`).
|
|
|
|
## 관계
|
|
|
|
- **leaf의 각 public 클래스는 자기 레인에 테스트를 갖는다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
- **같은 튜닝 값이 두 계층에 있으면 어느 쪽이 이기는지 정한다**
|
|
같은 분석 리프에서 끌어낸 규칙이다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
**분류가 두 단계로 정확하다.** 만료·부재는 운영 문제(`PERMANENT_BUSINESS`), 크기·digest 불일치는 오염(`POISON_MESSAGE`). 두 예외 클래스와 두 카테고리가 그 구분을 담는다.
|
|
|
|
## ClaimCheckIntegrityGuard 참조 위치
|
|
|
|
:::evidence key="messaging-claim-check-c05" alt="코드베이스에서 ClaimCheckIntegrityGuard 를 검색한 출력 11줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ClaimCheckIntegrityGuard 코드베이스 검색 — 11줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
## 환경 문제를 메시지 실패로 만들지 않는다
|
|
|
|
`ClaimCheckIntegrityGuard.sha256`이 `NoSuchAlgorithmException`을 `IllegalStateException("Java runtime does not provide SHA-256")`으로 감싼다 — 복구 불가능한 환경 문제이므로 메시지 실패가 아니다.
|
|
|
|
<!-- body:end -->
|