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
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 | grpc-operation-ledger-jpa-c03 | 서수 컬럼은 값이 끼어들면 모든 행을 조용히 바꾼다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:grpc-operation-ledger-jpa-c03 | 2026-09-01 |
|
|
|
grpc-operation-ledger-jpa |
서수 컬럼은 값이 끼어들면 모든 행을 조용히 바꾼다
IN_PROGRESS에서만 전이할 수 있고 커밋은 결과 참조가 비면 거부한다. 상태 컬럼은 EnumType.STRING이다.
본문
IN_PROGRESS 에서만 전이할 수 있다(requireInProgress). 커밋은 결과 참조가 비면 거부한다.
원장의 전이
:::evidence key="grpc-operation-ledger-jpa-c03-diagram" alt="IN_PROGRESS 에서 COMMITTED 로 가는 실선 화살표와 FAILED 로 가는 점선 화살표가 있고 두 종착 상태에서 나가는 화살표는 없는 구조" caption="원장의 전이" zoom="false" :::
EnumType 참조 위치
:::evidence key="grpc-operation-ledger-jpa-c03" alt="코드베이스에서 EnumType 를 검색한 출력 25줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="EnumType 코드베이스 검색 — 25줄 · exit 0" zoom="true" :::
상태 컬럼을 문자열로 두는 이유
EnumType.STRING 을 쓰는 이유가 javadoc 에 있다 — 서수 컬럼은 열거형에 값이 끼어들면 저장된 모든 행을 조용히 다른 값으로 만든다.