Who's Accountable When the Agent Acts? | Governed by Design #4

An agent does something unexpected. You know what happened. You don't know who's responsible.

In multi-agent systems, accountability doesn't just get complicated, it disappears into the handoff. In this episode, hosts Alex and Jaime introduce the Accountability Canvas: a pre-deployment tool for assigning four named owners before any agent goes live.

You'll learn:

Why accountability diffuses in agentic systems, assumed by all, held by none
What Accenture and Wharton mean by "intelligence may be scalable, but accountability is not"
How OWASP ASI08 (Cascading Failures) makes attribution in multi-agent systems structurally difficult
The four roles on the Accountability Canvas: Boundary Owner, Oversight Owner, Error Response Owner, Boundary Update Owner
Why EU AI Act Article 26 requires a named natural person, not a team or committee
How to implement canvas-before-deployment as a forcing function
How the canvas connects directly to Decision Boundary Contracts (Edition 2) and the Oversight Spectrum (Edition 3)

Key Insight: Delegation doesn't transfer ownership. The team that deploys Agent A still owns what Agent C does, because they started the chain. The Accountability Canvas makes that explicit before the agent acts.

Resources mentioned in this episode:📄 Full edition with research + downloadable Accountability Mapping Canvas: themohamedadam.substack.com📰 LinkedIn newsletter version: Search "Automate & Elevate" on LinkedIn

Coming next week: Edition 5 "Audit Trails That Survive Scrutiny". What to log, how to structure it, and what regulators will actually ask for.

Det här avsnittet är hämtat från ett öppet RSS-flöde och publiceras inte av Podme. Det kan innehålla reklam.

Avsnitt(39)

The Invisible Gap: What Article 26(5) Actually Deems Fulfilled | Governed by Design #9

There's a sentence in Article 26(5) of the EU AI Act that reads like a gift to financial institutions: the monitoring obligation "shall be deemed to be fulfilled" by complying with the internal govern...

13 Juli 20min

The Rehearsal: Proving You Can Stop the Agent Before You Have To | Governed by Design #8

You filled in the Suspension Authority Ledger. A name, measurable triggers, an ordered notification chain. One question remains: is any of it true?In this episode, Alex and Jaime take Edition 7's sixt...

10 Juli 19min

The Authority to Stop: Who Can Halt the Agent When It Goes Wrong | Governed by Design #7

An AI agent is in production and starts doing the one thing it was built never to do. Who has the authority to stop it, right now, this afternoon?We closed this series at five primitives. This episode...

1 Juli 20min

The Implementation Path: From Framework to Reality | Governed by Design #6 (Series Finale)

After five editions building a vocabulary for AI agent governance, the question that kept coming back was the same one. Where do we actually start?In this final edition of Governed by Design, hosts Al...

20 Maj 24min

Audit Trails That Survive Scrutiny | Governed by Design #5

Most agent systems have logs. Few have audit trails. Almost none have evidence architecture, the version that holds up under regulators. This episode introduces the Handoff Receipt: the unit of eviden...

12 Maj 24min

Human Oversight That Doesn't Become a Bottleneck | Governed by Design #3

Most teams say they have human oversight. What they often have is a human approval queue.In this episode, hosts Alex and Jaime break down the Oversight Spectrum, a framework for designing human oversi...

28 Apr 25min

Governing AI Agents: The Decision Boundary Contract

"The agent can process refunds."That's not a boundary. That's a capability statement.A boundary tells the agent what it's allowed to do, and what to do when it's not sure.In this episode of Governed b...

14 Apr 20min