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>
4.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-notification-c01 | 이름 없던 상태에 이름을 붙인 세 자리 | composition-and-lifecycle-models | clean-architecture-backend-template | 게시 전 | 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 | concept:adapter-outbound-notification-c01 | 2026-09-01 |
|
|
|
adapter-outbound-notification |
이름 없던 상태에 이름을 붙인 세 자리
세 클래스가 각각 이전에는 구분되지 않던 두 상황을 구분한다 — 공급자가 없는 플랫폼, 알 수 없는 공급자 타입, 그리고 능력별로 필요한 비밀 키.
본문
세 클래스가 각각 이전에는 구분되지 않던 두 상황을 구분한다.
이름 없던 상태에 이름 붙이기
:::evidence key="adapter-outbound-notification-c01-diagram" alt="이전과 지금 두 열에 세 상태가 같은 높이로 놓이고 이전 쪽 세 상자만 빗금으로 표시된 구조" caption="이름 없던 상태에 이름 붙이기" zoom="false" :::
NotificationPlatformMode — 공급자가 하나도 조립되지 않은 플랫폼이 공급자가 있는 플랫폼과 똑같이 보였다.
"A platform with no assembled provider used to look identical to one with providers: the same beans, the same scheduler, the same readiness. Requests were accepted durably and then sat in the queue with no eligible route. Naming the state makes it a decision an operator takes rather than a situation they discover."
INGEST_ONLY는 명시적으로 선택해야 하고("A deployment that reaches zero providers by accident is a misconfiguration, and the whole point of this enum is that the two are told apart"), NotificationProviderAssembly:183이 그것을 강제한다 — 경로가 비었는데 모드가 INGEST_ONLY가 아니면 조립을 거부하고 메시지로 그 모드를 안내한다.
NotificationPlatformMode 참조 위치
:::evidence key="adapter-outbound-notification-c01" alt="코드베이스에서 NotificationPlatformMode 를 검색한 출력 23줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="NotificationPlatformMode 코드베이스 검색 — 23줄 · exit 0" zoom="true" :::
app-bootstrap 쪽에서도 NotificationPlatformWorkerConfig가 "everything that starts a thread, and therefore everything INGEST_ONLY must not have"를 그 모드로 가른다.
자유 문자열이던 타입이 닫힌 enum이 됐다
ProviderType — 설정이 타입을 자유 문자열로 날랐고 "the only thing that read it was a" 비교였다. 지금은 닫힌 enum이라 알 수 없는 타입이 startup 바인딩 실패가 되고 채널도 타입에서 유도된다.
여덟 키를 항상 요구하던 것이 잘못된 방향이었던 이유
NotificationSecretRequirements — 이전에는 여덟 개 키를 항상 요구했다.
"That is fail-closed in the wrong direction: it made every deployment provision and rotate keys for capabilities it had switched off — a Web Push signing key for a platform with no Web Push profile… and a key that exists but is never used is a key nobody notices leaking. It also made the eight look equally load-bearing."
지금은 네 개(CONTACT_ENCRYPTION·CONTACT_LOOKUP_HMAC·PAYLOAD_ENCRYPTION·PROVIDER_REQUEST_LOOKUP_HMAC)가 모든 모드에 필요하고 — 수용 경로에 있으므로 INGEST_ONLY에서도 필요하다 — 나머지 넷은 능력을 따라간다. 약해지면 안 되는 방향은 명시된다: "a capability that is switched on and whose key is missing still refuses the boot, because the alternative is discovering it on a user's notification."