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.7 KiB
1.7 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 | adapter-inbound-websocket-c04 | 키를 요구하는 검증기가 없어서 잘못된 확인 신호도 없다 | schema-and-wire-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-inbound-websocket-c04 | 2026-09-01 |
|
|
|
adapter-inbound-websocket |
키를 요구하는 검증기가 없어서 잘못된 확인 신호도 없다
ResumeTokenCodec(217) + ResumeTokenKeyRing(87) 조합은 graphql §24.1의 커서 코덱 조합과 같은 형태인데, 차이가 하나 있다.
본문
ResumeTokenCodec(217) + ResumeTokenKeyRing(87)이 서명된 재개 토큰을 만든다. 이 조합은 graphql §24.1의 HmacGraphQlCursorCodec + GraphQlCursorKeyRing과 같은 형태다.
ResumeTokenCodec 참조 위치
:::evidence key="adapter-inbound-websocket-c04" alt="코드베이스에서 ResumeTokenCodec 를 검색한 출력 26줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ResumeTokenCodec 코드베이스 검색 — 26줄 · exit 0" zoom="true" :::
잘못된 확인 신호가 없는 이유
차이는 이쪽에는 그 키를 요구하는 시작 검증기가 없다는 것 — 즉 "키를 요구하고 서명하지 않는" 잘못된 확인 신호가 없다. 면책 목록에 replay/resume이 있으므로 문서·코드·검증이 일치한다.