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.2 KiB
2.2 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-c03 | 실패가 런타임이 아니라 빌드에서 발생한다 | result-and-failure-algebra | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:domain-core-c03 | 2026-09-01 |
|
|
|
domain-core |
실패가 런타임이 아니라 빌드에서 발생한다
이 module의 runtime executable behavior는 매우 작다. annotation 자체에는 success/failure path가 없고 interface도 implementation을 가지지 않으므로, 주요 failure mechanics는 build-time architecture violation이다.
본문
이 module의 runtime executable behavior는 매우 작다. annotation 자체에는 success/failure path가 없고, interface도 implementation을 가지지 않는다. 그래서 주요 failure mechanics는 build-time architecture violation이다.
위반이 걸리는 규칙 이름
| 위반 | 잡는 규칙 |
|---|---|
| forbidden framework/domain dependency | DOMAIN_IS_PURE |
| domain logger dependency | DOMAIN_HAS_NO_LOGGER |
| public no-arg value object | VALUE_OBJECTS_HAVE_NO_PUBLIC_NO_ARG_CONSTRUCTOR |
public set* aggregate mutator |
AGGREGATE_ROOT_SETTERS_ARE_NOT_PUBLIC |
| non-record domain event | DOMAIN_EVENTS_ARE_RECORDS |
| enumerated transport dependency | DOMAIN_EVENTS_ARE_TRANSPORT_FREE |
ResourceId에 할당할 수 없는 id field raw type |
NO_LONG_ID_PK |
| registry에 없는 project dependency | verifyCleanArchitectureDependencies |
production -> sample-portfolio edge |
settings registry validation · root dependency verification · cross-module ArchUnit rule |
코드베이스의 ResourceId 참조
:::evidence key="domain-core-c03" alt="코드베이스에서 ResourceId 를 검색한 출력 2줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="ResourceId 코드베이스 검색 — 2줄 · exit 0" zoom="true" :::