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.7 KiB
JSON
15 lines
2.7 KiB
JSON
{
|
|
"assetKey": "a-resumed-redrive-skips-what-it-could-not-move",
|
|
"kind": "terminal",
|
|
"command": "M=messaging/messaging-admin-runtime/src/main/java/dev/caskeleton/messaging/admin/runtime\nA=messaging/messaging-admin-api/src/main/java/dev/caskeleton/messaging/admin\nT=messaging/messaging-admin-runtime/src/test/java/dev/caskeleton/messaging/admin/runtime\necho '# 재개 지점의 계약'\ngrep -n 'param resumeFrom' $M/RedriveService.java\necho '# 그리고 건너뛰는 자리의 주석'\nsed -n '109,113p' $M/RedriveService.java\necho\necho '# 그런데 체크포인트가 세는 것은 시도한 개수다'\nsed -n '105,107p;114,120p' $M/RedriveService.java\necho\necho '# 그 체크포인트 값이 다음 재개 지점이 된다'\nsed -n '55,61p' $M/InMemoryAdminOperationJournal.java\nsed -n '101,106p' $M/InMemoryAdminOperationJournal.java\necho '# 두 저널 구현이 각각 되돌아가지 않게 고정한다'\ngrep -n 'Math.max(current.itemsCompleted()' $M/InMemoryAdminOperationJournal.java | head -1\ngrep -rn 'GREATEST' --include=JdbcAdminOperationJournal.java . | sed 's|.*/||' | head -1\necho\necho '# 완료로 닫힌 승인은 다시 인수되지 않는다'\nsed -n '86,89p' $M/InMemoryAdminOperationJournal.java\necho\necho '# 목록은 매번 다시 조회하고, 확인되지 않은 재발행은 정착시키지 않는다'\ngrep -n 'source.peek(request.source' $M/RedriveService.java\nsed -n '10,13p' $A/RedriveResult.java\necho\necho '# 전부 정산됐는지 묻는 술어가 이미 있다'\nsed -n '41,48p' $A/RedriveResult.java\necho -n '# 그 술어를 부르는 main 코드: '\ngrep -rn 'isFullyAccounted' --include=*.java . | grep '/main/' | grep -vc 'RedriveResult.java'\necho -n '# 부르는 테스트 메서드: '\ngrep -rn 'isFullyAccounted' --include=*.java . | grep '/test/' | sed 's|.*/||'\necho\necho '# 이 경로에는 실행 가능한 구현이 없다'\necho -n ' 오케스트레이터를 생성하는 코드: '\ngrep -rn 'new DefaultMessagingAdminService' --include=*.java . | wc -l\necho -n ' RedriveSource 를 구현하는 main 코드: '\ngrep -rn 'implements RedriveService.RedriveSource' --include=*.java . | grep -c '/main/'\necho ' 유일한 구현과 그 조회·정착'\nsed -n '183,201p' $T/RedriveResumptionTest.java\n",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template/src",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-02T02:14:53+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a-resumed-redrive-skips-what-it-could-not-move.txt",
|
|
"svg": "evidence/rendered/a-resumed-redrive-skips-what-it-could-not-move.svg",
|
|
"rawSha256": "a32b123e148be248309cf0a689987896b7916c92518d4a19b90d23ca935cb51d",
|
|
"lines": 88,
|
|
"redaction": "none — 분석 문서 발췌"
|
|
}
|