The papers first.
Three papers, in the order they depend on each other. The abstract and the PDF are on each paper’s page.
Trust and Proof
The question is not whether a system is trustless. It is where the trust has gone: what was proved, relative to which assumptions, and what residue remains.
Read the paper →Goal-Relative Assurance of Dynamically Generated Execution Traces
When an agent builds the path, assurance cannot mean “the approved process was followed.” The claim is that this trace meets this goal relative to this boundary, and that the boundary covers the floor the institution required.
Read the paper →Agentic Process Governance
An allow is not discharge. The institution, not the agent, pins the goal and the floor. Governance is the relation among the goal, the trace, the proof boundary, and the trust that remains.
Read the paper →The terms the papers fix.
The glossary records the sense each paper gives a term. It does not add a claim.
Stacks and Anchor, with the code in the open.
The Lean protocol stacks and Anchor are patterns we have researched and prototyped. Open source is the evidence. You reach them inside a software project, through the Lean-proved software offer. Proof Fabric is the name for the gate and Anchor used together.
The Compliance Operator Framework project.
COF is the SMART: SCOTLAND project, from 18 June 2026 to 30 June 2027. It is not another name for the Compliance Operator. Read the announcement.
Spec++ is how a policy is written.
Spec++ is the method for writing a policy so the gate can be proved. It is not a product.
Proof-Gated Architecture Overview
An overview of the gate for a reader who wants the architecture in one document.
Available on request to targeted customers and interested parties.
Request the document →