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.2 KiB
JSON
15 lines
2.2 KiB
JSON
{
|
|
"assetKey": "a13-f002-authentication-failed-resumehealthy",
|
|
"kind": "terminal",
|
|
"command": "set -e\nset -o pipefail\nD=src/adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform/dispatch\nO=src/adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform/observation\nT=src/adapter/outbound/notification/src/test/java/dev/caskeleton/adapter/outbound/notification/platform/dispatch\nA=src/application-core/src/main/java/dev/caskeleton/application/notification/platform/admin\necho \"# 같은 원자 참조를 쓰는 전이 일곱\"\ngrep -n \"public void markAuthenticationFailed\\|public boolean mark\\|public boolean resumeHealthy\" $D/ProviderRuntime.java | sed \"s/^/ /\"\necho\necho \"# resumeHealthy 가 적은 보장과 구현\"\ngrep -n \"\" $D/ProviderRuntime.java | sed -n \"195,214p\"\necho\necho \"# 현재 값을 받아 놓고 쓰지 않는 둘\"\ngrep -n \"\" $D/ProviderRuntime.java | sed -n \"221,228p;235,242p\"\necho\necho \"# set 으로 쓰는 하나\"\ngrep -n \"\" $D/ProviderRuntime.java | sed -n \"127,132p\"\necho\necho \"# 관리자 포트가 여섯을 분배한다\"\ngrep -n \"\" $D/RegistryProviderRuntimeControl.java | sed -n \"30,39p\"\necho\necho \"# 헬스 보고기가 unhealthy 로 보는 상태\"\ngrep -n \"\" $O/NotificationHealthReporter.java | sed -n \"18,21p;63,67p\"\necho\necho \"# 사유 코드를 읽는 곳\"\ngrep -rn \"unhealthyReason\" --include=*.java src | sed \"s|.*/dispatch/| |\"\ngrep -n \"record ProviderHealth\" -A1 $O/NotificationHealthSnapshot.java | sed \"s/^/ /\"\necho\necho \"# 이 보장을 확인하는 test\"\ngrep -n \"\" $T/ProviderRuntimeStateTest.java | sed -n \"124,137p;143,150p\"",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-02T14:53:15+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a13-f002-authentication-failed-resumehealthy.txt",
|
|
"svg": "evidence/rendered/a13-f002-authentication-failed-resumehealthy.svg",
|
|
"rawSha256": "83288f4a088fe11462c47d4500f0ceee962de714f7ceb6a86dd0908ecd84a2bc",
|
|
"lines": 109,
|
|
"redaction": "none — 코드베이스 정적 검색"
|
|
}
|