Agent Certificate and Evidence

Configuration you can't see becomes a record you can hand over.

The incident review starts months after the agent moved on. The record is already there, and the agent can't rewrite it.

SIGNED RECORDS · KEPT OFF THE AGENT'S MACHINEillustrative
AGENT'S MACHINE
analytics-svc-09
×rewrite history — refused
signed
ACC-…-4416ALLOWprev 0x51c2…hash 0x8e07…
ACC-…-4417HOLDprev 0x8e07…hash 0x9c41…
ACC-…-4418BLOCKprev 0x9c41…hash 0x3fa0… ✓
Each record points to the one before it. Change one, and every record after it stops matching.
Agent Certificate

What an agent is for, and who answers for it

ISSUEDATBASH AGENT CERTIFICATEFinance Operations
MANDATE
Keep the books reconciled and suppliers paid within approved limits and rails.
OWNER
finance-lead
APPROVED BY
CFO
RED LINES
5 active
REVIEW BY
Jan 2027
atb-cert:0x7f3a…c91e · policy-hash 0x2b9d…

What a certificate holds

Mandate
Owner and chain of command
Tools, skills and memory
Red lines and approval boundaries
Identifiers and key metadata
Policy hash and certificate ID
Responsibility map
Review date

Key metadata only. A certificate never contains your secrets.

Verdict Record

Every decision, reconstructible on demand

01

Action and target

What it tried, on what.

02

Agent identity

Who asked, and whether it matched its registry record.

03

Policy version

Which rules applied, down to the clause.

04

Red lines evaluated

Each one passed or triggered.

05

Reasoning

Why, in plain words.

06

Decision time

How long the verdict took.

07

Escalation and approver

The name on every HOLD.

08

Audit reference

One ID to pull the whole story.

Give your auditors one ID, not a forensics project.