Receiptverification.Verifier-boundcheck.
Inspect receipt identity, governance binding, causal proof, and the supporting artifact surface without browser-local proof claims.
Two denial scenarios are available as walkable Evidence Pack Tours — OpenClaw and Behavior Governance. Inspect the receipt envelope, evidence pack, and supporting artifacts.
Identity, governance binding, and receipt refs are inspectable on the public surface.
Artifacts behind the evidence pack are visible instead of implied.
The verifier-bound policy check stops short of cryptographic success and reports unavailable when verifier response is missing.
OpenClaw-style agents operate over live systems through internet-exposed command interfaces. Without a governed execution boundary, an unauthorized command reaches its target. Here, the boundary held: the request arrived, the policy denied it, execution was not attempted, and the outcome is failed_closed. Inspect the decision, the null execution receipt, and the linked Evidence Pack to see what that boundary looks like as evidence.
actor_not_authorized_for_protected_mailbox. The unauthenticated external principal had no authority over mailbox.read.protected.
Execution was not attempted. The execution receipt is null. No capability was exercised against the protected resource.
Terminal. Governance held. A Denial Receipt is evidence that the boundary worked — not a system error. Evidence Pack available.
Receipt identity is inspectable — type, version, tenant, actor, and correlation are exposed on the public surface.
Governance binding is inspectable — policy hash, actor, and correlation anchor the decision to its context.
Evidence-pack and artifact references are visible — not implied.
Verification posture is explicit — algorithm, canonicalization, and offline-verifiable flag are in the envelope.
Cryptographic validation remains verifier-bound — no browser-local verification success is claimed.
What an Evidence Pack is.
Evidence Packs are portable inspection artifacts governed by CAES v0.2.0 — the standard for how consequential AI actions are authorized before effect. The receipt envelope supports verifier review, the evidence pack groups the support, and artifacts identify the supporting material behind the pack.
Receipt reference that groups the support surface for verifier review and offline-verifiable export.
Documents, recordings, URLs, attestations, or system records inside or behind the evidence pack.
Verification material expected by the runtime verifier for full receipt validation.
Signature algorithm, canonicalization, hash algorithm, and offline-verifiable posture for recomputation.
artifacts[] references the documents, recordings, external records, screenshots, attestations, or transcripts that sit inside or behind the evidence pack.
Proof has to survive review.
Two Evidence Pack Tours are publicly available: OpenClaw unauthorized command denial and Behavior Governance helpdesk unauthorized action denial. Each shows a governed boundary stopping an unauthorized action before execution.
OpenClaw / Unauthorized Command Denied
Internet-exposed autonomous command fails closed before execution
Behavior Governance / Unauthorized Help Desk Action Denied
Password reset and account disclosure request fails closed before execution
Saved evidence. Receipt envelopes and linked artifacts are inspectable. Live gateway checks run separately when configured.
This execution record documents a sample AI decision governed by Keon. The public envelope shows receipt identity, governance binding, decision state, execution state, evidence-pack linkage, and verification metadata.
The receipt envelope supports verifier review, the evidence pack groups the support, and artifacts identify the supporting material. Verification remains verifier-bound until a Keon Systems verifier returns status for the envelope and its artifacts.
Browser-local cryptographic validation is not claimed here. Verification requires a verifier response; unavailable remains unavailable, never verified.
Embedded inspection surface. Use the proof actions below for full tour access.
What each surface contains.
Select an artifact component to inspect what it contains, what it proves, and what remains verifier-bound.
The EvidencePack receipt is the envelope that ties together the decision, outcome, PolicyHash, artifact references, and verifier posture. It is the artifact a verifier inspects to confirm that a governed action was evaluated under a specific policy before effect.
This is not a feature comparison. It is a question of what is provable.
Can it establish the action was authorized?
No. A log records what happened. It does not establish that it was permitted.
A receipt can support authorization review only when validated by the verifier that issued or recognizes the proof chain.
Can it be independently verified?
No. Verification requires access to the original system to confirm the log is authentic.
Yes, when a valid evidence pack, artifact set, and recognized verifier are available. The configured decide_only policy check surface shown here is not full receipt verification.
Is it tamper-evident?
No. Logs are mutable. A modified log is indistinguishable from an original without external controls.
Tamper evidence depends on backend signature and anchor validation, not browser-local comparison.
Does it bind to a specific policy version?
No. A log entry cannot establish which policy version was active at execution time.
The PolicyHash, evidence-pack reference, and artifact bindings are present in the sample envelope and must be checked by the verifier before verification can be claimed.
PolicyHash binds a decision to canonical policy state at evaluation time — a concept defined by CPP v1.0 — the protocol for deterministic, verifiable, independently reproducible policy decisions. The Governed Spine is the append-only, tenant-scoped causal evidence chain that records all governed events.
Receipt identity is inspectable — type, version, tenant, actor, and correlation are exposed on the public surface.
Governance binding is inspectable — PolicyHash, actor, and correlation anchor the decision to its policy context.
Evidence-pack and artifact references are visible, not implied.
Verification posture is explicit — algorithm, canonicalization, and offline-verifiable flag are in the envelope.
Cryptographic validation remains verifier-bound — no browser-local verification success is claimed here.
The public sample now shows the receipt envelope, the evidence-pack reference, and the supporting artifacts. Full signature and artifact verification still depends on verifier runtime and trust material.