Agent-era builds · Stamp tooling

The stamp tool

Describe the agent action here, in your browser. The tool binds it to the draft you read, the exact machine parameters, and an expiry, then seals all three with SHA-256. Everything computes on your machine. Nothing is sent anywhere, nothing is stored.

What it does

The tool walks the seven blocks of the v0.1 stamp: what the action is, which law governed the draft, the exact machine parameters, the draft you read, and your sign-off. It pulls the CA-01 to CA-12 rows live from the versioned index, so the citations never go stale, and it shows you the canonical parameter text before anything is sealed. When the stamp is computed you get the JSON download and a clean one-page record for the file.

Read the full spec v0.1 before you sign anything: it defines the seven blocks, the verification procedure, and the one rule with no exceptions, that a stamp never carries raw personal information.

The honesty caveat

A stamp is only as honest as the code that computes it. Never trust digests computed by the agent that benefits from the approval. This tool runs in your browser, not the agent's.

No names, no email addresses, no ID numbers anywhere in this form. A stamp carries categories, never values.

1. The envelope

Permission expires (required)

An approval without an expiry is a permission that never dies. Ninety days is the default.

2. What the action is

Loading the live consequential-action index…

One-sentence summary

Smallest permission the task needs

Target system (a stable id, never a credential or endpoint secret)

Data categories touched (comma-separated: types, never values)

3. Which law governed it

Corpus version

Statute citations (one per line)

Enforcement case ids (one per line)

4. The machine's exact arguments

Execution parameters (JSON)

Parsed as JSON, canonicalized per RFC 8785, then hashed. The canonical text is shown below before anything is sealed, so you can check exactly what gets hashed.

5. Proof you saw what runs

The draft the approver read (exact text)

Hashed byte-for-byte as UTF-8. Paste the exact draft: what you paste is what gets hashed, and the character count is shown so you can confirm nothing was added or trimmed.

0 characters

6. Your word

Approver role (a role, never a name)

Decision

Signed at

Attestation (in your own words)

7. The fixed disclaimer

This stamp is an open evidence format for recording human approvals of agent actions. It is not legal advice, and it is not a movahedi.ca compliance certification.

Fixed by the spec. It appears in every stamp byte-identical; nothing may be added, nothing removed.

Local only

All digests compute in this tab with WebCrypto. The only network call this page makes is loading the public consequential-action index. Your inputs never leave this machine.

The honesty caveat

A stamp is only as honest as the code that computes it. Never trust digests computed by the agent that benefits from the approval. This tool runs in your browser, not the agent's, and it shows you the exact bytes it hashes before you sign.

What this is not

Not legal advice, not a compliance certification. The stamp is an evidence format: it records what was approved so a third party can re-verify it months later. It confers no status, and no stamp is ever described as certified or endorsed by movahedi.ca.

Questions

Where do my inputs go?

Nowhere. The stamp is built entirely in your browser with WebCrypto. The page makes one network call: loading the public consequential-action index. No account, no storage, no telemetry.

How do I turn the stamp into a PDF?

After computing, choose Print / save PDF. The tool opens a clean one-page record and your browser's print dialog; save as PDF from there.

Can I verify a stamp someone else made?

Yes. Open the Verify tab, paste the stamp JSON and the exact draft text the approver read. The tool re-runs the spec's four-step verification locally: any mismatch, any missing block, any expired stamp is rejected.

What if the index changes after I stamp?

The stamp pins the corpus version in its cited-authority block. Verification recomputes the digests from the stamp itself; it does not consult the live index. A newer index never rewrites an old stamp.