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>
This commit is contained in:
DongHyeonka
2026-09-04 22:51:59 +09:00
co-authored by Claude Opus 5
parent 43bccd08a8
commit b2963105a8
5017 changed files with 372751 additions and 4943 deletions
@@ -3,7 +3,8 @@ id: 08a74b35-10c3-4874-8fbc-209b0b6e942e
kind: PROJECT_DECISION
slug: batch-fetch-for-entity-graph
title: Entity Graph 조회에는 Batch Fetch를 사용한다
topic: JPA 피드 조회 성능
topic: jpa-feed-query-performance
topicName: JPA 피드 조회 성능
project: Liner N + 1문제
status: 게시 전
studio: "https://hyeonworks.com/studio/documents/08a74b35-10c3-4874-8fbc-209b0b6e942e/edit"
@@ -3,7 +3,8 @@ id: 7f248f68-ce2b-43ec-94ce-82324d0bd1a7
kind: PROJECT_DECISION
slug: keep-read-model-as-cqrs-lite
title: 현재 Read Model은 CQRS-lite로 유지한다
topic: JPA 피드 조회 성능
topic: jpa-feed-query-performance
topicName: JPA 피드 조회 성능
project: Liner N + 1문제
status: 게시 전
studio: "https://hyeonworks.com/studio/documents/7f248f68-ce2b-43ec-94ce-82324d0bd1a7/edit"
@@ -3,7 +3,8 @@ id: 1dbce381-f0dc-4d49-ad68-bd31d205677e
kind: PROJECT_DECISION
slug: keyset-for-feed-pagination
title: Feed Pagination은 Keyset을 사용한다
topic: JPA 피드 조회 성능
topic: jpa-feed-query-performance
topicName: JPA 피드 조회 성능
project: Liner N + 1문제
status: 게시 전
studio: "https://hyeonworks.com/studio/documents/1dbce381-f0dc-4d49-ad68-bd31d205677e/edit"
@@ -3,7 +3,8 @@ id: ae6c9bea-d3a3-46e1-bbd4-8d580d336394
kind: PROJECT_DECISION
slug: measure-plan-on-real-postgresql
title: Query Plan은 실제 PostgreSQL에서 측정한다
topic: JPA 피드 조회 성능
topic: jpa-feed-query-performance
topicName: JPA 피드 조회 성능
project: Liner N + 1문제
status: 게시 전
studio: "https://hyeonworks.com/studio/documents/ae6c9bea-d3a3-46e1-bbd4-8d580d336394/edit"
@@ -3,7 +3,8 @@ id: 5e4d033c-d6fe-4257-a4dc-1ade44473c72
kind: PROJECT_DECISION
slug: no-collection-fetch-join-with-pagination
title: Collection Fetch Join과 Pagination을 같이 사용하지 않는다
topic: JPA 피드 조회 성능
topic: jpa-feed-query-performance
topicName: JPA 피드 조회 성능
project: Liner N + 1문제
status: 게시 전
studio: "https://hyeonworks.com/studio/documents/5e4d033c-d6fe-4257-a4dc-1ade44473c72/edit"
@@ -3,7 +3,8 @@ id: 4e3200c8-eff5-4442-ae84-ae7b7fa92c8b
kind: PROJECT_DECISION
slug: query-strategy-behind-port
title: Query Strategy는 FeedQueryPort 뒤에서 소유한다
topic: JPA 피드 조회 성능
topic: jpa-feed-query-performance
topicName: JPA 피드 조회 성능
project: Liner N + 1문제
status: 게시 전
studio: "https://hyeonworks.com/studio/documents/4e3200c8-eff5-4442-ae84-ae7b7fa92c8b/edit"
@@ -3,7 +3,8 @@ id: 30a37f34-b406-4061-b924-e22e0be0c3bf
kind: PROJECT_DECISION
slug: read-projection-for-screen-query
title: 화면 조회는 Read Projection을 사용한다
topic: JPA 피드 조회 성능
topic: jpa-feed-query-performance
topicName: JPA 피드 조회 성능
project: Liner N + 1문제
status: 게시 전
studio: "https://hyeonworks.com/studio/documents/30a37f34-b406-4061-b924-e22e0be0c3bf/edit"