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-httpclient-c03 | 검사할 수 없는 성분을 가진 본문은 재생 가능으로 인증되지 않는다 | schema-and-wire-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-httpclient-c03 | 2026-09-01 |
|
|
|
adapter-outbound-httpclient |
검사할 수 없는 성분을 가진 본문은 재생 가능으로 인증되지 않는다
ObjectBody의 재생 가능성은 값의 성질로 구조적으로 판정되고, 판정할 수 없으면 ONE_SHOT으로 떨어진다.
본문
이 sub-scope에서 가장 신중한 코드다. 과거 동작과 그 결과가 적혀 있다.
ObjectBody 참조 위치
:::evidence key="adapter-outbound-httpclient-c03" alt="코드베이스에서 ObjectBody 를 검색한 출력 29줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ObjectBody 코드베이스 검색 — 29줄 · exit 0" zoom="true" :::
값의 성질로 판정한다
지금은 deeplyImmutable(value)가 구조적으로 판정한다 — 문자열·숫자·불리언·문자·enum·UUID·Temporal은 통과, 컬렉션과 맵은 JDK의 불변 뷰인지 이름으로 확인하고 원소까지 재귀, record는 모든 성분을 반사로 재귀 확인, 그 외는 전부 ONE_SHOT.
인증할 수 없으면 재생하지 않는다
반사가 실패하면 "A component the platform cannot inspect cannot be certified, and an uncertified body is one-shot rather than optimistically replayable." 컬렉션 판정이 이름 기반인 이유도 적혀 있다 — "List.of(...) and Collections.unmodifiableList(...) return package-private classes with no shared marker interface. An ordinary ArrayList the caller still holds is exactly the case this must not accept." test 넷이 네 갈래를 고정한다 — anImmutableRecordReplays, aMutableValueIsOneShot, aRecordWrappingMutableStateIsOneShot, anArbitraryBeanIsOneShot.