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.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-outbound-persistence-jpa-c57 | registry에서 task graph 한 방향만 검사한다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-persistence-jpa-c57 | 2026-09-01 |
|
|
|
adapter-outbound-persistence-jpa |
registry에서 task graph 한 방향만 검사한다
config/jpa/release-registry.json의 gate는 6개이고 모두 blocking이다. pool lane은 registry에도 support-matrix에도 JpaReleaseGate.required()에도 없는데 jpaPlatformReleaseGate가 그것을 의존한다.
본문
config/jpa/release-registry.json의 gate는 6개이고 모두 blocking이다. pool lane은 registry에도, docs/jpa/support-matrix.md §Release gates 6행에도, testkit JpaReleaseGate.required()에도 없다(세 곳 모두 grep exit=1). 그런데 jpaPlatformReleaseGate는 dependsOn jpaPlatformPoolContractTest를 갖고, root jpaReleaseGate가 그것을 다시 의존한다.
분석 원문의 세 곳 확인
:::evidence key="adapter-outbound-persistence-jpa-c57" alt="분석 문서 analysis/05-adapter-outbound-persistence-jpa.md 에서 이 기록의 근거 절을 그대로 잘라낸 15줄. 코드베이스를 측정한 것이 아니라 원본 판정이 무엇을 적었는지를 보여 준다." caption="analysis/05-adapter-outbound-persistence-jpa.md 발췌 — 15줄" zoom="true" :::
검사되지 않는 반대 방향
verifyJpaReleaseGateTasks는 registry → task graph 한 방향만 검사한다 — registry의 각 gate가 실제 Test task로 resolve되는가. 반대 방향, 즉 release gate에 들어 있는 lane이 registry에 있는가는 어디서도 검사되지 않는다.
결함으로 올리지 않은 이유
jpaPlatformReleaseGate의 주석이 밝힌 집계 기준은 "documented gate가 검증되지 않은 채 통과하게 만드는 lane"이고, pool lane은 문서화된 gate를 뒷받침하지 않으므로 기준상 registry에 없는 것이 일관적이다. 다만 그 결과로 jpaPlatformReleaseGate에서 pool lane 의존을 지워도 어떤 verifier도 반응하지 않고, 남는 실행 경로는 nightly workflow 한 줄뿐이다. 이 lane의 release gate 소속만은 아무 계약도 보호하지 않는다. P3.