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>
3.3 KiB
kind, slug, title, topic, project, status, sourceRevision, rootTreeNode, evidenceCapturedOn, assets, evidence, source, module
| kind | slug | title | topic | project | status | sourceRevision | rootTreeNode | evidenceCapturedOn | assets | evidence | source | module | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| CONCEPT | adapter-outbound-persistence-jpa-c51 | Stable 스캔 목록에 experimental package가 이미 들어 있다 | transaction-and-consistency-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-persistence-jpa-c51 | 2026-09-01 |
|
|
|
adapter-outbound-persistence-jpa |
Stable 스캔 목록에 experimental package가 이미 들어 있다
현재 production call graph에서 experimental 타입을 조립하는 경로는 없다. 그러나 structural opt-in은 완전히 닫혀 있지 않다.
본문
현재 repository 내부 production call graph에서는 TenantDataSourceRegistry, TenantEntityManagerFactoryRegistry, SchemaMultiTenantConnectionProvider, ConsistencyAwareDataSourceRouter, RlsTenantSessionBinder, SchemaTenantMigrationOrchestrator 등을 app-bootstrap이나 다른 production leaf가 조립하는 경로를 찾지 못했다. backend.jpa.experimental.* property도 production configuration에서 읽어 bean을 만드는 경로가 없고, 실제 문자열은 ExperimentalFeature enum의 property vocabulary에만 존재한다.
TenantDataSourceRegistry 참조 위치
:::evidence key="adapter-outbound-persistence-jpa-c51" alt="코드베이스에서 TenantDataSourceRegistry 를 검색한 출력 8줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="TenantDataSourceRegistry 코드베이스 검색 — 8줄 · exit 0" zoom="true" :::
latent로 분류한 이유
따라서 아래 semantic finding은 현재 app-bootstrap runtime에서 즉시 활성화된 production defect가 아니라 latent experimental defect로 분류한다. 이 구분은 중요하다 — public API surface에 올라 있고 같은 artifact에 포함된 library code가 잘못된 것과, 현재 기본 애플리케이션이 그 code를 실제 실행하는 것은 다른 주장이다.
Stable 스캔 목록에 들어 있는 것
:::evidence key="adapter-outbound-persistence-jpa-c51-diagram" alt="Stable EntityScan 목록에서 stable package 목록과 experimental package 로 화살표가 나가고 experimental 쪽만 빗금 상자로 표시된 구조" caption="Stable 스캔 목록에 들어 있는 것" zoom="false" :::
반면 structural opt-in은 완전히 닫혀 있지 않다. PersistenceJpaConfig의 Stable @EntityScan과 @EnableJpaRepositories 문자열 목록에는 이미 dev.caskeleton.adapter.outbound.persistence.experimental이 들어 있다. 현재 experimental package에는 @Entity, @Repository, JpaRepository, @MappedSuperclass가 없어서 당장 persistence unit에 들어오는 concrete JPA type은 없지만, 이후 experimental entity/repository 하나가 추가되면 별도 feature condition 없이 Stable persistence unit이 스캔한다.