donghyeon.kang/document-haness
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Files
9d2a3725c5fbd86ad33e15e924c04a6aa3240ae3
document-haness/docs/clean-architecture-backend-template/tech-log-studio/schema-and-wire-models/concept/concept-adapter-outbound-messaging-c01.md
T
DongHyeonkaandClaude Opus 5 b2963105a8 docs(keycloak-session-store): import the session-storage lab as a new project 
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>
2026-09-04 22:51:59 +09:00

3.7 KiB
Raw Blame History

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-messaging-c01 구성이 끝난 뒤에는 스키마를 가져올 방법이 남아 있지 않다 schema-and-wire-models clean-architecture-backend-template 게시 전 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916 concept:adapter-outbound-messaging-c01 2026-09-01
key file
adapter-outbound-messaging-c01 ../../../final/evidence/rendered/adapter-outbound-messaging-c01.svg
key file
adapter-outbound-messaging-c01-diagram ../../../final/assets/diagrams/adapter-outbound-messaging-c01.svg
../../../final/evidence/raw/adapter-outbound-messaging-c01.txt
원본 분석 절은 analysis/12-adapter-outbound-messaging.md#L174 이다.
adapter-outbound-messaging

구성이 끝난 뒤에는 스키마를 가져올 방법이 남아 있지 않다

LocalJsonSchemaRegistry의 닫힘이 어휘·키워드·참조·메타스키마 권위 네 겹으로 표현되고, 매니페스트 핀이 실제 파일을 가리키는 것까지 probe로 확인했다.

본문

LocalJsonSchemaRegistry의 한 줄 요약이 계약이다 — "Immutable, startup-compiled Draft 2020-12 registry backed only by explicitly supplied bytes. Every reference is checked before NetworkNT compilation. After construction this type exposes no loader, URL, file or classpath fetch operation."

레지스트리가 닫힌 방식

:::evidence key="adapter-outbound-messaging-c01-diagram" alt="넘겨받은 바이트와 동봉된 메타스키마와 허용 어휘가 레지스트리 안에 놓이고 원격 참조 로더와 동적 키워드가 바깥에 빗금으로 놓인다" caption="레지스트리가 닫힌 방식" zoom="false" :::

닫힘이 네 겹으로 표현된다

  1. 어휘 allowlist — KNOWN_VOCABULARIES 8종(core·applicator·unevaluated·validation·meta-data·format-annotation·format-assertion·content) 밖의 $vocabulary 항목은 거부된다.
  2. 키워드 부분집합 — $anchor·$dynamicRef·$dynamicAnchor·$recursiveRef·$recursiveAnchor 다섯이 UNSUPPORTED_CLOSED_SUBSET_KEYWORDS로 문서 어디에서든 거부된다(test rejectsDynamicRecursiveAndAnchorKeywordsEverywhereInTheClosedSubset).
  3. 참조 사전 검사 — validateAllReferences가 NetworkNT 컴파일 전에 모든 $ref를 확인하고, 원격 참조와 설정된 깊이를 넘는 참조 그래프를 거부한다.
  4. 핀 고정된 메타스키마 권위 — 9개 Draft 2020-12 메타 문서를 리소스로 동봉하고 authority.sha256 매니페스트로 해시를 고정하며, 도메인 분리 상수(ca-skeleton.messaging.draft-2020-12-authority.v1)를 섞는다. 매니페스트는 UTF-8 디코딩을 REPORT 모드로 읽어 잘못된 바이트를 조용히 대체하지 않는다.

핀이 실제 파일을 가리키는지 실행해서 봤다

동봉된 9개 파일의 SHA-256이 authority.sha256의 아홉 줄과 전부 일치한다(178-... §8.3).

LocalJsonSchemaRegistry 참조 위치

:::evidence key="adapter-outbound-messaging-c01" alt="코드베이스에서 LocalJsonSchemaRegistry 를 검색한 출력 37줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="LocalJsonSchemaRegistry 코드베이스 검색 — 37줄 · exit 0" zoom="true" :::

식별자는 정확한 URN 스킴만 받는다

$id는 정확한 URN 스킴만 허용하고(acceptsOnlyExactUrnSchemeForRootIdentifiersAndAbsoluteReferences), 중첩 $id는 상대·절대 어느 쪽도 허용하지 않으며 값 타입과 무관하게 키 자체를 거부한다(rejectsNestedSchemaIdentifierKeysRegardlessOfValueType).

Reference in New Issue View Git Blame Copy Permalink