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 | domain-core-c01 | 도메인 내용이 아니라 도메인 모델링 계약을 소유한다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:domain-core-c01 | 2026-09-01 |
|
|
|
domain-core |
도메인 내용이 아니라 도메인 모델링 계약을 소유한다
현재 domain-core에는 WorkLog 같은 실제 aggregate가 없다. 실제 샘플 aggregate/value object/event는 sample-portfolio에 있다.
본문
현재 domain-core에는 WorkLog 같은 실제 aggregate가 없다. 실제 샘플 aggregate/value object/event는 sample-portfolio에 있다.
이 모듈이 실제로 소유한 것
:::evidence key="domain-core-c01-diagram" alt="모듈 경계 안에 식별자 추상화와 모델링 표식 두 상자가 들어 있고 sample-portfolio 의 aggregate 가 경계 밖 점선 상자로 놓인 구조" caption="이 모듈이 실제로 소유한 것" zoom="false" :::
이 모듈에 남은 production surface는 두 종류다 — 식별자 추상화(ResourceId, IdFactory)와 모델링 표식(@ValueObject, @AggregateRoot, @DomainEvent).
ResourceId 참조 위치
:::evidence key="domain-core-c01" alt="코드베이스에서 ResourceId 를 검색한 출력 2줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ResourceId 코드베이스 검색 — 2줄 · exit 0" zoom="true" :::
정책이 허용하는 범위와 현재 내용의 차이
"business concepts, entities, value objects…"를 둘 수 있는 계층이라는 정책과 달리, 현재 snapshot의 실제 contents는 skeleton 전반에서 사용할 domain-layer contract/marker에 가깝다. 이는 현재 source에 대한 관찰이며, 향후 실제 production domain type이 이 module에 추가되지 않는다는 뜻은 아니다.