Anchor Proof Framework
Anchor uses the same formal-methods pattern as the Compliance Operator. Riley Betts has researched it. It is on the roadmap. It is not a second product you can adopt today.
The same pattern as the gate
The Compliance Operator checks a proposed action against a versioned policy. It emits a decision and a certificate. Riley Betts did that work in the lean-compliance research. Anchor starts from that certificate. It does not replace the gate.
Anchor adds a proved policy for how agents negotiate and interact. That policy sits above the agent protocols already in use. It does not replace those protocols. The proof includes its limit: what was shown, given which assumptions, and what is still trusted.
What is committed, and what stays off the record
A third party can see a hash of the certificate and the policy version. The certificate, the inputs, and the policy text stay off that record. The chain attests that the decision existed at a time. It does not re-check the mathematics. Riley Betts found that split in an Ethereum feasibility study.
A public or private chain as an audit channel
The receipt can sit on a public chain or on a private one. The Ethereum study is the public example. It anchors a Compliance Operator decision. Two agents co-sign a confirmation off the hot path. The chain write comes after the decision. Riley Betts measured that study on a local chain.
A public or private chain can carry the receipt of a compliance decision. That receipt can include a bilateral trade confirmation. The book stays off the chain. The consortium ledger below is the private example.
A receipt another party can check
lean-tee is a trusted execution environment. Its implementation is a zkVM (zero knowledge virtual machine). That machine binds which program ran, which inputs it saw, and which output it produced. Another party can accept an honest result or reject a forged one. It is not a confidentiality enclave. The measured programs are examples of the same gate shape: compliance, trade, onboarding, and voting.
A consortium ledger, specified in Lean
anchor-chain is a separate researched ledger. Nodes agree a receipt of a transition that happened off the ledger. Safety properties are proved in Lean. The cryptographic checks sit beside that proof. Not every cryptographic step is proved. Full in-circuit recursion is not done. A complete compiler from operations to constraints is not done.
Status
Anchor stays on the roadmap. When it is built for a customer, you reach it through the Lean-proved software engagement. Proof Fabric is the name for the gate and Anchor used together.