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.1 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-cache-redis-c11 | R4인데 BLOCKED이 아닌 정책 파일은 읽히지 않는다 | schema-and-wire-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-cache-redis-c11 | 2026-09-01 |
|
|
|
adapter-outbound-cache-redis |
R4인데 BLOCKED이 아닌 정책 파일은 읽히지 않는다
RedisCommandPolicyLoader가 일반 YAML 파서를 쓰지 않고, 교차 필드 불변식이 로딩 시점에 적용된다.
본문
RedisCommandPolicyLoader의 javadoc이 일반 YAML 파서를 쓰지 않는 이유를 적는다. 파서는 그만큼 좁다 — 탭 금지, 들여쓰기 0/2/4만 허용, commands: 루트 정확히 하나, 명령 블록 중복 금지, 필드 이름 allowlist(12종) 밖이면 거부, 빈 값 거부, 필드 중복 거부. test가 rejectsUnknownFieldsEnumsAndDuplicates로 잡는다.
RedisCommandPolicyLoader 참조 위치
:::evidence key="adapter-outbound-cache-redis-c11" alt="코드베이스에서 RedisCommandPolicyLoader 를 검색한 출력 6줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="RedisCommandPolicyLoader 코드베이스 검색 — 6줄 · exit 0" zoom="true" :::
모순된 정책 파일은 읽히지 않는다
RedisCommandPolicy/RedisCommandDescriptor의 교차 필드 불변식(§24)이 로딩 시점에 적용되므로, "R4인데 BLOCKED이 아닌" 정책 파일은 읽히지 않는다.
집합을 고정하는 테스트
everyDestructiveCommandIsBlockedAndUnreachable·deprecatedCommandNamesAreNotReachable·arbitraryScriptSourceExecutionIsBlocked·theCatalogFailsClosedForAnUnclassifiedCommand.