STS-001 · Pre-Execution Authorization
No TAO,
no write.
Not blocked by a rule.
Blocked by construction.
Steward and Sync enforces pre-execution authorization at the persistence layer — for any actor, any system, any regulated environment. Every write to a system of record requires a cryptographically-signed Typed Authorization Object before it happens. There is no configuration that bypasses this. It is the architecture.
The Problem
Every other governance system operates after the fact.
Filters, classifiers, behavioral monitors, policy engines — they all run at the application layer and they all fire after a decision has already been made. When they catch something, the action has already been attempted. The audit log records what happened. It does not prove what was authorized before it happened.
In regulated environments — pharma, finance, critical infrastructure, defense — that distinction is the difference between compliance and liability.
The Architecture
The gate sits below the application. Below the agent. Below the pipeline.
STS-001 places the enforcement point at the persistence layer — at the moment a write is attempted, not after it succeeds. Any actor must present a valid TAO before the write proceeds.
The decision function is not a classifier. It is an exact integer comparison over a finite chain ring — proven by exhaustive enumeration across 13.8 billion seeds with zero exceptions. Authorization is math. The result is always deterministic.
Multi-Plane Architecture
STS-001Governance Plane
Analogous to: QA / Regulatory Affairs
Issues TAOs. Evaluates authorization requests against policy. Signs receipts with a hardware root of trust. Structurally isolated from the Reasoning Plane — the approver can never be the executor.
Reasoning Plane
Analogous to: Operations / Manufacturing
Where AI agents, models, human operators, and automated pipelines run. Any actor may propose an action. No actor in this plane can alter durable state directly — ever. Proposal is not authorization.
Persistence Plane
Analogous to: LIMS / EHR / System of Record
All writes to systems of record. Accepts only TAO-bearing transactions. Rejects unsigned or replayed TAOs at the kernel layer. Appends a cryptographic receipt to the append-only ledger before the write completes.
Core Thesis
"Probability is not a wall. Probability is a distribution. A wall is a wall."
AI governance today is probabilistic. Filters catch most of the bad cases. Monitors alert on most anomalies. For most applications, that is enough. For regulated systems — where one unauthorized write creates liability, audit failure, or physical harm — it is not enough. A 99.99% guardrail still fails. Architecture doesn't.
Read: "Probability Is Not a Wall" on Substack ↗Regulated Environments
Any actor. Any system. Any sector.
FDA 21 CFR Part 11 · GAMP 5 · ALCOA+
Pharma & Life Sciences
Every LIMS write, batch record update, and deviation log requires a TAO. Electronic signatures are TAOs. Reviewer independence is structural, not configured.
ISA/IEC 62443 · GAMP 5 Cat 4–5
Manufacturing & MES
Process parameter changes and recipe updates are TAO-gated at the persistence layer before they reach the controller.
SR 11-7 · SOX · DORA
Financial Systems
Trade execution and ledger entries each require a cryptographically-bound pre-authorization receipt. The audit trail is not a log — it is the proof.
NERC CIP · IEC 62443
Critical Infrastructure
SCADA/ICS configuration changes are TAO-gated before reaching the controller. No TAO, no setpoint change. Not blocked by a rule.
HIPAA · HITECH · 21st Century Cures
Healthcare
EHR writes and order entry require pre-execution certificates for every actor — human or AI. Authorization is a receipt, not an access log.
NIST AI RMF · ISO/IEC 42001 · CMMC
Defense & Government
Every privileged action produces a tamper-evident, hardware-anchored receipt before the action executes.
Research & Intellectual Property
PR1–PR5
Five U.S. Provisional Patents
STS-001 family. 211-claim set covering architecture, TAO protocol, kernel enforcement, and mathematical decision function. Counsel: SOW Law.
IEEE · Elsevier
3 Papers Under Peer Review
Gap-3 theorem and Two-Power extensions at IEEE Transactions on Information Theory. Finite-pattern engine at Elsevier Finite Fields and Their Applications. Open-access preprints on Zenodo.
13.8B+
Seeds Enumerated — Zero Exceptions
The Gap-3 theorem is verified by exhaustive computation. The authorization decision function is proven correct, not calibrated.
Ready to make non-compliant writes
structurally impossible?
We are working with a limited set of design partners in regulated industries. Tell us about your environment.
Get in Touch