verified context layer
Contracts that verify themselves.
Requirement and implementation are bound by a pair of hashes. Any harness, any model. We never generate code — that's why our verdict is worth something.
The primitive: LogicBlock
contract_hash
An executable specification confirmed by a human. The reference. One contract — many implementations: different models, different languages.
impl_hash
An implementation automatically checked against the contract. The defendant. Cosmetics (formatting, comments) never change the hash.
Verdict
Cached by the pair. Re-checking a known pair costs zero. Content-addressed: reproducible by any third party.
How it works
1 · scan
Paste your code — scan proposes contract drafts from existing functions. We propose, a human confirms.
2 · confirm
Confirm a contract — its canonical form gets a contract_hash and becomes the reference.
3 · verify
Paste an implementation (from any agent, from any harness) — get a verdict for the pair (contract_hash, impl_hash).
Why we're neutral
A tool that writes code cannot be the one that rules on its correctness. That's a structural conflict of interest, not a question of model quality. We support every harness because we're not allowed to have one.