- CONTRACT
- compute-travel-expense-pre-approval
- VERSION
- v3
- ISSUED
- 2026-05-12 14:32:07 UTC
- SEALED BY
- ⌃ Sarah Chen · Finance
- RECEIPT
- rcpt_3f7a92b8e4c1
- ROOT
- 0x4e2a...b71c
An LLM guesses.
RAG paraphrases.
Ctrl AI signs every action.
The Contract is signed. The Receipt is the proof. Every AI action in your company — Cursor, ChatGPT, Slack AI, your own apps — runs through a signed Contract and leaves a cryptographic Receipt of Record.
Verify offline → curl ctrlai.com/api/receipts/rcpt_3f7a92b8e4c1
Three primitives. One signed unit.
Most "AI governance" is logging on top of an LLM. Ctrl AI flips it: the LLM picks from typed contracts your humans signed. Hallucination is not mitigated — it is structurally impossible.
Contracts
Typed callable functions signed by humans. Input schema. Output schema. Post-conditions. The LLM picks a Contract and calls it — it does not invent behaviour from prose.
Missions
Standing directives with success criteria. Auto-evaluated as Contracts run. The agent has commitments, not just answers.
Cases
Durable working memory with an append-only event log. A multi-week decision is a single Case with every signed action attached.
Every action leaves a Receipt of Record.
On every invocation we sign the inputs, outputs, signers, and trust level with an Ed25519 key, then append the digest to a chained-hash transparency log. Any counterparty — your auditor, your customer, your regulator — can verify the receipt offline with one curl and one signature check.
# Verify any Ctrl AI receipt offline curl -s https://ctrlai.com/api/receipts/rcpt_3f7a92b8e4c1 \ | jq '.receipt' > receipt.json # Fetch the public signing key curl -s https://ctrlai.com/.well-known/ctrlai/receipt-keys \ > keys.json # Verify the Ed25519 signature node verify.js receipt.json keys.json # → SEALED · entry #1,847 · root 0x4e2a...b71c ✓
No SDK required · No vendor lock · Cryptographic, not theatrical
Five surfaces. One frame.
- §4·1
Compliance Packs
Install expert-co-signed bundles of typed Contracts. EU AI Act Starter, DORA AI Risk, B2B SaaS Rev-Ops.
- §4·2
Approval Inbox
Daily triage of gates pending sign-off, Contracts past review, expired Contracts, stale Mission criteria, proposals from Coverage.
- §4·3
Mission Control Room
Visualize a Mission's typed executor plan walking step by step. Auto-advance, gates surface inline, every step receipt-anchored.
- §4·4
Trust Portal
Public, cryptographically verifiable record of every signed Contract invocation. Pin the root hash; verify offline.
- §4·5
Authority Layer
Explicit delegation grants from humans to agents or API keys. Scoped, conditioned, expiring. MCP callers blocked without a matching delegation.
You don’t author governance. You install it.
Expert-co-signed bundles of typed Contracts targeted at a regulation and a vertical. Install in five minutes. Inherit the jurisdiction tags, the clause mappings, the expert signatures.
Three tiers. Plain numbers.
Free
Two users. One workspace. The full primitive set, no caps.
- —Up to 2 seats
- —Unlimited Contracts
- —Receipts of Record
- —Public Trust Portal
Team
One installed Pack. Up to 25 seats. SSO and audit export.
- —1 Compliance Pack
- —Up to 25 seats
- —SSO + SAML
- —Quarterly audit binder
Enterprise
Multi-Pack. Unlimited seats. Custom signers. Dedicated transparency log retention.
- —Unlimited Packs
- —Unlimited seats
- —Custom Pack co-signing
- —Air-gapped or self-hosted option
The Contract is signed.
The Receipt is the proof.
Deploy AI on work that actually matters. Receipts your auditor can verify. Authority your delegations enforce. Missions your agents honour without being asked.