Files
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

66 lines
4.2 KiB
Plaintext

# 주제: 같은 블록의 규칙 엔진 두 개 중 하나는 커밋된 실제 입력을 먹고, 하나는 먹지 않는다
# revision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
# ---- 먹는 쪽: grpc-proto-contract ----
# 커밋된 스키마 리소스 5개:
# src/grpc/grpc-proto-contract/src/main/resources/proto/buf.yaml
# …/proto/buf.gen.yaml
# …/proto/buf.lock
# …/proto/hyeonworks/grpc/common/v1/error.proto
# …/proto/hyeonworks/grpc/common/v1/stream.proto
#
# GrpcProtoContractValidatorTest 가 그것을 읽는다:
# :20-24 private static String committedSchema(String resourcePath) {
# …getClassLoader().getResourceAsStream(resourcePath)
# if (null) throw new IllegalStateException("missing committed schema resource: " + …)
# :37-38 committedSchema("proto/hyeonworks/grpc/common/v1/error.proto")
# committedSchema("proto/hyeonworks/grpc/common/v1/stream.proto")
# :53-55 committedSchema("proto/buf.yaml") / buf.gen.yaml / buf.lock
# :61-62 .contains("build/generated/source/proto/main/java")
# .contains("build/generated/source/proto/main/grpc")
# => 규칙 엔진(GrpcProtoContractValidator, 605 LOC 중 대부분)이
# **이 저장소가 실제로 커밋한 스키마**에 대해 실행된다.
# 리소스가 없으면 테스트가 IllegalStateException 으로 실패한다 — 조용한 skip 이 아니다.
# ---- 먹지 않는 쪽: grpc-server ----
# EVD-328 참조. GrpcApplicationBoundaryRules / GrpcRawApiImportRule 은
# 저장소 소스를 한 번도 입력으로 받지 않고, 테스트가 합성 문자열을 넘긴다.
# ---- 같은 판단이 build.gradle 에 적혀 있다 ----
# grpc-codegen/build.gradle:4-7
# "The Buf rules are implemented here rather than shelled out to the Buf CLI (adaptation D5): the
# CLI is not present in this toolchain, and **a gate that silently no-ops when a binary is
# missing is worse than one that computes the same judgement from the committed schema.**"
# grpc-proto-contract/build.gradle:3-9
# "No protobuf plugin and no protoc invocation here … The validator reads `.proto` text and
# enforces the Stable style manifest (proto3 + explicit optional, package versioning, reserved
# history, enum zero suffix, WKT allowlist), which is the invariant the plan owns; running protoc
# is a separate, gated decision."
# => "조용히 no-op 하는 게이트보다 커밋된 스키마로 같은 판단을 계산하는 게이트가 낫다" 는 원칙이
# proto-contract·codegen 에는 적용되었고 server 의 경계 규칙에는 적용되지 않았다.
# ---- 저장소의 .proto 전수 (4개) ----
# grpc-proto-contract/src/main/resources/proto/hyeonworks/grpc/common/v1/stream.proto
# grpc-proto-contract/src/main/resources/proto/hyeonworks/grpc/common/v1/error.proto
# grpc-advanced-edition/src/main/resources/proto/edition2024/compatibility.proto
# messaging-schema-protobuf/src/test/proto/order_created_v1.proto
# => 서비스 정의(.proto with `service`)가 없다. 공통 타입 두 개와 호환성 시험용 하나뿐이다.
# grpc-codegen 이 관리하는 "생성 소유권" 의 대상이 아직 없다는 뜻이다.
# ---- grpc-codegen 의 소비자 컴파일 게이트 픽스처 ----
# src/grpc/grpc-codegen/src/test/resources/consumer-fixtures/v1/build.gradle.kts
# src/grpc/grpc-codegen/src/test/resources/consumer-fixtures/v1/src/main/java/fixture/DocumentClientFixture.java
# => 소비자가 새 스키마로 컴파일되는지를 검사하는 픽스처가 실재한다.
# ---- 네 리프 도달성 ----
GrpcReflectionPolicy 다른리프=1 src/main생성=3
GrpcKubernetesProfile 다른리프=0 src/main생성=3
GrpcSchemaArtifactPublisher 다른리프=2 src/main생성=0
GrpcServiceHealthRegistry 다른리프=1 src/main생성=1
GrpcBufPolicy 다른리프=0 src/main생성=1
GrpcConsumerFixture 다른리프=0 src/main생성=1
GrpcDiscoveryPolicyValidator 다른리프=1 src/main생성=0
GrpcDrainCoordinator 다른리프=0 src/main생성=0
GrpcPlatformSnapshotService 다른리프=0 src/main생성=0
GrpcProtoContractValidator 다른리프=0 src/main생성=0