Governed execution proof demo

Generate a proof receipt before action.

This page creates a deterministic receipt for a governed action. It records the proposed action, verdict, evidence references, policy reference, canonical JSON, and SHA-256 receipt hash. A refusal or human deferral is treated as a valid proof outcome, not a failure.

APPROVE
REFUSE
DEFER TO HUMAN
Canonical JSON
SHA-256 receipt hash
Downloadable proof artifact
Public demo note: this browser page creates deterministic proof receipts. It does not claim server signing, append-only settlement, external notarization, legal approval, compliance approval, or automatic execution.

Create receipt

Enter a proposed action and generate a deterministic proof receipt.

What this proves: the generated receipt material hashes to the displayed receipt hash. If the receipt content changes, the verifier should fail.

Receipt output

Copy or download the generated receipt. The verifier recomputes the hash from canonical receipt material.

No receipt generated yet.
Verifier: paste a receipt below to recompute the hash and check whether it matches.

FAQ and proof boundaries

This section is intentionally plain. It prevents overclaiming and makes the demo easier for engineers, buyers, and skeptical reviewers to understand.

Is this a real cryptographic receipt?

Yes. The page creates receipt material, canonicalizes it with sorted-key JSON, and hashes it with SHA-256 in the browser.

Is this server-signed?

No. This public demo is browser-generated. Server signing is a production upgrade.

Does this prove the action actually happened?

No. It proves the generated receipt content matches the displayed hash. Execution proof requires backend settlement or logs.

Does this prove the evidence links are true?

No. It binds evidence references into the receipt. It does not independently validate the truth of external evidence.

Why include REFUSE and DEFER TO HUMAN?

Because safe systems need proof of non-action too. A refusal or human deferral can be the correct terminal outcome.

Can a receipt be changed after download?

Someone can edit a file, but the verifier should detect that the edited receipt no longer matches the original hash.

Is this legal, financial, medical, or compliance advice?

No. It is a technical proof demo. Production use should be reviewed against the policies and laws of the actual deployment.

What comes next in production?

AEG Gate can add server signing, append-only settlement, external anchoring, policy bundles, identity, and replay verification.

Production boundary: this demo is intentionally static and safe to host as a website page. It does not store user data, does not send receipt contents to Bosley Systems, and does not execute external actions.