No agent acts on one key.
An AI from a different company checks every action. Your people countersign. Then it runs.
Two keys. Two makers. Always.
An AI checking work from its own company can share the same blind spots. So Biclave always asks a different company's AI to check.
- Key one is the AI that does the work. Key two is an AI from a different company that checks it.
- Biclave never lets a company check its own AI's work. It is a rule in your charter, not a setting.
- Every pairing is recorded, so an auditor can see which AI built a change and which one checked it.
illustration
Two independent keys. Then yours.
The agent that builds is never the one that checks. Follow one change through Biclave.
The builder
An AI coding agent plans and builds inside a sandbox. Your checks run against exactly what will be committed.
The independent verifier
A model from another vendor reviews the exact commit. Its verdict is bound to the bytes it read.
Your countersign
Nothing is accepted on one key. You approve the exact change, and a veto window stays open.
Your agents work all night. Nothing consequential should happen on one key.
AI agents are starting to pay suppliers, email customers, share files and change production. The same rule applies to every one of those actions: an AI from a different company checks it, and the right person approves it.
Agents ask before they act
A consequential action waits for the two keys before it happens, not a review after the fact.
One approval, one action
An approval covers one exact action. It cannot be stretched to cover anything else.
Never the same company
The AI that checks an action never comes from the company whose agent wants to take it.
illustration
Every step leaves evidence you can check.
Show an auditor who built a change, who checked it, who approved it, and the exact bytes each one saw.
Codex returned PASS FOR THIS GATE and the acceptance rule holds. Accept the package?
A charter approved by hash
Change a rule, a template or a line of code, and Biclave stops acting alone until you approve again.
Builder and checker kept apart
Key one and key two always come from different companies, and the pairing is recorded.
Approvals bound to the change
An answer applies only to the exact decision it answered. Change the question and the approval lapses.
A sealed audit trail
Every decision, verdict and transition is recorded and chained before anything acts on it.
Sandboxed agents
Agent steps run in the operating system's sandbox behind a command guard. Secrets never reach the logs.
It stops itself
Stop rules, daily budgets and a bounded shutdown. When something is off, it asks instead of guessing.
Governance built into one vendor's agent checks that vendor's work, by that vendor's rules. Biclave keeps the keys apart.
Put a second key on your agents.
Biclave is in early access with a small number of teams. Tell us which agents you run and the controls you need, and we will show you Biclave on your own work.
Request early access