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.0 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-persistence-jpa-c43 | H2 idempotency와 V2 owner 필드 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-persistence-jpa-c43 | 2026-09-01 |
|
|
|
adapter-outbound-persistence-jpa |
H2 idempotency와 V2 owner 필드
H2IdempotencyClaimRepository의 MERGE/takeover는 V2 owner/transition field를 초기화하지 않는다. baseline IdempotencyRecordEntity가 V1 field만 매핑하고 owner-safe V2는 PostgreSQL capability stream으로 분리되어 있으므로, 서로 다른 schema generation의 필드를 H2 V1이 reset하지 않는 것은 현재 계약 위반이 아니다.
본문
H2 baseline이 소유하는 필드
H2IdempotencyClaimRepository의 MERGE/takeover 경로에는 V2 owner/transition field 초기화가 없다. 그러나 baseline IdempotencyRecordEntity 자체가 V1 field만 매핑한다.
H2IdempotencyClaimRepository 참조 위치
:::evidence key="adapter-outbound-persistence-jpa-c43" alt="코드베이스에서 H2IdempotencyClaimRepository 를 검색한 출력 4줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="H2IdempotencyClaimRepository 코드베이스 검색 — 4줄 · exit 0" zoom="true" :::
PostgreSQL V2와 분리된 activation contract
owner-safe V2는 PostgreSQL capability stream으로 분리되어 별도 activation contract를 가진다. H2 baseline 경로와 PostgreSQL V2 경로가 서로 다른 schema generation을 소유하므로, H2 V1이 V2 field를 reset하지 않는 동작은 현재 계약과 충돌하지 않는다.