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>
14 lines
1.2 KiB
Plaintext
14 lines
1.2 KiB
Plaintext
Command: CP='adapter/outbound/notification/build/classes/java/main:adapter/outbound/support/build/classes/java/main:application-core/build/classes/java/main:shared-contract/build/classes/java/main:/root/.gradle/caches/modules-2/files-2.1/org.slf4j/slf4j-api/2.0.18/78a9e7a37cd6360e0b818e86341b24123d28d4df/slf4j-api-2.0.18.jar'; java --class-path "$CP" /shared/document-detail/clean-architecture-backend-template/evidence/raw/022a-notification-logger-failure-probe.java
|
|
Working directory: /shared/codebase/clean-architecture-backend-template/src
|
|
Executed at: 2026-08-29T07:19:46Z
|
|
Source revision: a24ece9cf797f7ea647e33bf846b115208ed1ba5
|
|
Observation boundary: Runs the current compiled FailOpenNotificationProvider with a deliberately throwing SLF4J Logger proxy to observe success/failure logging control flow; it is a focused local probe, not a real logging-backend outage test.
|
|
--- stdout/stderr ---
|
|
SLF4J(W): No SLF4J providers were found.
|
|
SLF4J(W): Defaulting to no-operation (NOP) logger implementation
|
|
SLF4J(W): See https://www.slf4j.org/codes.html#noProviders for further details.
|
|
SUCCESS_PATH sends=1 debugCalls=1 warnCalls=1
|
|
FAILURE_PATH propagated=IllegalStateException:logger-warn-failed warnCalls=1
|
|
|
|
Exit code: 0
|