How it works
Don’t trust. Verify.
Prismatic treats everything an agent produces as a proposal. Only verified evidence counts as completion.
The loop
Guide → Produce → Verify → Solve.
Agents move through a ten-state flow — no state is skipped, and no claim advances itself:
guided → admitted → leased → producing → proposed → independently verified → receipt valid → merge authorized → merged → post-merge verified
The contract
The verification contract.
Results arrive as proof-carrying bundles: exact SHAs, digests, commands, exit codes, policy decisions, rollback plans, signatures. Acceptance is mechanical:
- The producer cannot self-authorize a merge.
- A revision change invalidates approval.
- Irreversible actions require human authorization.
Receipts
Two kinds of proof.
RUN RECEIPTS
What the run did.
Whether its checks passed — DONE or NOT DONE, derived from the done gate, never from the agent’s word. Ed25519-signed.
MERGE RECEIPTS
What merged.
Under which tier, with which approvals — signed on every merge. Both kinds are verifiable with a public key and readable on the dashboard.
Deep dive
The specs live in the repo.
The site never paraphrases the contract — the canonical documents are public: