Files

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

2.0 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

messaging-policy-c07

발행 경로는 프로덕션에서 실제로 조립된다

delivery-and-settlement-models

clean-architecture-backend-template

게시 전

21234e38cdb9a926cbc92bb97a2aee2e4a7d2916

concept:messaging-policy-c07

2026-09-01

key	file
messaging-policy-c07	../../../final/evidence/rendered/messaging-policy-c07.svg

../../../final/evidence/raw/messaging-policy-c07.txt

원본 분석 절은 analysis/messaging/messaging-policy.md#L603 이다.

messaging-policy

발행 경로는 프로덕션에서 실제로 조립된다

DefaultMessagePublisher MessagingCoreAutoConfiguration.java:446 TransportMessagingRuntime MessagingCoreAutoConfiguration.java:476 DefaultRetryDecisionEngine MessagingCoreAutoConfiguration.java:168 DeadLetterOrchestrator MessagingCoreAutoConfiguration.java:180

관계

구성 오류는 한 예외 타입과 안정 코드로 보고한다 같은 분석 리프에서 끌어낸 규칙이다.
저장소 밖 문서를 절 번호로 인용하지 않는다 같은 분석 리프에서 끌어낸 규칙이다.
부팅 경로의 알고리즘 복잡도는 문서화한다 같은 분석 리프에서 끌어낸 규칙이다.

본문

네 타입이 프로덕션 auto-configuration 안에서 생성된다.

타입	생성 지점
`DefaultMessagePublisher`	`MessagingCoreAutoConfiguration.java:446`
`TransportMessagingRuntime`	`MessagingCoreAutoConfiguration.java:476`
`DefaultRetryDecisionEngine`	`MessagingCoreAutoConfiguration.java:168`
`DeadLetterOrchestrator`	`MessagingCoreAutoConfiguration.java:180`

이 기록이 다루는 범위

:::evidence key="messaging-policy-c07" alt="코드베이스에서 파일 목록을 만든 출력 25줄. 이 기록이 다루는 범위가 그 목록이다." caption="코드베이스 파일 목록 — 25줄 · exit 0" zoom="true" :::

2.0 KiB Raw Blame History

발행 경로는 프로덕션에서 실제로 조립된다

관계

본문

이 기록이 다루는 범위

2.0 KiB

Raw Blame History