Open Integration Standard · Protocol 144
This is the open specification under which physical trust telemetry — a signed receipt of whether an AI agent stayed in the lane it was given, that anyone can recompute — integrates with a commercial underwriting facility. It is published, not negotiated in the dark — the exact mathematical and operational terms, open to any facility that meets the technical threshold.
Notice
This document is an open, non-binding integration standard and letter of intent. It is not a binding offer, not a solicitation of securities, and not a custody or market-making service. Nothing here creates an obligation on any party until a bilateral agreement is executed. ThetaDriven Inc. remains an attestation oracle — it never custodies a work-product byte.
Run it before you read the terms
Every claim in this standard traces to something you can execute right now. The gate is free to install; the receipt it mints recomputes on your own machine. You are not asked to take the signal on faith — you are asked to reproduce it.
The install and the measurement are free and open-source (MIT); only the financialization/attestation layer is licensed. To recompute a receipt yourself, clone the public repository at the commit the receipt names and run:
2.27 s to recompute a public receipt in a fresh clone (one run, 2026-09-28). The published npm package (2.54.0) does not carry this command; npx thetacog-mcp recompute-receipt lands with 2.55.0.
What a qualifying facility integrates. Four terms, each independently verifiable — the math, the hardware, and the transaction, with the philosophy left in the book where it belongs.
How an underwriting engine queries it — the Richter scale, not the kill-switch
A facility's underwriting engine queries the lattice to read whether a client's agent stayed in its commanded lane. A fleet-wide lane-jump is the correlated signal an accumulation model needs — the one thing that makes autonomous-agent liability writable at all: it turns an uncorrelated-because-invisible tail into a countable, signed event.
We make no claim to stop the drift. A Richter scale doesn't stop the earthquake — it makes it parametric, a number a policy or a bond can pay out on. We provide the LLM-free, recomputable measurement that the boundary was crossed — 0.90 in/out-domain separation, 10/10 out-of-domain rejection, 4.48σ against a scrambled null, with the honest open inch (paraphrase-invariance 0.30) published rather than hidden. What you build on that signal — an automated checker, a human-in-the-loop fallback — is yours.
That is why it survives counsel, not just diligence: once a decidable ruler exists, not consulting it is the negligence — the T.J. Hooper standard. Hundreds of live receipts recompute in the open at /commit. The boundary is the product, not a limitation of it.
Status
Open for bilateral execution with any qualifying commercial underwriting facility. This is a live, actively-maintained standard, not a one-time letter. First-access priority is determined by completion of the physical telemetry audit package — the technical threshold, not a relationship.
No partner facility is named on this page. When one executes and consents to disclosure, it is recorded here, sourced — never before. The absence of a name is the standard working as designed, not the absence of a standard.
thetadriven.com/standard • Protocol 144 • Open · non-binding · recompute every term yourself • US Patent App. 19/637,714
