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>
13 lines
2.1 KiB
Plaintext
13 lines
2.1 KiB
Plaintext
./messaging/messaging-testkit/src/test/java/dev/caskeleton/messaging/testkit/InMemoryMessagingHarness.java:36: private final Faults faults = new Faults();
|
|
./messaging/messaging-testkit/src/test/java/dev/caskeleton/messaging/testkit/InMemoryMessagingHarness.java:203: private static final class Faults implements FaultController {
|
|
./messaging/messaging-rabbit/src/test/java/dev/caskeleton/messaging/rabbit/RabbitContractHarness.java:47: private final Faults faults = new Faults();
|
|
./messaging/messaging-rabbit/src/test/java/dev/caskeleton/messaging/rabbit/RabbitContractHarness.java:247: private static final class Faults implements FaultController {
|
|
./messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaContractHarness.java:87: private final Faults faults = new Faults();
|
|
./messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaContractHarness.java:313: private static final class Faults implements FaultController {
|
|
./messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaBrokerCertificationIT.java:70: * <p>Faults are injected with Toxiproxy in front of the broker rather than by pausing the
|
|
./messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaBrokerCertificationIT.java:156: void clearInjectedFaults() throws IOException {
|
|
./messaging/messaging-kafka/src/test/java/dev/caskeleton/messaging/kafka/KafkaBrokerCertificationIT.java:226: clearInjectedFaults();
|
|
./adapter/inbound/websocket/src/test/java/dev/caskeleton/adapter/inbound/websocket/release/WebSocketNginxProxyProfileTest.java:23: void compliantProfileHasNoFaults() {
|
|
./adapter/outbound/fileserver/src/test/java/dev/caskeleton/adapter/outbound/fileserver/LocalPersistentControlPlaneTest.java:168: void contextualFaultsIdentifyRecordBoundaryIdentityAndApplicableOperationRevision()
|
|
./adapter/outbound/persistence-mongo/src/testkit/java/dev/caskeleton/adapter/outbound/mongo/testkit/failover/ToxiproxyMongoNetworkFaultController.java:18: * <p>Faults are injected in the path, not in the server, because the failure that matters cannot be
|