Files
document-haness/docs/clean-architecture-backend-template/tech-log-studio/state-machines-and-ownership/concept/concept-messaging-schema-protobuf-c02.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

48 lines
1.9 KiB
Markdown

---
kind: CONCEPT
slug: messaging-schema-protobuf-c02
title: 나가는 의존이 하나도 없다
topic: state-machines-and-ownership
project: clean-architecture-backend-template
status: 게시 전
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
rootTreeNode: concept:messaging-schema-protobuf-c02
evidenceCapturedOn: 2026-09-01
assets:
- key: messaging-schema-protobuf-c02
file: ../../../final/evidence/rendered/messaging-schema-protobuf-c02.svg
evidence:
- ../../../final/evidence/raw/messaging-schema-protobuf-c02.txt
source:
- 원본 분석 절은 analysis/messaging/messaging-schema-protobuf.md#L76 이다.
module: messaging-schema-protobuf
---
# 나가는 의존이 하나도 없다
들어오는 것은 셋이고 나가는 것은 없다. 어떤 leaf의 `allowed_dependencies`에도 없고 starter 목록에도 없다.
## 관계
- **검증되지 않는 스키마 파일은 문서임을 파일 안에 적는다**
같은 분석 리프에서 끌어낸 규칙이다.
- **신뢰할 수 없는 입력 쪽 경계를 먼저 테스트한다**
같은 분석 리프에서 끌어낸 규칙이다.
## 본문
<!-- body:start -->
들어오는 것: `messaging-core-api`(api), `messaging-schema-api`(api), `protobuf-java:4.29.3`(api). 나가는 것: **없다.** 어떤 leaf의 `allowed_dependencies`에도 없고 starter 목록에도 없다. 런타임 배선도 없고 bean도 없다(Spring 주석 0개).
## 이 기록이 다루는 파일 범위
:::evidence key="messaging-schema-protobuf-c02" alt="코드베이스에서 파일 목록을 만든 출력 2줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 2줄 · exit 0" zoom="true"
:::
## lockfile이 확인하는 실제 해석
컴파일/런타임은 4.29.3, annotation processor 경로만 4.33.2다. §12.4에서 저장소 전체의 protobuf 버전 지형을 다룬다.
<!-- body:end -->