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.3 KiB
JSON
15 lines
2.3 KiB
JSON
{
|
|
"assetKey": "a05-f020-inspect-claim",
|
|
"kind": "terminal",
|
|
"command": "P=adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/idempotency/PostgreSqlOwnerSafeIdempotencyStore.java\nM=adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/postgresql/idempotency/IdempotencyRecordRows.java\nE=application-core/src/main/java/dev/caskeleton/application/idempotency/v2/IdempotencyExecutorV2.java\nI=adapter/outbound/persistence-jpa/src/postgresqlIntegrationTest/java/dev/caskeleton/adapter/outbound/persistence/readiness/PostgreSqlIdempotencyIntegrationTest.java\n\necho '# 청구 경로는 행을 잠근 뒤 데이터베이스 시각을 읽고 만료를 먼저 본다'\ngrep -n '' \"$P\" | sed -n '127,143p'\ngrep -n -A4 'private static boolean isExpiredCompleted' \"$P\"\necho -n '# claim 본문에서 databaseNow 를 부르는 줄: '\nsed -n '120,170p' \"$P\" | grep -c 'databaseNow'\n\necho\necho '# 조회 경로 전문'\ngrep -n '' \"$P\" | sed -n '393,427p'\necho -n '# inspect 본문에서 databaseNow 를 부르는 줄: '\nsed -n '393,427p' \"$P\" | grep -c 'databaseNow'\necho '# inspect 본문이 replayUntil 로 하는 일'\nsed -n '393,427p' \"$P\" | grep -n 'replayUntil'\necho '# 만료 비교는 파일에 한 곳뿐이고, 그것을 부르는 곳'\ngrep -n 'isExpiredCompleted' \"$P\"\necho '# 조회가 쓰는 조회 SQL 에 시간 술어가 있는가'\ngrep -n -A6 'SELECT_ROW_SQL' \"$M\" | head -10\n\necho\necho '# 조회 결과를 받는 세 자리'\ngrep -n -A3 'case COMPLETED_REPLAY' \"$E\"\n\necho\necho '# 출하 통합 시험의 만료 시험이 무엇을 만료시키는가'\ngrep -n ' void ' \"$I\" | grep -i expired\ngrep -n 'Duration.ofMillis(25)' \"$I\"\ngrep -n -A3 'private static IdempotencyClaimRequest request(' \"$I\"",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template/src",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-02T04:35:46+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a05-f020-inspect-claim.txt",
|
|
"svg": "evidence/rendered/a05-f020-inspect-claim.svg",
|
|
"rawSha256": "6e593699caca084c7ca0492d96ebfb5e84f65e0e1d20ce22efde4616db802ac3",
|
|
"lines": 95,
|
|
"redaction": "none — 코드베이스 정적 검색"
|
|
}
|