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.3 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-outbound-objectstorage-c04 | 새 레코드를 추가하면 컴파일이 codec 갱신을 강제한다 | schema-and-wire-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-objectstorage-c04 | 2026-09-01 |
|
|
|
adapter-outbound-objectstorage |
새 레코드를 추가하면 컴파일이 codec 갱신을 강제한다
ObjectControlRecord가 sealed이고 codec이 exhaustive switch를 쓰므로 계열이 닫혀 있고, 모르는 스키마는 덮어쓰지 않고 격리된다.
본문
ObjectControlRecord는 열한 개 구현만 허용하는 sealed interface이고, javadoc이 규칙을 적는다 — "Unknown families and schemas fail closed." codec의 payload(...)가 그 계열에 대해 exhaustive switch를 쓰므로, 새 레코드를 추가하면 컴파일이 강제로 codec을 갱신하게 만든다.
ObjectControlRecord 참조 위치
:::evidence key="adapter-outbound-objectstorage-c04" alt="코드베이스에서 ObjectControlRecord 를 검색한 출력 35줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ObjectControlRecord 코드베이스 검색 — 35줄 · exit 0" zoom="true" :::
모르는 스키마는 덮어쓰지 않고 격리한다
스키마 버전은 ControlRecordSupport.header가 schemaVersion != 1을 거부한다 — "only control schema version 1 is writable". 더 새로운 스키마를 만나면 UnsupportedObjectControlSchemaException으로 격리한다("A newer or unknown durable schema that must be quarantined rather than overwritten").
누출 금지가 가시성으로 성립한다
objectstorage.control 패키지를 leaf 밖에서 참조하는 코드는 0이다(151-... §8.1, exit=1). CLAUDE.md의 "control-record types leaking into application-core" 금지가 가시성으로 성립한다.