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.6 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-inbound-graphql-c06 | 매니페스트 조회를 설계했는데 단일 빈이 대신 주입된다 | composition-and-lifecycle-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-inbound-graphql-c06 | 2026-09-01 |
|
|
|
adapter-inbound-graphql |
매니페스트 조회를 설계했는데 단일 빈이 대신 주입된다
설계는 GraphQlClientPolicyManifest에서 프로파일을 해석하는 것을 말하지만, 자동설정은 GraphQlClientPolicy.defaults(...) 단일 빈을 만들어 여덟 개 빈에 주입한다. 매니페스트는 만들어지지 않는다.
본문
설계는 매니페스트 조회를 말한다.
GraphQlClientPolicyManifest— "The design keeps benchmarked limits in an environment manifest rather than in application code, so this is the one place a profile is resolved from. An unknown profile is a startup or request failure rather than a silent fallback to a permissive default."
자동설정은 단일 빈을 만든다.
// GraphQlPlatformAutoConfiguration:302-303
@Bean public GraphQlClientPolicy graphQlClientPolicy(GraphQlPlatformSettings properties) {
return GraphQlClientPolicy.defaults(...);
}
그리고 그 하나가 여덟 개 빈(:123 · :237 · :380 · :389 · :397 · :453 · :463 …)에 주입된다. 매니페스트는 만들어지지 않는다. §16.2.
GraphQlPlatformWebInterceptor 참조 위치
:::evidence key="adapter-inbound-graphql-c06" alt="코드베이스에서 GraphQlPlatformWebInterceptor 를 검색한 출력 10줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="GraphQlPlatformWebInterceptor 코드베이스 검색 — 10줄 · exit 0" zoom="true" :::
프로파일은 여전히 신뢰된 경로에서 온다
프로파일 자체는 신뢰된 경로에서 온다 — GraphQlAuthenticationContextFactory:59가 principal.clientProfile()을 쓰고(검증된 principal), 미인증 호출자에는 GraphQlPlatformWebInterceptor의 anonymousProfile이 붙는다. 즉 GraphQlClientProfileResolver가 막으려는 노출(호출자가 자기 프로파일을 지정)은 배선된 경로에서도 발생하지 않는다. 그 타입은 중복이다.