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>
15 lines
2.4 KiB
JSON
15 lines
2.4 KiB
JSON
{
|
|
"assetKey": "a-test-that-passed-on-the-wrong-guard",
|
|
"kind": "terminal",
|
|
"command": "N=adapter/outbound/notification/src\nC=$N/main/java/dev/caskeleton/adapter/outbound/notification/catalog/NotificationBindingCompiler.java\nT=$N/test/java/dev/caskeleton/adapter/outbound/notification/catalog/NotificationBindingCompilerTest.java\necho '# 첫 가드가 SINGLE 아닌 전략을 전부 거부한다'\nsed -n '140,145p' $C\necho '# 그 뒤 전략을 보지 않는 검사 둘'\nsed -n '146,158p' $C\necho\necho '# switch 네 갈래 — SINGLE 을 뺀 셋은 도달할 수 없다'\nsed -n '159,185p' $C\necho\necho '# 그리고 폴백 그래프 검사가 던질 수 있는 두 문구'\ngrep -n 'fallback references unknown target' $C\ngrep -n 'cyclic notification fallback graph' $C\necho\necho '# 순환을 거부한다는 테스트'\ngrep -n 'void legacyReceiptUnsafeFallbackBoundsAndCyclesAreRejected' $T\necho '# 그 테스트가 만든 팬아웃 라우트'\nsed -n '246,253p' $T\necho '# 그리고 순환 라우트 — 전략과 범위 값'\nsed -n '279,300p' $T\necho '# 그 둘에 붙은 단언'\ngrep -n 'hasMessageContaining' $T | sed -n '5,6p'\necho\necho '# 이 두 분기를 태울 라우트를 만드는 곳 — 저장소 전수'\ngrep -rn 'NotificationRouteStrategy\\.\\(FAN_OUT_ALL\\|ORDERED_FALLBACK\\)' --include=*.java . | sed 's|.*/||'\necho -n '# 설정 파일의 비-SINGLE 전략: '\ngrep -rn 'FAN_OUT_ALL\\|ORDERED_FALLBACK' --include=*.json --include=*.yaml --include=*.yml . | wc -l\necho\necho '# 그 테스트를 실제로 돌린 결과'\n./gradlew :adapter:outbound:notification:test --tests '*NotificationBindingCompiler*' --offline --console=plain 2>&1 | grep -E 'BUILD|tests completed'\nX=$(find $N/../build/test-results -name '*NotificationBindingCompilerTest.xml' 2>/dev/null | head -1)\n[ -n \"$X\" ] && grep -o 'tests=\"[0-9]*\" skipped=\"[0-9]*\" failures=\"[0-9]*\" errors=\"[0-9]*\"' \"$X\" | head -1\n",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template/src",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-02T02:48:01+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a-test-that-passed-on-the-wrong-guard.txt",
|
|
"svg": "evidence/rendered/a-test-that-passed-on-the-wrong-guard.svg",
|
|
"rawSha256": "3271ecb9ed1356089f705ff969cc3502243b98761b41779f78477f191168005a",
|
|
"lines": 106,
|
|
"redaction": "none — 분석 문서 발췌"
|
|
}
|