Agent governance Action-level audit
Agent Privileging · Component 3

Action-level audit

Model governance audits outcomes on a cadence — quarterly checks against a baseline. Agent governance cannot wait for a quarter: the unit of risk is the individual action, so the unit of audit must be too.

Log against scope, at write time

Each action record carries the action type, timestamp, and — computed when the record is written, not during a later review — whether the action fell within the agent's scope. Computing compliance at write time is what makes the next component possible: automatic suspension the moment an out-of-scope action occurs, rather than at the next committee meeting.

The organization holds the log

A vendor dashboard is the vendor's record, shaped by the vendor's interests, retained on the vendor's schedule. The defensible position is an organization-held log — fed by the vendor's events if need be, but owned, retained and tamper-evident on your side. When something goes wrong, "our log shows" and "the vendor's dashboard showed" are different sentences in every forum that matters.

Tamper-evidence is not paranoia

An audit log that can be silently edited protects no one — including the people who never edited it, who now cannot prove they didn't. Hash-chaining entries (each record carrying a digest of the previous) is cheap and turns the log into evidence: any alteration breaks the chain visibly. The same property that protects patients protects the accountable humans.

Part of the complete healthcare AI governance guide.