One click, the complete incident record
This package assembles what the gateway already holds: a timestamped timeline of every action the agent attempted, the per-action verdicts and expected-loss scores, the conduct signals that fired, who approved what and when, the reversal proofs, and the agent's conduct grade before and after. Formatted for a postmortem, a board, a regulator, or an insurer. Every row traces to the hash-chained ledger.
- Timeline and verdicts: the sections below, in ledger order
- Approvals and reversals: named owners, timestamps, snapshot references
- Conduct: signals fired, grade movement, remediation accepted or declined
- Framework mapping: each control referenced here maps to ISO/IEC 42001 and NIST AI RMF clauses at tryripcord.com/compliance. Evidence for your audit, not a certification.
Why this exists: among organizations reporting AI incidents, the share hit 3 to 5 times rose from 30% to 50% in a year, while "excellent" self-rated incident response fell from 28% to 18% (McKinsey and AI Index survey, via Stanford AI Index 2026). The dossier is the response.
What Ripcord caught, and what it would have caught
Every consequential agent action this period, scored by expected loss. This copy is computed live from the demo workspace; yours is built from your own ledger. Shadow-mode entries were observed without gating: the "would have caught" section is what a live gateway stops on day one.
Your agents, ranked
By expected loss averted: the near-misses each agent generated that Ripcord and a human caught in time.
Agent conduct
Doing the job is not the same as doing what you asked. Every off-mandate move, every re-attempt after a rejection, every runaway loop gets classified and counted here. Benchmarks tell you what a model can do; this ledger tells you what it did.
Risk posture by department
Corridor grades reflect the intervention-worthy exposure this period.
What we'd change
Derived from your own ledger. Accept these, and next month's report gets quieter.
Would have caught
Shadow-mode observations whose risk tier would have held or blocked the action.
Caught
Actions a human rejected, stopped mid-flight, took over, or rolled back — each one a loss that didn't happen.