Part 7 of 12 · 1 min read
Accountability and escalation: rules to follow
- Name an owner for every agent and every high-risk action (a RACI), including who can approve, who is on call and who may stop it.
- Log consequential decisions in an append-only, tamper-evident store with a fixed schema; keep an anchor elsewhere; verify on a schedule.
- Do not log raw secrets or unnecessary personal data; set retention (module 6).
- Write severity definitions and response times in advance, with irreversibility and reach as inputs.
- Use rule-based escalation triggers (value limits, domains, repeated denials) for the high-stakes cases; use model judgement for extra caution only.
- Escalate through different people, with timeouts, and test the paging path.
- Install a kill switch that cuts tool access, not just the chat, and require a named human to reset it.
- Set breaker thresholds from baselines and review false trips.
- Run incident reviews (blameless, with fixes) and feed them into evals and red-team suites (modules 8 and Level 9).
- Rehearse: game days that practise the page, the kill switch and the audit query.