Files
document-haness/docs/clean-architecture-backend-template/final/evidence/raw/analysis-finding-a04-f005.txt
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

97 lines
5.9 KiB
Plaintext

# README 가 적은 세 문장
README.md:7 허용/금지 의존 정책은 `src/build.gradle` 의
README.md:8 `allowedProjectDependencies['adapter:outbound:support']` 항목이 SSOT 다(이 모듈은 아직 별도
README.md:9 CLAUDE.md 를 두지 않았다). 이 문서는 코드 주석에서 덜어낸 **설계 결정의 근거**를 모아둔 참조용
README.md:10 기록이다 — 코드를 읽다 "왜 이렇게 했나"가 궁금할 때 본다.
README.md:11
README.md:20
README.md:21 실패를 ERROR 가 아니라 WARN 으로 로깅한다: cache/messaging/notification 선택형 어댑터는
README.md:22 fail-open 이라 의존성 실패가 나도 use case 는 성공한 것이다 — 관측은 하되 escalate 하지 않는다.
README.md:23 이는 호출자에게 직접 노출되는 hard failure 를 ERROR 로 올리는 `httpclient` 모듈의
README.md:24 `OutboundHttpDependencyLogger` 와 명확히 구분된다. 메서드 시그니처가 본문·수신자·페이로드를
README.md:25 받지 않아 PII 가 로그에 닿지 않는다.
README 의 커밋 이력 :
821fe00c 2026-07-24 init: 클린 아키텍처 백엔드
# 두 파일이 언제 태어났는가
C b3add016 2026-07-28 feat: redis, fileserver, httpclient 런타임 시점 구현 추가
M src/adapter/outbound/support/CLAUDE.md
C 821fe00c 2026-07-24 init: 클린 아키텍처 백엔드
A src/adapter/outbound/support/CLAUDE.md
A src/adapter/outbound/support/README.md
README 가 쓰인 커밋의 레지스트리 위치 :
build.gradle@821fe00c:558 File moduleRegistryFile = new File(rootProject.projectDir.parentFile, '.harness/project/modules.yaml')
modules.json 이 들어온 커밋 :
b3add016 2026-07-28 feat: redis, fileserver, httpclient 런타임 시점 구현 추가
# 1. 의존 정책의 정본이 어디인가
src/build.gradle 에서 그 이름이 나오는 줄 : 3 개 (전부)
src/build.gradle:1419 Map<String, Set<String>> allowedProjectDependencies = registry.modules.collectEntries { module ->
src/build.gradle:1430 Set<String> governedModules = allowedProjectDependencies.keySet()
src/build.gradle:1448 allowedProjectDependencies.each { moduleName, allowed ->
modules.json:41 "id": "adapter-outbound-support",
modules.json:42 "gradle_path": ":adapter:outbound:support",
modules.json:43 "source_path": "src/adapter/outbound/support",
modules.json:44 "allowed_dependencies": [
modules.json:45 "domain-core",
modules.json:46 "application-core",
modules.json:47 "shared-contract"
modules.json:48 ],
modules.json:49 "runtime_memberships": [
modules.json:50 "app-bootstrap"
modules.json:51 ]
modules.json:52 },
# 2. 이 모듈에 CLAUDE.md 가 있는가
src/adapter/outbound/support/CLAUDE.md
src/adapter/outbound/support/README.md
support/CLAUDE.md:1 # adapter:outbound:support — shared outbound support
support/CLAUDE.md:2
support/CLAUDE.md:3 ## Registered identity
support/CLAUDE.md:4
support/CLAUDE.md:5 - Module ID: `adapter-outbound-support`
support/CLAUDE.md:6 - Gradle path: `:adapter:outbound:support`
support/CLAUDE.md:7 - Focused test (derived from Gradle path): `./gradlew :adapter:outbound:support:test --console=plain`
support/CLAUDE.md:8 - Runtime baseline: Java 21; repository framework baseline: Spring Boot 4.0.0.
support/CLAUDE.md:9 - Registry SSOT: `src/config/architecture/modules.json`.
support/CLAUDE.md:10
CLAUDE.md 의 커밋 이력 :
b3add016 2026-07-28 feat: redis, fileserver, httpclient 런타임 시점 구현 추가
821fe00c 2026-07-24 init: 클린 아키텍처 백엔드
# 3. httpclient 쪽 로거의 이름
OutboundHttpDependencyLogger 를 가진 파일 : 0 개
httpclient main 의 이름에 Logger 가 든 파일 : 0 개
httpclient main 에서 org.slf4j 를 import 하는 파일 : 0 개
httpclient main 의 log.error 호출 : 0 줄
[자기시험] 없는 이름 OutboundHttpDependencyLoggerZZZ : 0 개
[대조] FailOpenDependencyLogger : 12 개
그 이름의 이력 :
C 5f10b791 2026-08-11 chore: record pre-existing uncommitted repository state
D src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/diagnostics/OutboundHttpDependencyLogger.java
D src/adapter/outbound/httpclient/src/test/java/dev/caskeleton/adapter/outbound/httpclient/diagnostics/OutboundHttpDependencyLoggerTest.java
C 821fe00c 2026-07-24 init: 클린 아키텍처 백엔드
A src/adapter/outbound/httpclient/src/main/java/dev/caskeleton/adapter/outbound/httpclient/diagnostics/OutboundHttpDependencyLogger.java
A src/adapter/outbound/httpclient/src/test/java/dev/caskeleton/adapter/outbound/httpclient/diagnostics/OutboundHttpDependencyLoggerTest.java
# 4. README 가 PII 에 대해 적은 것과 로거가 실제로 적는 것
README.md:24 `OutboundHttpDependencyLogger` 와 명확히 구분된다. 메서드 시그니처가 본문·수신자·페이로드를
README.md:25 받지 않아 PII 가 로그에 닿지 않는다.
FailOpenDependencyLogger.java:36 /** WARN: fail-open adapter — the use case still succeeded, so this is not an ERROR. */
FailOpenDependencyLogger.java:37 public void logFailure(
FailOpenDependencyLogger.java:38 String dependencyName, String dependencyType, String operation, Throwable cause) {
FailOpenDependencyLogger.java:39 log.warn(
FailOpenDependencyLogger.java:40 "dependency_name=\"{}\" dependency_type=\"{}\" operation=\"{}\" "
FailOpenDependencyLogger.java:41 + "outcome=\"FAILURE\" correlation_id=\"{}\" error=\"{}: {}\"",
FailOpenDependencyLogger.java:42 dependencyName,
FailOpenDependencyLogger.java:43 dependencyType,
FailOpenDependencyLogger.java:44 operation,
FailOpenDependencyLogger.java:45 OutboundCorrelation.current(),
FailOpenDependencyLogger.java:46 cause.getClass().getSimpleName(),
FailOpenDependencyLogger.java:47 cause.getMessage());
FailOpenDependencyLogger.java:48 }