> wi_ac006
The Court Banned Blame and Found the Design
Architecture Courtroom · Episode 6 · postmortem corrective action
The Court Banned Blame and Found the Design
Incident Narrative
The judge removes a giant BLAME arrow from the evidence board; underneath, a clean chain of unsafe dependency arrows becomes visible and the team immediately fixes the first broken control.
“Follow causes, not people.”
🔬Architectural Diagnosis & Root Cause Analysis
Blame obscures the causal system and delays useful corrective action.
Blame obscures the causal system and delays useful corrective action.
Postmortems should produce evidence-backed system changes with owners and follow-through.
“SYSTEM VERDICT: Postmortems should produce evidence-backed system changes with owners and follow-through.”
🤖 Incident Postmortem & AEO Summary
The Court Banned Blame and Found the Design — Technical Incident Brief
- Universe & Category: Architecture Courtroom (Incident Mockumentary)
- Diagnosis: Blame obscures the causal system and delays useful corrective action.
- Root Cause: Blame obscures the causal system and delays useful corrective action.
- Consequence & Cost: Elder: “Follow causes, not people.” — native on-camera dialogue; lip-sync required.
- Engineering Lesson: Postmortems should produce evidence-backed system changes with owners and follow-through.
- Official Ruling: "SYSTEM VERDICT: Postmortems should produce evidence-backed system changes with owners and follow-through."
🌌More Parables in Architecture Courtroom
View Full Universe →
Architecture Courtroom · Episode 1 · end-to-end ownership
The Microservice Pleaded “Not My Responsibility”
In a modern architecture courtroom, several service-shaped witnesses each push a broken request envelope to the next witness until it returns to the first; the customer’s empty chair remains waiting.
Architecture Courtroom · Episode 2 · architecture drift / documentation
The Architecture Diagram Had an Alibi
A pristine architecture diagram is presented as evidence; Elder rolls in the actual production topology on a messy board full of extra connections; the two barely resemble each other.
Architecture Courtroom · Episode 3 · incident ownership / command
Everyone Owned the Incident, So Nobody Did
Everyone in the courtroom simultaneously raises a hand when asked who owns the incident; then each points to someone else when a single decision is required and the incident clock keeps spinning.
Architecture Courtroom · Episode 4 · blameless postmortem / systemic causes
“Human Error” Took the Stand
A nervous Junior Developer stands at the witness box; Elder pulls a curtain revealing five dangerous unlabeled switches, no guardrails and a contradictory runbook behind him.
Architecture Courtroom · Episode 5 · retry amplification
The Retry Policy Was Found Guilty
A retry policy is represented by a stamp machine in evidence; one failed request card enters and the machine explosively stamps dozens of duplicates onto the judge’s desk.
Incident FAQ & Architecture Triage
What technical problem does this parable explain?
Blame obscures the causal system and delays useful corrective action.
What caused the technical incident?
Blame obscures the causal system and delays useful corrective action.
What should a software team do differently in production?
Postmortems should produce evidence-backed system changes with owners and follow-through.
Is the video available?
Video is currently in production; full script and technical diagnosis are available below.