DongHyeonkaandClaude Opus 5
b2963105a8
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
4.9 KiB
JSON
15 lines
4.9 KiB
JSON
{
|
|
"assetKey": "analysis-finding-a05-f030",
|
|
"kind": "terminal",
|
|
"command": "#!/bin/bash\nset -euo pipefail\ncd /shared/codebase/clean-architecture-backend-template\n. /tmp/lib.sh\nJ=src/adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/notification/platform/JpaAdminOperationStore.java\nS=src/application-core/src/main/java/dev/caskeleton/application/notification/platform/admin/NotificationAdminApplicationService.java\nV=$(git ls-files -- '**/V8__notification_admin_claim.sql'); V3=$(git ls-files -- '**/V3__notification_platform_inbox_admin.sql')\nE=$(git ls-files -- '**/AdminAuditEntity.java'); T=$(git ls-files -- '**/AdminOperationClaimContractTest.java')\nR=$(git ls-files -- '**/AdminAuditJpaRepository.java')\nfor f in \"$J\" \"$S\" \"$V\" \"$V3\" \"$E\" \"$T\" \"$R\"; do test -f \"$f\"; done\n\necho \"# 마이그레이션이 만든 것\"\nat \"$V\" 1 29 V8__notification_admin_claim.sql\necho \" operation_id 의 유일성 제약 :\"\nhits 'uk_notification_admin_operation|UNIQUE \\(operation_id\\)' \"$V3\" \\\n | sed -E 's#^([0-9]+): *# V3__notification_platform_inbox_admin.sql:\\1 #'\n\necho\necho \"# 청구가 넣는 행과 저장이 넣는 행\"\nat \"$J\" 30 72 JpaAdminOperationStore.java\necho\nat \"$R\" 22 47 AdminAuditJpaRepository.java\necho\nat \"$J\" 91 108 JpaAdminOperationStore.java\n\necho\necho \"# 그 청구를 부르는 자리\"\nprintf ' operations.claim 을 부르는 main 줄 : %s\\n' \"$({ grep -c 'operations\\.claim' \"$S\" || true; })\"\nprintf ' [대조] operations.save 를 부르는 main 줄 : %s\\n' \"$({ grep -c 'operations\\.save' \"$S\" || true; })\"\necho \" AdminOperationClaim 을 참조하는 파일 :\"\nhits 'AdminOperationClaim' 'src/**/*.java' | cut -d: -f1 | sort -u | sed 's#.*/# #'\n\necho\necho \"# 청구가 넣은 행을 완료로 바꾸는 코드가 있는가\"\nprintf ' 프로덕션에서 그 컬럼을 갱신하는 자리 : %s 개\\n' \\\n \"$({ git grep -niE 'UPDATE notification_admin_audit|SET +phase' -- 'src/**/src/main/**' || true; } | grep -c . || true)\"\necho \" 그 문장이 나오는 자리 전부 (시험 포함) :\"\n{ git grep -niE 'UPDATE notification_admin_audit|SET +phase' -- 'src/**' || true; } \\\n | sed -E 's#^src/(.*)/java/.*/([A-Za-z0-9_]+\\.java):([0-9]+): *# \\2:\\3 #'\necho \" AdminAuditEntity 가 가진 필드 :\"\nE=$(git ls-files -- '**/AdminAuditEntity.java')\n{ grep -nE '^ private ' \"$E\" || true; } | sed -E 's#^([0-9]+): *# AdminAuditEntity.java:\\1 #'\n\necho\necho \"# 청구 계약 시험이 무엇을 단언하는가\"\nT=$(git ls-files -- '**/AdminOperationClaimContractTest.java')\n{ grep -nB1 -E ' void [a-zA-Z]+\\(\\)' \"$T\" || true; } \\\n | sed -E 's#^([0-9]+)[:-] *# AdminOperationClaimContractTest.java:\\1 #'\nprintf ' 그 시험 파일에서 COMPLETED 가 나오는 줄 : %s 개\\n' \"$({ grep -c 'COMPLETED' \"$T\" || true; })\"\nprintf ' phase 를 단언하는 줄 : %s 개\\n' \"$({ grep -cE 'assertThat\\(phase' \"$T\" || true; })\"\n\necho\necho \"# 두 연산을 이어 부르면 무엇이 일어나는가\"\necho \" postgres:16-alpine 에 V3 51~62 와 V8 12~15·27~29 를 그대로 적용하고 두 삽입을 이어 실행한다.\"\ndocker rm -f ca-f030 >/dev/null 2>&1 || true\ndocker run -d --name ca-f030 -e POSTGRES_PASSWORD=probe postgres:16-alpine >/dev/null\nfor _ in $(seq 1 30); do docker exec ca-f030 pg_isready -U postgres >/dev/null 2>&1 && break; sleep 1; done\npg() { docker exec -i ca-f030 psql -q -v ON_ERROR_STOP=0 -U postgres 2>&1 | sed 's/^/ /'; }\n{ sed -n '51,62p' \"$V3\"; sed -n '12,15p' \"$V\"; sed -n '27,29p' \"$V\"; } | pg\necho \" 1. claimOperation 의 삽입 (AdminAuditJpaRepository:34-39)\"\necho \"INSERT INTO notification_admin_audit ( id, operation_id, action, actor_ref, attributes, dry_run, occurred_at, command_fingerprint, phase, claimed_at) VALUES ('11111111-1111-1111-1111-111111111111', 'op-1', 'RETRY', 'actor-a', '{}'::jsonb, false, now(), 'fp-a', 'CLAIMED', now()) ON CONFLICT (operation_id) DO NOTHING;\" | pg\necho \" 2. save 의 삽입 (JpaAdminOperationStore:96-106) — ids.nextId() 로 새 id, 같은 operation_id\"\necho \"INSERT INTO notification_admin_audit (id, operation_id, action, actor_ref, reason_code, tenant_id, attributes, dry_run, occurred_at) VALUES ('22222222-2222-2222-2222-222222222222', 'op-1', 'RETRY', 'actor-a', NULL, NULL, '{}'::jsonb, false, now());\" | pg\necho \" 3. 남은 행\"\necho \"SELECT operation_id, phase, id FROM notification_admin_audit;\" | pg\ndocker rm -f ca-f030 >/dev/null 2>&1 || true\n",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-04T06:58:09+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/analysis-finding-a05-f030.txt",
|
|
"svg": "evidence/rendered/analysis-finding-a05-f030.svg",
|
|
"rawSha256": "f5b7f2bc764748b1b732723d2d2d87caf282c3bef764b237235e4c0ec974007a",
|
|
"lines": 182,
|
|
"redaction": "없음"
|
|
}
|