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>
2.1 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-c30 | Querydsl은 production runtimeClasspath에 들어오지 않는다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-persistence-jpa-c30 | 2026-09-01 |
|
|
|
adapter-outbound-persistence-jpa |
Querydsl은 production runtimeClasspath에 들어오지 않는다
QuerydslJpaSupport는 Advanced opt-in으로 설계돼 있고, lockfile에서 Querydsl은 compileClasspath와 test/integration/performance classpath에만 나타난다.
본문
QuerydslJpaSupport는 Advanced opt-in으로 설계돼 있다. lockfile에서 Querydsl은 compileClasspath와 test/integration/performance classpath에는 나타나지만 production runtimeClasspath configuration에는 포함되지 않는다.
QuerydslJpaSupport 참조 위치
:::evidence key="adapter-outbound-persistence-jpa-c30" alt="코드베이스에서 QuerydslJpaSupport 를 검색한 출력 3줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="QuerydslJpaSupport 코드베이스 검색 — 3줄 · exit 0" zoom="true" :::
helper가 두는 제한
따라서 JPA leaf를 사용하는 것만으로 Querydsl runtime dependency가 Stable deployment에 따라오는 구조는 아니다. QuerydslJpaSupport도 bounded page size <= 500, null predicate는 explicit unbounded opt-in 없으면 거부, 등록된 QueryName을 Hibernate comment hint로 적용이라는 제한을 둔다.
미채택 상태로 기록한다
현재 production consumer는 확인되지 않았다. 이는 Advanced opt-in helper의 미채택 상태로 기록하며 dead-code defect로 단정하지 않는다.