Context Hash Grants

Approval leases bound to grant context — content hash + context hash, sealed.

1 · The action

What is being approved

Action type

Content pointer (optional)

Content hash (sha256 of the exact bytes being approved)

Compute from text

Compute from file

2 · The context

Model / agent identity

Venue (where the action executes)

Tools available at decision time (one per line)

Conversation reference (optional)

Approval lease expires

Approver (identity + authority basis) Notes for the approver (optional)

3 · The approval card — exactly what gets bound

Fill in the action and context — the card renders live here.

Signing happens with the CWI offline key — never in the browser. Take the package to sign-grants.js, or request a signature via hp@cumulativeweb.com.

Verify a grant

Paste a grant record above, or open a ?grant=<id> link.

Honest limits. A grant binds the recorded context, not the universe — it is only as complete as what was put in. Hash verification proves the package is intact and unexpired; Ed25519 signature verification (verify-grant.js, Node) proves CWI sealed it. A VERIFIED grant does not prove the action was wise — only that this exact content, in this exact recorded context, was approved before expiry.

Try Context Hash Grants live

Approval leases bound to grant context — every approval seals content hash + context hash, Ed25519-signed and hash-chained.

Try it: verify a real signed grant Read the trust-log companion

Verify it yourself

Don't take our word for it — re-run the check from your own machine or your own agent runtime.

In your browser: verify-grant.js — the zero-trust Node checker (schema + hash + Ed25519 signature + expiry + crosscheck); paste any grant record into the page's own Verify tab for the same check in your browser.
From your agent runtime: cwi-mcp-server — CWI's read-only MCP server. Call ledger_state_get: read CWI's live approval records yourself: ledger_state_get with fields=["approvals"] — read-only, no auth. Zero-trust guide: VERIFY.md.