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.9 KiB
2.9 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-kafka-share-experimental-c05 | 조용히 강등하지 않고 던진다 | delivery-and-settlement-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:messaging-kafka-share-experimental-c05 | 2026-09-01 |
|
|
|
messaging-kafka-share-experimental |
조용히 강등하지 않고 던진다
MessagingCapabilityUnavailableException의 javadoc이 이 leaf의 태도와 정확히 일치한다 — "Thrown instead of quietly degrading. Downgrading … ordered delivery to unordered, produces a system that looks healthy right up to the moment the guarantee actually mattered."
관계
- 허용 의존 목록은 상한이므로 미사용을 잡지 않는다 — 그것을 잡으려면 별도 검사가 필요하다 같은 분석 리프에서 끌어낸 규칙이다.
- leaf의 각 public 클래스는 자기 레인에 테스트를 갖는다 같은 분석 리프에서 끌어낸 규칙이다.
- 에러 메시지가 지시하는 설정은 그 설정을 읽는 코드와 함께 존재해야 한다 같은 분석 리프에서 끌어낸 규칙이다.
- 구성 오류는 한 예외 타입과 안정 코드로 보고한다 같은 분석 리프에서 끌어낸 규칙이다.
본문
실패가 다섯 가지다.
| 코드 | 예외 | 카테고리 | 조건 |
|---|---|---|---|
KAFKA_SHARE_DISABLED |
MessagingCapabilityUnavailableException |
CONFIGURATION |
enabled == false |
| (코드 없음) | IllegalArgumentException |
— | orderingScope != NONE |
KAFKA_SHARE_NO_PAUSE |
MessagingCapabilityUnavailableException |
CONFIGURATION |
pause(...) |
KAFKA_SHARE_NO_RESUME |
MessagingCapabilityUnavailableException |
CONFIGURATION |
resume(...) |
| (코드 없음) | IllegalArgumentException |
— | shareGroup 공백, maxDeliveryCount < 1 |
MessagingCapabilityUnavailableException 참조 위치
:::evidence key="messaging-kafka-share-experimental-c05" alt="코드베이스에서 MessagingCapabilityUnavailableException 를 검색한 출력 37줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="MessagingCapabilityUnavailableException 코드베이스 검색 — 37줄 · exit 0" zoom="true" :::
javadoc 이 이 leaf 의 태도와 일치한다
"Thrown instead of quietly degrading. Downgrading … ordered delivery to unordered, produces a system that looks healthy right up to the moment the guarantee actually mattered."