DongHyeonkaandClaude Opus 5
b2963105a8
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>
15 lines
1.9 KiB
JSON
15 lines
1.9 KiB
JSON
{
|
|
"assetKey": "a19-f014-kafka-msg-probe",
|
|
"kind": "terminal",
|
|
"command": "#!/bin/bash\nset -u\ncd /tmp/probe\nCP=$(cat /tmp/probe-cp.txt)\njava -Dfile.encoding=UTF-8 -Dsun.stdout.encoding=UTF-8 -cp \".:$CP\" MessagingGateProbe > /tmp/probe/out.txt 2>/dev/null\n\necho \"# 출하 컴포지션 루트를 세 조합으로 기동한 결과\"\necho \"# ShippedCompositionHarness.shippedComposition(\\\"local\\\") 에\"\necho \"# requiredOperatorInputs + allOffArguments 를 준 뒤 조합별로 덮어썼다\"\necho\ngrep -E '^#####|^ (기본 인자|덮어쓴 인자|결과)|^ (맨 위 예외|실패한 빈|맨 아래 예외|없는 것)' /tmp/probe/out.txt\n\necho \"# C3 에서 실제로 만들어진 KafkaProducer 의 설정\"\ngrep -E '^\t(bootstrap\\.servers|client\\.id|key\\.serializer|value\\.serializer|security\\.protocol|acks) ' /tmp/probe/out.txt \\\n | sed 's#^\\t# #'\nn=$(grep -c 'client\\.id = producer' /tmp/probe/out.txt || true)\necho \" 세 조합을 통틀어 만들어진 KafkaProducer 수 : ${n:-0}\"\necho\necho \"# 세 조합에서 공통으로 마지막에 남는 실패\"\necho \" 이 프로브의 클래스패스에는 app-bootstrap 시험 출력이 함께 있어\"\necho \" Spring Data JPA 저장소 스캔이 켜지고 entityManagerFactory 부재로 끝난다.\"\necho \" C2 의 kafkaSeamProducer 실패는 그보다 먼저 난다.\"\ngrep -c \"A component required a bean named 'entityManagerFactory'\" /tmp/probe/out.txt \\\n | sed 's#^# entityManagerFactory 로 끝난 조합 수 : #'\n",
|
|
"cwd": "/tmp/probe",
|
|
"exitCode": 0,
|
|
"executedAt": "2026-09-04T01:35:45+00:00",
|
|
"sourceRevision": "21234e38cdb9a926cbc92bb97a2aee2e4a7d2916",
|
|
"raw": "evidence/raw/a19-f014-kafka-msg-probe.txt",
|
|
"svg": "evidence/rendered/a19-f014-kafka-msg-probe.svg",
|
|
"rawSha256": "fc3df07e10f2ac8e997ec6e4d3a8d0ab4a819924d48297fd755a309b2b5a19e5",
|
|
"lines": 43,
|
|
"redaction": "비밀값 없음"
|
|
}
|