
Watch a real AI agent check a stamp before taking a high-impact action. Try a prompt injection attack. See why it fails.
An AI agent is about to take a high-impact action. Before it executes, it queries Good Proof.
Action proceeds within verified scope
When no stamp is found, the gate returns NOT_VERIFIED and the action is blocked. This is fail-closed by default — no stamp means no ship.
Try a prompt injection attack. See why prompt tricks cannot bypass an external reliance gate.
Send an instruction to see how the agent reasons.
Idle. Awaiting a reliance request from the agent.
The 13 binding fields
Every Good Proof Stamp cryptographically binds these 13 fields. Change any one of them and the Stamp must be re-verified or withdrawn.
action classThe category of high-impact action this Stamp authorises (e.g. tool execution, irreversible transfer, eligibility decision).
scope summaryThe boundaries of the action — what is in scope and what is not. Acceptance is limited to this scope.
policy versionThe exact policy version under which the Stamp was issued. Policy changes trigger NEEDS_REFRESH.
verification modeAuto-stamp, Guardian-sealed, or hybrid — how the verification was carried out.
workflow / prompt hashHash of the workflow definition (or prompt template, for AI lanes) bound at issuance.
model versionFor AI-assisted lanes, the exact model snapshot bound at issuance. Model change triggers NEEDS_REFRESH.
tool permission manifestThe full set of tools and permissions the bound action class is authorised to use.
evidence pack hashHash of the IDA Evidence Pack snapshot — the dispute-ready, time-stamped artefact that travels with the Stamp.
signer referenceThe signing authority that issued the Stamp (programme-scoped HSM key or Guardian panel reference).
expiryISO 8601 timestamp at which validity ends. After expiry, status transitions to NEEDS_REFRESH automatically.
revocation statusWhether the Stamp is live, revoked, or pending withdrawal. Revocation is append-only — older signatures remain verifiable.
escalation ruleWhat happens when status is not VALID — block, escalate to Guardian, route to a human, or fail closed.
jurisdiction / programme scopeThe programme, contract, or regulatory regime that defines acceptance criteria. Acceptance depends on counterparty and programme.
This is what makes a Stamp portable, machine-checkable, and dispute-ready — and what makes it impossible for the agent to forge.
Export this list as a PDF for procurementFrom first conversation to live verification in production. Here's the journey.

You just tested the gate for insurance actions. Explore real-world use cases, stamped specimens, and sector-specific verification lanes.

Insurance
Real-world use cases, stamped specimens, and pre-filled Sprint form
Every Good Proof Stamp ships two artifacts: a live Status Link and a time-stamped IDA Evidence Pack.
Live Status Link
Real-time verification endpoint
token: h4qd9wb9spyw
status: VALID
scope: hardship_determination
expires: 2026-08-15
Try the verifier
IDA Evidence Pack
Time-stamped dispute-ready snapshot
signer: guardian_panel_uk_01
version: 2026.01.21.1
hash: sha256:7f3a...
window: 90 days
Browse stamped specimens
Book a 25-minute Sprint call. Identify your first verification lane. Ship in 30 days.
Or explore Insurance examples