Agent Passport — worked example
This is what a real Agent Passport looks like once it's been through registration, risk assessment, control tracking and approval — the actual product, not a mockup of it.
ApprovedElevatedPriya Sharma, Finance Systems Lead
Finance Operations
Platform Engineering
19 Jan 2027
Matches incoming vendor invoices against purchase orders and flags discrepancies for human review before payment release.
Read invoice data from the AP inbox. Cross-reference against the PO system. Write a match/discrepancy flag. Draft (not send) a query email to the vendor contact on file.
Cannot approve or release payment. Cannot modify PO records. Cannot send vendor communications without human review.
Elevated. This agent can write to internal systems and drafts (but does not send) external communications — meaningful capability, with no path to irreversible financial action.
Score 14 / 42 · assessed under model version 2026.1
7 of 7 mandatory controls closed — 6 implemented, 1 under a current, complete exception. This is what actually gates approval now, not just informational text.
New agent, first recertification cycle not due until the standard 90-day mark. Tracked via the finance-systems team's existing quarterly access review instead of a separate campaign for now.
Expires 18 Oct 2026 · Approved by raj.kumar@example.com (CISO)
Approved 19 Jul 2026 by Raj Kumar (CISO).
Approval here required a named principal, a scheduled review date, and every mandatory control closed — implemented, or under a complete, current exception. That's not informational text; it's an actual gate. LFC-01's exception above (reason, expiry, named approver) is what closed that control, not a status dropdown flipped without a record behind it — an incomplete or expired exception would have kept this Passport blocked at Pending approval.
This is one agent, fully governed. A real pilot builds this for up to ten of yours in thirty days.
See the pilot →© 2026 Aseem Mohan · Assessment · Sample Estate · Methodology · Control library