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
2.3 KiB
JSON
15 lines
2.3 KiB
JSON
{
|
|
"assetKey": "a13-f005-retry-after-illegalargumentexception-unassembled",
|
|
"kind": "terminal",
|
|
"command": "set -e\nset -o pipefail\nNP=adapter/outbound/notification/src/main/java/dev/caskeleton/adapter/outbound/notification/platform\nAC=application-core/src/main/java/dev/caskeleton/application/notification/platform\necho \"# 재시도 정책이 보는 두 값은 어디서 오는가\"\ngrep -n 'providerIdempotency()\\|statusQuery()' $AC/dispatch/NotificationDispatchService.java\ngrep -n 'context.providerIdempotency()\\|context.statusQuerySupported()' $AC/policy/DefaultNotificationRetryPolicy.java\necho\necho \"# 알림 경로에서 capabilities 를 선언하고 부르는 자리 — 수신자가 무엇인지 본다\"\ngrep -rn 'capabilities()' --include=*.java adapter/outbound/notification/src/main \\\n application-core/src/main/java/dev/caskeleton/application/notification \\\n | grep -v 'ProviderCapabilities.java' | sed -E 's#.*/src/(main|test)/.*/#\\1 · #'\necho\necho \"# ProviderProfileSnapshot 을 만드는 자리\"\ngrep -rn 'new ProviderProfileSnapshot(' --include=*.java . --exclude-dir=build | sed -E 's#.*/src/(main|test)/.*/#\\1 · #'\necho\necho \"# ProviderRuntimeAssembler 구현\"\ngrep -rn 'implements ProviderRuntimeAssembler' --include=*.java . --exclude-dir=build | sed -E 's#.*/src/(main|test)/.*/#\\1 · #'\necho\necho \"# 문제의 세 어댑터를 생성하는 자리\"\ngrep -rn 'new SesNotificationProviderAdapter(\\|new TwilioSmsProviderAdapter(\\|new WebPushNotificationProviderAdapter(' \\\n --include=*.java . --exclude-dir=build | sed -E 's#.*/src/(main|test)/.*/#\\1 · #'\necho\necho \"# 조립기가 없는 계열을 만나면 기동이 거부된다\"\ngrep -rn -B4 'has no assembler in this build' --include=*.java . --exclude-dir=build | sed -E 's#.*/src/(main|test)/.*/#\\1 · #'\n",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template/src",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-02T17:14:09+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a13-f005-retry-after-illegalargumentexception-unassembled.txt",
|
|
"svg": "evidence/rendered/a13-f005-retry-after-illegalargumentexception-unassembled.svg",
|
|
"rawSha256": "1f8a89575f27a2badb98a2ca1ca65629537072ccbd45d3c87b3a12ceb63a988e",
|
|
"lines": 49,
|
|
"redaction": "none — 코드베이스 정적 검색"
|
|
}
|