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>
45 lines
1.9 KiB
Markdown
45 lines
1.9 KiB
Markdown
---
|
|
kind: CONCEPT
|
|
slug: messaging-testkit-c02
|
|
title: 상속하는 쪽이 컴파일되려면 전부 전이되어야 한다
|
|
topic: delivery-and-settlement-models
|
|
project: clean-architecture-backend-template
|
|
status: 게시 전
|
|
sourceRevision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
|
|
rootTreeNode: concept:messaging-testkit-c02
|
|
evidenceCapturedOn: 2026-09-01
|
|
assets:
|
|
- key: messaging-testkit-c02
|
|
file: ../../../final/evidence/rendered/messaging-testkit-c02.svg
|
|
evidence:
|
|
- ../../../final/evidence/raw/messaging-testkit-c02.txt
|
|
source:
|
|
- 원본 분석 절은 analysis/messaging/messaging-testkit.md#L99 이다.
|
|
module: messaging-testkit
|
|
---
|
|
|
|
# 상속하는 쪽이 컴파일되려면 전부 전이되어야 한다
|
|
|
|
여섯 개가 전부 api 다. implementation 이 하나도 없다.
|
|
|
|
## 본문
|
|
|
|
<!-- body:start -->
|
|
|
|
여섯 개가 전부 `api` 다. `implementation` 이 하나도 없다.
|
|
|
|
## MessagingAdapterContract 참조 위치
|
|
|
|
:::evidence key="messaging-testkit-c02" alt="코드베이스에서 MessagingAdapterContract 를 검색한 출력 8줄. 이 기록이 세는 참조가 그 출력에 그대로 보인다." caption="MessagingAdapterContract 코드베이스 검색 — 8줄 · exit 0" zoom="true"
|
|
:::
|
|
|
|
## 이 리프에서는 그것이 옳은 선택이다
|
|
|
|
`MessagingAdapterContract` 는 `@Test` 를 **자기 시그니처에** 달고 있고(`MessagingAdapterContract.java:28`), `ContractAssertions` 는 AssertJ 를 반환 타입 없이 쓰지만 상속받는 쪽이 같은 AssertJ 를 봐야 하며, `MessagingAdapterHarness.publish` 는 `PublishResult`(core-api)를, `ContractMessage` 는 `EncodedMessage`(schema-api)를 **공개 시그니처에** 노출한다.
|
|
|
|
## 빈 membership 의 뜻이 다른 리프들과 정반대다
|
|
|
|
`runtime_memberships: []` 이지만 §12.1 의 판정은 다른 `[]` 리프들과 정반대다. 추가로 `messaging-kafka/build.gradle:91` 이 이 리프의 **리소스 파일 경로를 문자열로 참조**한다(§4.3).
|
|
|
|
<!-- body:end -->
|