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>
11 lines
617 B
JSON
11 lines
617 B
JSON
{
|
|
"assetKey": "application-core-c10-diagram",
|
|
"kind": "diagram",
|
|
"svg": "assets/diagrams/application-core-c10.svg",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"svgSha256": "06978b8dd61c5197f109bee03eca1e447a52909fbedf6cf3481e861a70ce43e3",
|
|
"claim": "public contract가 arbitrary Object를 허용하지 않고 sealed NotificationVariable algebra를 쓰며 contact point는 암호값과 keyed fingerprint로 분리된다",
|
|
"authoredAt": "2026-09-01T08:36:30+00:00",
|
|
"constraints": "상자 7개 이하 · 라벨은 이름 · 글자 2종 · 색 단독 의미 없음 · 숫자 없음"
|
|
}
|