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.1 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-c03 | ObjectReference가 보장하는 route 구획 | security-and-trust-boundaries | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-objectstorage-c03 | 2026-09-01 |
|
|
|
adapter-outbound-objectstorage |
ObjectReference가 보장하는 route 구획
RoutingObjectReadAdapter.load는 canonicalText를 분리한 뒤 두 번째 구획을 직접 읽는다. 별도 인덱스 검사는 없지만 ObjectReference 생성자가 ObjectIdentitySupport.requireRouted(canonicalText, "osr1")로 형식을 강제하므로, 유효한 참조에는 route 구획이 항상 존재한다.
본문
직접 인덱싱과 입력 불변식
RoutingObjectReadAdapter.load는 reference.canonicalText().split("\\.", -1)[1]로 route token을 읽는다. 이 코드만 보면 두 번째 구획이 없을 때 ArrayIndexOutOfBoundsException이 발생할 수 있다.
RoutingObjectReadAdapter 참조 위치
:::evidence key="adapter-outbound-objectstorage-c03" alt="코드베이스에서 RoutingObjectReadAdapter 를 검색한 출력 5줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="RoutingObjectReadAdapter 코드베이스 검색 — 5줄 · exit 0" zoom="true" :::
ObjectReference가 보장하는 형식
ObjectReference 생성자는 ObjectIdentitySupport.requireRouted(canonicalText, "osr1")를 통해 routed 형식을 먼저 검증한다. 따라서 정상적으로 생성된 ObjectReference가 load에 전달되는 경로에서는 두 번째 구획이 값 타입의 불변식으로 보장된다. 현재 계약에서는 이 split 자체를 결함으로 분류할 근거가 없다.