Files
document-haness/docs/clean-architecture-backend-template/final/evidence/raw/318-kafka-certification-lane-executed.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

38 lines
3.3 KiB
Plaintext

# 주제: 인증 레인과 그 게이트를 실제로 실행했다 — messaging-testkit 문서의 미확인 항목을 닫는다
# revision: 21234e38cdb9a926cbc92bb97a2aee2e4a7d2916
# command: ./gradlew :messaging:messaging-kafka:verifyMessagingCertificationEvidence --console=plain
# exit: 0
> Task :messaging:messaging-kafka:messagingCertificationTest
> Task :messaging:messaging-kafka:verifyMessagingCertificationEvidence
BUILD SUCCESSFUL in 35s
31 actionable tasks: 2 executed, 29 up-to-date
# 레인이 생산한 매니페스트 (build/messaging-certification/broker-certification-evidence.jsonl, 4줄)
{"adapter":"messaging-kafka","brokerImage":"apache/kafka:4.1.0","scenario":"confirm-timeout","testId":"KafkaBrokerCertificationIT#aConfirmThatNeverArrivesIsReportedAsAmbiguousAndTheRecordIsThere","outcome":"AMBIGUOUS","gitCommit":"local","observedAt":"2026-08-31T12:21:34.332358735Z"}
{"adapter":"messaging-kafka","brokerImage":"apache/kafka:4.1.0","scenario":"connection-cut-after-write","testId":"KafkaBrokerCertificationIT#aConnectionCutAfterTheWriteIsReportedAsAmbiguous","outcome":"AMBIGUOUS","gitCommit":"local","observedAt":"2026-08-31T12:21:38.390549137Z"}
{"adapter":"messaging-kafka","brokerImage":"apache/kafka:4.1.0","scenario":"high-latency","testId":"KafkaBrokerCertificationIT#latencyBeyondThePublishDeadlineIsReportedAsAmbiguous","outcome":"AMBIGUOUS","gitCommit":"local","observedAt":"2026-08-31T12:21:25.465977439Z"}
{"adapter":"messaging-kafka","brokerImage":"apache/kafka:4.1.0","scenario":"settlement-lost","testId":"KafkaBrokerCertificationIT#aDeliveryLostBeforeSettlementIsRedelivered","outcome":"REDELIVERED","gitCommit":"local","observedAt":"2026-08-31T12:21:45.488559062Z"}
# 게이트 리포트 (build/reports/messaging-certification-evidence.txt)
scenarios=4 manifest=/…/messaging-testkit/src/main/resources/messaging/broker-certification-evidence.jsonl
# 판정
# 1) messagingCertificationTest 가 실제 apache/kafka:4.1.0 + toxiproxy 컨테이너에 대해 실행되었다.
# 2) verifyMessagingCertificationEvidence 가 생산물과 커밋본을 비교해 통과했다.
# (gitCommit·observedAt 은 정규식으로 제거 후 비교 — 그 설계는 messaging-kafka/build.gradle 에 명시)
# 생산본의 gitCommit 은 "local"(GITHUB_SHA 미설정 시 기본), 커밋본은 e98b56eb.
# 나머지 필드 — adapter, brokerImage, scenario, testId, outcome — 는 4줄 모두 일치했다.
# => **커밋된 인증 매니페스트는 이 revision 에서 레인이 실제로 생산하는 것과 동일하다.**
# analysis/messaging/messaging-testkit.md §16 이 "확인하지 못한 것" 으로 남긴 두 항목
# ("매니페스트 4줄이 실제 실행에서 나왔는지", "게이트가 실제로 도는지")이 여기서 닫힌다.
#
# 3) 5개 시나리오 중 connection-refused 는 여전히 증거가 없다. 이는 결함이 아니라
# CertifiedEvidenceTest 가 명시적으로 단언하는 알려진 gap 이다
# ("a Kafka producer buffers before it learns a connection exists, so this stays unproven").
# 참고: 일반 `test` 레인에는 KafkaBrokerCertificationIT 가 포함되지 않는다.
# command: ./gradlew :messaging:messaging-kafka:test --rerun-tasks (아래 EVD-320)
# 결과 XML 에 KafkaBrokerCertificationIT 가 없다 — excludeTags 'messaging-certification' 대로다.