Riley Betts Proof Fabric
An ensemble of CECO and Anchor that produces portable trust: proved policy, a deterministic gate, and a compact public receipt that neither party owns.
The Riley Betts Proof Fabric is an ensemble of CECO and Anchor. It produces portable trust: independently verifiable proof that a rule held, that can sit above whatever system is acting. CECO is the local gate — the agent proposes; a formally specified validator decides, the same way every time, before anything runs. Anchor is the chain layer — a proof-anchored ledger where data stays off-chain and the chain only orders, timestamps, and verifies a compact proof that a state transition happened. When two parties must bind one object, they co-sign once. The artefact is a trust passport, not a new venue and not the book.
When two internal logs disagree, there is still no artefact that neither firm owns. Copilots, messages, human-in-the-loop, monitoring, and public ledgers each miss a different part of that gap. The Proof Fabric sits in it. It does not replace existing rails. It sits beside them: CECO proves locally; Anchor anchors publicly; validity stays in the off-chain certificate. The pattern is domain-general. OTC confirmation is one feasibility application, not the definition of the fabric.
When two logs disagree, what artefact neither firm owns?
That is the question. A reconstructed audit trail is not it. A dashboard is not it. A public book of the underlying data is not it.
Portable trust is a compact, independently verifiable receipt: which rule applied, whether it held, at a stated time — including when the answer is no. It can travel between counterparties, examiners, and systems that do not trust each other’s IT. We call that artefact a trust passport.
02 — The ensembleCECO proves locally. Anchor holds the receipt.
CECO, the Cryptographically Enforced Compliance Operator, is the local gate. It treats the agent as untrusted. Prompt injection cannot talk it into a non-compliant transition: the gate is not a prompt. Same state, same action, same allow or deny. That is deterministic governance applied to a consequential action, and a use of proof-gated architecture.
Anchor is the chain layer of the fabric. Data and application logic stay off-chain, in each owner’s own store. The chain only orders, timestamps, and verifies a compact proof that a state transition happened. Additive under CECO, not a replacement — the receipt log for “anchor publicly,” without replicating the book.
When two parties must agree the same terms and the same compliance hashes, they co-sign once. There is no “my version vs yours.”
Prove locally. Co-sign when the relationship requires it. Anchor publicly.
03 — What travelsHashes, outcomes, and time. Not the book.
Validity stays in the off-chain certificate. Books, terms, rulesets, and sensitive data stay off-chain. The chain attests existence and time. It does not become the venue, the register, or the matching engine.
Beside the rails, not instead of them.
- ≠A matching engine or a new legal finality story. The fabric does not become the venue.
- ≠A public book of the underlying data. Confidentiality stays with the owner. The chain carries proofs, not the ledger of the business.
- ≠A replacement for existing rails. Messages, clearing, settlement, and custody endure. The fabric sits beside them.
- ≠“Put it all on chain.” That is the wrong disclosure. Hashes, outcomes, and time travel. The book does not.
The pattern is domain-general.
Wherever a consequential action must be proved locally and a receipt must be portable, the same ensemble applies. OTC confirmation is one feasibility PoC — see the look-alike case study and what the fabric does in capital markets. That PoC used Ethereum as a stand-in for Anchor. It does not define the fabric.
06 — FAQCommon questions.
What is the Riley Betts Proof Fabric?
An ensemble of CECO and Anchor that produces portable trust: proved policy, a deterministic gate, and a compact public receipt that neither party owns.
How do CECO and Anchor differ?
CECO is the local gate — the validator that decides before execution. Anchor is the chain layer — a proof-anchored ledger that orders, timestamps, and verifies a compact proof of a state transition. Together they are the fabric.
Is Anchor generally available?
No. Anchor is in active R&D. CECO is pilot / PoC on domain workflows.
Does OTC define the fabric?
No. OTC confirmation is one application of the fabric. The fabric is portable trust, not a trading venue.
Does this replace existing rails?
No. It sits beside them. Messages, clearing, settlement, and custody endure. The fabric carries a portable answer to whether a rule held.
What travels on the chain?
Hashes, outcomes, and time. Validity stays in the off-chain certificate. The book never goes on-chain.
Portable trust. Proof, not promises.
Start with a fixed-scope pilot on the workflow where “my version vs yours” still costs you: CECO decides locally; Anchor holds the portable receipt.