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.0 KiB
2.0 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-web-c09 | 캐시 헤더를 소유하는 것은 24줄 상수 두 개다 | state-machines-and-ownership | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-inbound-web-c09 | 2026-09-01 |
|
|
|
adapter-inbound-web |
캐시 헤더를 소유하는 것은 24줄 상수 두 개다
배선된 CacheControlFilter는 @Component라 컴포넌트 스캔이 잡고 모든 응답에 no-store를 붙인다. 프로파일·지시자·Vary 규칙을 갖춘 cache 패키지 4파일 310 LOC은 배선되지 않았다.
본문
배선된 쪽은 CacheControlFilter다. @Component이므로 컴포넌트 스캔이 잡고 Spring이 Filter 빈을 체인에 넣는다. 모든 응답에 no-store를 붙인다. 배선되지 않은 것은 cache 패키지 4개 파일 310 LOC이고, web.cache. 패키지를 참조하는 파일이 자기 패키지 밖에 0개다.
분석 원문의 두 벌 비교
:::evidence key="adapter-inbound-web-c09" alt="분석 문서 analysis/14-adapter-inbound-web.md 에서 이 기록의 근거 절을 그대로 잘라낸 15줄. 코드베이스를 측정한 것이 아니라 원본 판정이 무엇을 적었는지를 보여 준다." caption="analysis/14-adapter-inbound-web.md 발췌 — 15줄" zoom="true" :::
소유자를 지목하는 주석과 실제 소유자
SecurityConfig:80이 Spring Security의 기본 캐시 헤더 작성기를 끄면서 그 이유를 적는다 — "CacheControlFilter owns the cache header policy". 소유자는 24줄짜리 상수 두 개이고, 프로파일·지시자·Vary 규칙을 갖춘 310줄은 소유하지 않는다.