Appeals backlog triggers unnoticed harm loops
A surge in appeal volume stalled remedies, leaving account holders in unresolved states for weeks.
- Drawn from: financial services
Failure patterns, each drawn from many systems
These are composites. None reports on a named institution or a dated event. Each names the control that was missing, the signal that would have shown it, and the fix. For failures a court, an inquiry, or a regulator established, see the casebook.
Composite scenarios
The patterns
Each card names the setting the pattern is drawn from. The scenario page holds the missing controls and the fixes.
Model overrides happened without audit trace
Human overrides removed automated denials, but the rationale was never logged for later audit review.
- Drawn from: public benefits
Appeal accepted without remedy follow-through
Appeals were marked resolved, but the remedies they granted never reached the teams responsible for delivering them.
- Drawn from: healthcare
Post-market monitoring
Incident reporting workflow
The stages from intake to closure, each with the record it must produce.
- Intake: Record the incident class, severity, affected parties, and owner when the incident is opened.
- Triage: Apply halt or degrade decisions and publish expected next update time.
- Remediation: Link fix actions to evidence artifacts and restoration targets.
- Regulatory reporting: Export regulator-ready summary with timeline, controls, and attachments.
- Closure and learning: Record closure decision, residual risk, and prevention commitments.
Machine-readable workflow objects are available at /api/post-market-monitoring.json.