A one-page excerpt of the kind of audit-grade evidence trail a governed write-path engagement produces — one row per proposed action, every policy check timestamped and mapped to a control.
| Action | PO / Amount | Decision | Actor |
|---|---|---|---|
| po_adjustment | PO-4488 · $1,200 | Executed | agent |
| po_adjustment | PO-4471 · $8,000 | Escalated → approved | agent + Compliance Reviewer |
| po_adjustment | PO-4502 · $40,000 | Blocked | agent |
| vendor_hold_release | PO-4471 · $2,000 | Blocked | agent |
| Check | Result | Detail | Control mapped |
|---|---|---|---|
| scope | pass | 'po_adjustment' is an authorized action type | NIST AI RMF GOVERN-1.5 |
| spend_cap | fail | $40,000 exceeds the $25,000 single-approver ceiling — no execution path exists | NIST AI RMF MANAGE-1.3 |
Note what this row shows: the action never reached the ERP validation layer at all, because policy blocked it first. That's the point — evidence is logged for what didn't execute, with the same fidelity as what did.