21 CFR Part 11 governs electronic records and signatures in FDA-regulated industries. Section 11.10(e) requires secure, computer-generated, time-stamped audit trails to independently record the date and time of operator entries and actions that create, modify, or delete electronic records, and adds that record changes shall not obscure previously recorded information. The audit trail must be retained at least as long as the record itself, and be available for agency review and copying.
Section 11.10(a) requires the system to be validated for, among other things, the ability to discern invalid or altered records. That is the property under scrutiny: can anyone tell whether the record was altered, and can they tell it without taking the operator's word for it.
In practice the audit trail lives inside the operator's validated system, an EDC, LIMS, or MES. Its integrity rests on that system being trusted, and on the operator not altering the store beneath it. FDA data-integrity enforcement, the warning letters and Form 483 observations, is largely about this exact failure: audit trails switched off, records backdated, results overwritten. Validation raises the bar inside the system. It does not give an outside investigator a way to check the record without trusting that system.
Each audit-trail entry is hash-chained, so every entry commits to the one before it, and the head of the chain is written as a leaf into a public transparency log at log.markovianprotocol.com, an append-only log outside the operator's control. Seven independent witnesses, including Geomys and Google's transparency.dev witnesses, cosign the log checkpoint hourly, and checkpoints are anchored to Bitcoin via OpenTimestamps. An investigator recomputes the chain from the records, which needs nobody, then checks inclusion of the head in the witnessed log from public endpoints. Once the checkpoint is anchored to Bitcoin, the head is checkable against the Bitcoin blockchain itself, independent of Markovian too.
An edit to any historical entry breaks the chain and no longer matches the anchored head. The regulation says record changes shall not obscure previously recorded information. This layer does not stop an operator editing their own database, it makes any such edit detectable by anyone, against a log the operator does not control and whose history is countersigned by independent witnesses. It maps to the ALCOA principles the FDA reads records by, strengthening the Original, Accurate, and Enduring properties in particular.
The same art12_audit_trail.py mechanism applies to a Part 11 audit trail. Each entry records the operator action, the record affected, the time, and a link to the entry before it. The chain head is anchored to Bitcoin and verified by recomputation.
Markovian provides the tamper-evidence and verifiability layer on top of the audit trail your validated system already produces. Validation, capture, and retention stay yours, and it is not a Part 11 compliance solution or regulatory advice.