Deterministic presets · no random failures
Failure Theatre
Failure is part of the architecture. Choose an authored fault, inspect exactly where processing stops, change one explicit condition, then replay only the failed hop. No points. No confetti. The failed evidence remains.
- 01 Stops at · client registryOpen scenario →
Two people look alike to the matcher
Two distinct synthetic people share a name and birth date, so automatic linkage stops.
- 02 Stops at · client registryOpen scenario →
No enterprise identity exists yet
The Client Registry returns no candidate and refuses to create one silently.
- 03 Stops at · terminology serviceOpen scenario →
Meaning cannot be guessed
This deterministic run selects the inactive LUM-HB-OLD subcase; the same rule also holds unknown, inexact, and one-to-many codes before normalization.
- 04 Stops at · terminology serviceOpen scenario →
The terminology dependency is unavailable
A simulated 503 triggers bounded deterministic retry and then dead-letter.
- 05 Stops at · iolOpen scenario →
The commit succeeds but its acknowledgement is lost
The SHR has committed the result, but the sender cannot yet distinguish success from loss.
- 06 Stops at · iolOpen scenario →
A processed event is submitted again
A duplicate logical event reaches the exchange with the same idempotency key.
- 07 Stops at · authenticationOpen scenario →
The sending system cannot authenticate
An expired synthetic sender credential is rejected before downstream routing.
- 08 Stops at · policyOpen scenario →
Policy does not permit disclosure
The toy policy engine returns deny and the SHR remains outside the route.
- 09 Stops at · interlinkingOpen scenario →
The authoritative directory says the actor is inactive
An inactive facility or unlinked worker fails the named toy trust policy.
- 10 Stops at · iolOpen scenario →
The illustrative payload does not satisfy its schema
A required field is missing from demo-clinic-v1 and validation stops the transaction.
- 11 Stops at · shared health recordOpen scenario →
A later result amends an earlier version
Result source version 2 arrives after source version 1 and must preserve history.
- 12 Stops at · hmisOpen scenario →
The aggregate export is late
Clinical commit succeeds while the asynchronous HMIS path is delayed.