Agent Seal Case Study

Annex III-style high-risk pattern

Benefits triage agent

A sample record for an intake agent used around access to essential public or private services.

Sample pilot record · Not legal advice · Not official registration

What the agent does

The agent receives an intake request, checks whether required documents are present, summarizes the case for a human reviewer, and recommends a routing queue. It does not issue a final approval, rejection, sanction, or benefit amount.

Why the record matters

In an essential-services workflow, the first audit question is not whether a model sounded helpful. The questions are concrete: which agent touched the file, who controlled it, what was it allowed to do, whether a human could intervene, where the logs are, and how an incident or complaint can be followed up.

Control area What the sample record shows What remains outside Agent Seal
Identity Signed covenant, public key, signed Agent Card, keeper, status. Internal access review and staff authorization.
Scope Allowed: intake review and queue recommendation. Denied: final decision and benefit calculation. Operational policy proving humans enforce that boundary.
Oversight Human oversight URL and keeper link are present in the evidence bundle. Actual staffing, training, escalation drills, and stop authority.
Record keeping Trace count, DAG root, timestamp receipt summaries, and court export pointer. Retention schedule and private case-file controls.
Incidents Procedure URL and public references can be indexed without private report bodies. Full incident reports, authority notifications, remediation, and complaint files.

How to read this sample

Treat the evidence JSON as an index. It tells a reviewer where to verify identity, status, keys, logs, timestamp receipts, incident procedure, and missing controls. It does not contain private applicant data, complaint bodies, raw proof arrays, or the provider's complete legal file.

Evidence links

Open evidence JSON Compare low-risk pattern