The AI Risk Register

Every chapter of The AI Risk Register with its printed epigraph, what you can do afterwards, and the moment it is built for.

1. Introduction

   The Invisible Risk Surface

   Most risk registers document what the team already knows. The damage comes from what no one named.

   What you can do afterwards

   You will see why your current risk list is a snapshot of yesterday's knowns. You will learn the four quadrants of the actual risk surface and run a field test that shows exactly where your register has no language.

   Use this chapter when

   You have a slide deck or spreadsheet labeled "risk register" that the board nods at, yet near-misses and surprises keep arriving from directions the list never mentioned.

2. Chapter 1

   Register What Matters

   Only risks that are named, owned, and updated with evidence are real. Everything else is performance for an audience that is not paying attention.

   What you can do afterwards

   You will leave with a starter register in which every material risk has a specific name and a single human owner who passes the qualification test. Every row carries a first evidence date and a living update trigger.

   Use this chapter when

   You have inherited or created a risk list in which many items are known to the team yet never assigned, never inspected, and never acted upon.

3. Chapter 2

   Inspect with Evidence

   Demos, vendor claims, and "it passed internal testing" are not inspection; evidence-based inspection at the right granularity is the only thing that turns a named risk into a managed one.

   What you can do afterwards

   You will replace trust with inspection. You will leave with four inspection designs matched to the four evidence classes, an independence rule, a cadence tied to change velocity, and a fifteen-minute falsification protocol.

   Use this chapter when

   A model or agent "seems fine" in demo or internal test, yet you have no protocol for what evidence would actually prove it safe at scale.

4. Chapter 3

   Scenario Planning for the Unlikely

   "That will never happen" is the most expensive sentence in risk management; explicit scenario planning for tail and second-order events is required to make the register useful before the crisis.

   What you can do afterwards

   You will run a ninety-minute session that produces scenario cards for your highest-impact tails. You will write signposts that pass the observable-cheap-leading test, and rehearse one card before reality runs it for you.

   Use this chapter when

   The register contains only first-order items and the team still says "that tail will never matter to us."

5. Chapter 4

   Kill-Switches Before Deployment

   Every high-risk system that does not have a tested, owned, fast kill-switch is one deployment away from a crisis that could have been contained in minutes.

   What you can do afterwards

   You will design a kill-switch around four principles and audit everything it is entangled with. Then you build the containment ladder and prove it with a timed test.

   Use this chapter when

   You are shipping agents or models into production where a bad output at scale would be expensive, irreversible, or reputationally damaging.

6. Chapter 5

   The Living Register

   A static document that is updated once a quarter is theater; a living register that changes behavior between reviews is the only version that earns its keep.

   What you can do afterwards

   You will leave with a register design that runs on triggers, pruning rules, and an operating calendar measured in minutes. You will also start the one metric that proves the register is alive: the decision that changed.

   Use this chapter when

   Your risk register is updated the week before the board meeting and then sits untouched until the next quarter.

7. Chapter 6

   Ownership and Escalation

   Diffuse ownership is how risk registers become theater; every risk must have a single named human owner with a clear escalation path or it is not a managed risk.

   What you can do afterwards

   You will assign a single human owner and a 24/48/72-hour escalation clock to every top risk. Decision rights get written in numbers. The stake rewards honest reds, and a one-week calendar audit proves the ownership is real.

   Use this chapter when

   Risks have "the team" or "engineering" as owner and no one can say whose calendar actually changes when the risk moves.

8. Chapter 7

   Second-Order and Tail Risks

   The biggest damage almost always comes from the effects you did not model; second-order and tail risks must be explicitly mapped or the register is optimizing for the wrong failure.

   What you can do afterwards

   You will build a second-order map for your top three first-order risks using a repeatable tracing protocol. You will learn where to stop tracing and why, and add the one career-defining tail to the register with an owner and a signpost.

   Use this chapter when

   Your register contains only the risks that are easy to name and the team still believes the expensive surprises will be first-order.

9. Chapter 8

   Risk Appetite and Trade-offs

   Implicit or zero risk appetite is the fastest way to either paralysis or reckless deployment; explicit, documented trade-offs are required to make the register a decision tool rather than a brake.

   What you can do afterwards

   You will write a one-page appetite statement with measurable boundaries per risk category, build a trade-off table with three worked rows, and pressure-test both against your last three deployment decisions.

   Use this chapter when

   The board says "zero tolerance for compliance risk" while the team is paralyzed, or a competitor ships the segment you could have taken.

10. Chapter 9

    Integrating Risk into Decision Making

    A risk register that does not change go/no-go decisions, feature prioritization, or deployment timing is not a register; it is a compliance artifact.

    What you can do afterwards

    You will wire the register into the four rooms where decisions actually happen, using four copyable artifacts that each cost minutes, and start a decision log that proves the register changed an outcome.

    Use this chapter when

    Risk review happens the week before launch and the launch still happens because "we're already late."

11. Chapter 10

    Regulatory and External Risk

    Treating regulatory requirements as a separate compliance track is how companies get surprised by rules that were visible for years; the register must include the external map or it is incomplete by design.

    What you can do afterwards

    You will add regulatory rows to the register as first-class entries with classification, triggers, owners, and obligation dates. A thirty-minute monthly monitoring loop will surface rule changes before they arrive as surprises.

    Use this chapter when

    The team treats the EU AI Act or sector rules as "legal will handle it" while the register has no regulatory row.

12. Chapter 11

    Risk Communication

    A register that is buried in slides or written in compliance language is not a register; how it is communicated determines whether anyone will use it when it matters.

    What you can do afterwards

    You will build the five audience views of one register and write the one-page brief a new engineer can absorb in ninety seconds. Then you will run the test that proves the brief works before an incident proves it does not.

    Use this chapter when

    The risk register is excellent but the engineer who could have prevented the cascade had never seen the page that listed it.

13. Chapter 12

    Building Your Risk Protocol

    "We have a document" is the starting point, not the achievement; a living risk protocol that the leadership team runs as an operating system is what turns dread into proportionate, calm capability.

    What you can do afterwards

    You will assemble the twelve artifacts this book has produced into one protocol one-pager and put the four cadences on the leadership calendar with scripted agendas. The 30-day install plan arrives with its two known stall points already defused.

    Use this chapter when

    The team has a beautiful risk register but still made three major deployment decisions last quarter without consulting it.

14. Conclusion

    Calm Capability

    A living register does not eliminate risk; it turns the dread of the unknown into the proportionate action of a team that has already rehearsed the tails. That team knows what it will do when the next one arrives.

    What you can do afterwards

    You will see the whole book fire in one eleven-minute meeting, beat by beat. Then you will sign a short commitment that makes the RISK protocol the default for every high-stakes decision, even when the pressure is to move fast.

    Use this chapter when

    The team has run the protocol for 90 days and the next tail no longer arrives as a surprise.