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.6 KiB
JSON
15 lines
2.6 KiB
JSON
{
|
|
"assetKey": "a05-f012-identity",
|
|
"kind": "terminal",
|
|
"command": "G=adapter/outbound/persistence-jpa/src/main/java/dev/caskeleton/adapter/outbound/persistence/hibernate/batch/HibernateBatchConfigurationGuard.java\n\necho '# 가드가 식별자를 찾는 방식'\ngrep -n '' \"$G\" | sed -n '49,75p'\n\necho\necho '# 이 타입을 언급하는 곳 전부 (자기 파일 포함)'\ngrep -rnw 'HibernateBatchConfigurationGuard' --include=*.java --exclude-dir=build . | sed 's|^\\./||'\necho -n '# 그 타입을 인스턴스화하는 main 코드: '\ngrep -rn 'new HibernateBatchConfigurationGuard(' --include=*.java --exclude-dir=build . | grep -c '/main/'\necho -n '# 같은 패키지의 프로파일 레지스트리를 읽는 main 코드: '\ngrep -rnw 'JpaBatchProfileRegistry' --include=*.java --exclude-dir=build . | grep '/main/' | grep -vc 'batch/JpaBatchProfileRegistry.java'\necho '# 계획 문서가 이 과제의 산출물로 적은 것'\ngrep -rn 'startup diagnostics for IDENTITY' ../docs/superpowers/plans/2026-08-11-jpa-persistence-platform-implementation-plan.md\n\necho\necho '# 가드가 거절하려는 전략이 main 에 나타나는 곳'\ngrep -rn 'GenerationType.IDENTITY' --include=*.java --exclude-dir=build . | grep '/main/' | sed 's|^\\./||'\necho -n '# main 에서 @GeneratedValue 를 쓰는 줄: '\ngrep -rnw '@GeneratedValue' --include=*.java --exclude-dir=build . | grep -c '/main/'\n\necho\necho '# 출하 엔티티의 식별자 접근 방식'\necho -n '# main 의 @Entity 파일: '\ngrep -rl '^@Entity' --include=*.java --exclude-dir=build . | grep -c '/main/'\necho -n '# 그중 @Id 를 필드에 단 파일: '\ngrep -rl '^@Entity' --include=*.java --exclude-dir=build . | grep '/main/' | xargs grep -lw '@Id' | wc -l\necho -n '# @Id 바로 뒤가 메서드 선언인 것 (프로퍼티 접근): '\ngrep -rA1 -w '@Id' --include=*.java --exclude-dir=build . | grep '/main/' | grep -c 'public .* get.*()'\necho -n '# @Access 나 AccessType 을 쓰는 줄 (저장소 전체): '\ngrep -rwE '@Access|AccessType' --include=*.java --exclude-dir=build . | wc -l\necho -n '# @EmbeddedId 를 쓰는 main 파일: '\ngrep -rlw '@EmbeddedId' --include=*.java --exclude-dir=build . | grep '/main/' | sed 's|.*/||' ",
|
|
"cwd": "/shared/codebase/clean-architecture-backend-template/src",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-02T03:55:56+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a05-f012-identity.txt",
|
|
"svg": "evidence/rendered/a05-f012-identity.svg",
|
|
"rawSha256": "9c4542285561ec793c0ddf5fcccc3cbaebeff56e65bc410970f9454e12c88f4a",
|
|
"lines": 51,
|
|
"redaction": "none — 출력에 자격증명이 없다"
|
|
}
|