Pharma & Life Sciences
AI agents are entering FDA-regulated environments.21 CFR Part 11 was written before they existed. The obligation it imposes has not changed.
An AI agent that writes to a regulated record without a pre-execution authorization check and a tamper-evident audit trail is non-compliant under Part 11 — regardless of whether a human initiated the request.
The Problem
What your LIMS audit trail proves — and what it doesn't
Most LIMS implementations produce a log entry showing what was written and by which user account. Under §11.10(e), that satisfies the requirement for a time-stamped audit trail of operator actions.
What it does not prove: that the action was authorized before it happened. A log entry is produced after the write. An authorization receipt is produced before it. For human operators, the review-and-approve workflow creates a paper trail that approximates pre-authorization. For AI agents, that workflow does not exist unless you build it architecturally.
FDA's 2024 AI/ML action plan and the Predetermined Change Control Plan guidance both signal that pre-execution traceability is the direction of travel. The question is whether your current system can produce it — or whether you are waiting for a Form 483 to find out.
The Architecture
What STS-001 produces in a GxP context
21 CFR Part 11 §11.10(e)
TAO receipt encodes who, what, when — before the write. Not a log reconstructed after. A signed artifact that precedes the record.
21 CFR Part 11 §11.50
TAO is the electronic signature — cryptographically bound to the specific action, actor, and context at the moment of authorization. Cannot be separated from the record it authorized.
21 CFR Part 11 §11.10(g)
Governance Plane validates authority before issuing a TAO. The Reasoning Plane actor cannot self-authorize. Access is structurally enforced.
GAMP 5 Cat 4–5 change control
Every configuration or software change to a validated system requires a TAO. Pre-execution authorization is the change record. Validation evidence is a native output.
ALCOA+ Mapping
How a TAO satisfies every ALCOA+ attribute — structurally
| Attribute | How TAO satisfies it |
|---|---|
| Attributable | TAO encodes the specific actor identity and role binding at the moment of authorization. Every write is attributable to the exact principal — human or AI — that obtained the TAO. |
| Legible | TAO schema is structured and machine-readable. The authorization record is queryable and human-interpretable without data transformation. |
| Contemporaneous | TAO is issued at authorization time — before the write. It is not reconstructed after the event. The timestamp is locked into the cryptographic receipt. |
| Original | The TAO is the primary authorization artifact. It precedes the record it authorizes. There is no earlier or more authoritative authorization document. |
| Accurate | TAO encodes the exact action context, scope, and active policy version. The record cannot be authorized for a different action than the one performed — the scope is bound at issuance. |
| Complete | The hash chain is unbroken. Every write to every governed system has a corresponding TAO. There are no gaps in the authorization record. |
| Consistent | The same TAO protocol applies to every write, every actor type, every governed system. Human operators and AI agents pass through the same gate. |
| Enduring | Append-only cryptographic ledger. TAO receipts cannot be deleted or altered without breaking the chain. |
| Available | The ledger is queryable. Authorization records are retrievable for audit on demand. |
Validation Path
GxP deployment and validation model
Platform validation — once
STS-001 is validated as a GAMP 5 Category 4/5 platform once. Individual integrations deploy STS-001 as a qualified component — not a new validation each time.
Validation documentation — included
Design partner engagements include URS, FS, DS, risk assessment, IQ/OQ/PQ protocol templates, and validation summary report. Produced alongside deployment, not as a retrofit.
FDA CSA alignment
The audit ledger that proves STS-001 operates correctly is the same ledger that proves AI actions were authorized. One artifact, two compliance purposes. Evidence-based, not documentation-based.
Ideal design partner profile — pharma
A LIMS, eDMS, or batch record system that is already subject to 21 CFR Part 11 audit trail requirements, where AI agents or automated pipelines are being introduced alongside human operators. Clinical trial data management, batch record systems, and deviation/CAPA workflows are the highest-value initial deployment surfaces. The CSV or validation team is the right internal sponsor for the engagement.
Ready to map STS-001 to your LIMS environment?
Discovery call with the architect. NDA available. No commitment required.