EP046 · Main episode
Who Owns the AI Incident?
AI incident response needs named authority for classification, containment, evidence, notification, disclosure, recovery, and closure. Build and test an AI Incident Authority Card.
- Published
- Sep 22, 2026
- Runtime
- 20m 51s
- Record
- Source-backed notes
Complete episode file
Notes, chapters, and evidence
The full editorial record lives here. Open only the section you need, without leaving the Desk.
Episode notes6 sections · 3 release notes
Original release summary
- An incident label is not an incident process. Name the classifier, stop authority, evidence custodian, notification owners, and recovery authority.
- A model stopping itself does not establish that an independent organizational stop control worked.
- Run a 45-minute authority drill with safe data, reachable backups, and evidence for each handoff.
Overview
AI Change Desk | Episode 46 | Runtime 20:51
When an AI workflow crosses a real boundary, an alert is only the beginning. This episode examines the authority needed to classify an event, interrupt work, preserve evidence, coordinate notifications, explain what is known, and authorize recovery.
The practical tool is a seven-part AI Incident Authority Card: named decision owners, reachable backups, and evidence that the handoffs work.
In this episode
- Evaluation boundaries and the difference between a model stopping itself and an independent stop control.
- Why an announced AI Force is not the same as an established operating structure.
- Why a reported privacy notification is not a final regulatory finding.
- The separate clocks for containment, notification, public disclosure, and closure.
- A 45-minute exercise for the workflow your organization cannot afford to improvise around.
Take action
Choose one consequential AI workflow. Assign the classifier, scope authority, stop owner, evidence custodian, notification reviewer, public-statement approver, and recovery/closure authority. Test the handoffs with safe data. Treat gaps as work with owners, not agenda items without deadlines.
Resource
AI Incident Authority Card worksheet
Chapters
Assembly boundaries follow the selected master. Interior body chapter times are word-weighted estimates, not forced-aligned timestamps.
- 00:00 Cold open: Who Owns the AI Incident?
- 01:02 Disclosure
- 01:46 AI Change Desk opening song
- 02:02 The incident and its different clocks
- 06:16 An incident label is not an incident process
- 09:06 Containment, obligations, and the public record
- 10:23 Privacy notification is not a final finding
- 13:21 Cross-organizational evidence handoffs
- 14:30 The seven-part AI Incident Authority Card
- 17:45 The 45-minute authority drill
- 20:41 AI Change Desk closing song
Transcript and disclosure
The transcript is derived from the approved render scripts and reusable disclosure, not an independent ASR transcription. Music positions follow the final assembly.
Quick disclosure before we start. AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are my opinions and are not representative of any organization. One additional disclosure as the Desk evolves. My current role includes privacy work, so you will hear me pay closer attention to purpose, access, retention, deletion, and accountability. I will not discuss nonpublic work here. These are my personal views, and they do not represent the State of Oregon or any other organization.
Chapters11 markers
Select a chapter to start that moment in the embedded player.
Original release timeline
Sources7 records
Disclosure and questionEditorial record
Disclosure
The transcript is derived from the approved render scripts and reusable disclosure, not an independent ASR transcription. Music positions follow the final assembly. Quick disclosure before we start. AI-assisted tools were used in parts of the research and production workflow. Final editorial judgment, risk posture, and release approval stayed human-led. This is operational guidance, not legal advice. These are my opinions and are not representative of any organization. One additional disclosure as the Desk evolves. My current role includes privacy work, so you will hear me pay closer attention to purpose, access, retention, deletion, and accountability. I will not discuss nonpublic work here. These are my personal views, and they do not represent the State of Oregon or any other organization.
Listener question
Who can classify, stop, preserve evidence, notify, and authorize recovery when your AI workflow crosses a real boundary?
Companion resources1 download
Download the episode resource.
Use the companion Word document when you want the signals, decisions, and assignments from this episode in one place before the meeting starts.
- Key signals and implications in a quick-review format.
- The actions to assign this week, with space to name owners.
- A working sheet for due dates, evidence, and follow-through.
Best Place In The Flow
Put it between listening and action: after the episode lands, before the handoff starts, or during the meeting where assignments get made.
- Use the workbook when someone wants the operational takeaway in under two minutes.
- Use the worksheet when the conversation shifts from analysis to ownership.
- Keep the transcript nearby only when you need fuller context or direct phrasing.