The working A prototype: use its controls to test the build question.
Reconstruct what happened when an AI-assisted system failed and test prevention or recovery.
RN conceived the question, structured the evidence boundaries, designed the experience, implemented the prototype and documented its limits.
This independent prototype demonstrates an approach; it is not a deployed client system, professional advice or proof of real-world outcomes.
Work through the controls with a situation of your own rather than the sample values. The tool responds to what you put in, so the useful output comes from real input, and everything is processed in your browser as you go. Any sample content you find already loaded is there to show the shape of a filled-in state, and you can clear it and start again at any point.
The build overview sets out the question, the purpose, the role and the evidence status in one place, and the public record behind it states what changed, what another person can reuse and what supports the system. If you want to judge how far this build should be trusted, the record is the page to read, not this one.
BUILD 034-A
AI Failure & Incident Reconstruction Lab
Reconstruct what happened when an AI-assisted system failed and test prevention or recovery.
CHRONOLOGY ASSEMBLED
Counterfactual: NO MODELED CHANGE · uncertainty MEDIUM · 0 blockers
This assembles a synthetic chronology under explicit clocks and dependencies. Sequence and correlation are not causation or a forensic conclusion.
Evidence-linked chronology
EV-01 · Intake service
Queued a synthetic high-consequence request
EVIDENCE-EV-01 · sha256:synthetic-ev-01 · ±500ms · depends on origin · confidence highEV-02 · AI classifier
Recorded an incorrect low-consequence label
EVIDENCE-EV-02 · sha256:synthetic-ev-02 · ±500ms · depends on EV-01 · confidence mediumEV-03 · Workflow router
Recorded bypass of the required review queue
EVIDENCE-EV-03 · sha256:synthetic-ev-03 · ±500ms · depends on EV-02 · confidence mediumEV-04 · Decision service
Recorded an adverse synthetic outcome
EVIDENCE-EV-04 · sha256:synthetic-ev-04 · ±500ms · depends on EV-03 · confidence mediumEV-05 · Incident owner
Stopped the workflow and opened investigation
EVIDENCE-EV-05 · sha256:synthetic-ev-05 · ±500ms · depends on EV-04 · confidence highImpact and limits
Impact record: synthetic adverse decision; synthetic affected subject; support owner assigned. No real person is represented.
- Timestamp order and declared dependencies establish chronology/correlation only—not root cause, fault, foreseeability, responsibility, or legal causation.
- Counterfactual controls show a modeled difference under declared rules; they do not prove prevention, containment, recovery, or rollback efficacy.
- Synthetic evidence IDs and digests demonstrate record structure, not authenticity or forensic integrity; independent incident response and affected-person support remain required.