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.4 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 | app-bootstrap-c02 | 런타임 멤버십이 결정하는 어댑터 활성화 스위치 범위 | capability-and-disclosure-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:app-bootstrap-c02 | 2026-09-01 |
|
|
|
app-bootstrap |
런타임 멤버십이 결정하는 어댑터 활성화 스위치 범위
src/config/architecture/modules.json의 runtime_memberships가 인바운드 어댑터의 런타임 포함 여부를 결정한다. gRPC와 WebSocket은 build-only leaf라 런타임 멤버십이 없고, MasterSwitch·env-keys.yaml·AdapterActivationReport에 활성화 스위치가 없는 상태가 이 모델과 일치한다.
본문
build-only 전송의 런타임 멤버십
adapter-inbound-grpc와 adapter-inbound-websocket의 runtime_memberships는 비어 있다. ConditionalTransportCompositionContractTest도 두 leaf가 어떤 런타임에도 올라가지 않아야 한다는 계약을 강제한다.
MasterSwitch 참조 위치
:::evidence key="app-bootstrap-c02" alt="코드베이스에서 MasterSwitch 를 검색한 출력 17줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="MasterSwitch 코드베이스 검색 — 17줄 · exit 0" zoom="true" :::
멤버십과 활성화 스위치의 관계
런타임에 포함되지 않는 build-only 어댑터에는 운영자가 켜고 끌 활성화 스위치가 필요하지 않다. 따라서 gRPC와 WebSocket이 MasterSwitch·env-keys.yaml·AdapterActivationReport에 없는 것은 누락이 아니라 런타임 멤버십 모델과 일치한다.
별도로 남는 web 경계
adapter-inbound-web은 ["app-bootstrap", "sample-portfolio"] 두 런타임에 포함된다. backend.web.mvc.enabled, backend.web.webflux.enabled, backend.web.budgets.enabled, app.web-platform.durable-operations.enabled는 MasterSwitch와 env-keys.yaml 341개 키에 포함되지 않는다. 이 경계는 같은 분석의 §4.1b에서 별도 finding으로 다룬다.