Tamper-evident evidence for consequential operations.
Evidence Layer records what was requested, what was checked, what was approved or denied, and what proof existed at the time -- without requiring sensitive operational data to leave controlled infrastructure.
Audit trails often show edits. They do not always prove the decision context.
In regulated and high-consequence operations, the question is not only whether a record changed. The harder question is what the operator requested, what state the system was in, what checks passed or failed, and whether the evidence existed before later dispute.
Every decision leaves a verifiable trace.
Evidence Layer turns a consequential action into a structured evidence packet that can be reviewed by operators, auditors, investigators, or counterparties.
| Field | Purpose |
|---|---|
| Request hash | Identifies the action without exposing the full content. |
| Operator metadata | Shows who or what participated in the decision. |
| Gate outcomes | Shows why the action was approved, denied, routed, downgraded, or held. |
| State freshness | Shows whether the system was current enough to trust at the moment of decision. |
| Timestamp | Places the event in operational time. |
| Witness record | Records independent confirmation or co-signing by a second party or node. |
| External anchor | Makes later alteration of the packet detectable by an independent reviewer. |
| Review note | Gives auditors a human-readable explanation of the decision path. |
Validity can be public. Data can stay private.
Evidence Layer separates the proof of integrity from the sensitive content itself. Full operational records remain inside controlled infrastructure. Hashes, timestamps, anchors, and permissioned packets can prove integrity without publishing regulated data.
| Layer | Externally visible? | Purpose |
|---|---|---|
| Full operational record | No | Remains in the controlled environment. |
| Hash / digest | Selective | Proves content integrity without revealing content. |
| Timestamp / anchor | Yes | Supports ordering and existence evidence. |
| Witness metadata | Permissioned | Shows who or what participated, under access control. |
| Audit packet | Permissioned | Supports inspection, dispute, or investigation by named reviewers. |
External anchoring makes later alteration detectable.
Evidence Layer can anchor cryptographic evidence to an available public network. The network does not need to contain the regulated data. It only needs enough proof material to make later changes detectable and to support an independent existence window.
The evidence model can support bounded timestamping: an internal record references a public chain tip, then anchors a digest in a later block. This creates evidence that the record existed after one public state and before a later public confirmation.
Anchoring is one mechanism inside a broader evidence chain. The full anchor lineage, public-network receipt detail, and reduction-to-practice records live on the Proof page, not here. Evidence Layer is the product surface; the proof receipts are the credibility surface.
Designed for audit, inspection, and dispute review.
| Requirement family | Evidence Layer support |
|---|---|
| ALCOA+ | Supports attributable, legible, contemporaneous, original, and accurate evidence design, with complete, consistent, enduring, and available record properties. |
| 21 CFR Part 11 | Supports electronic record and electronic signature review, audit controls, and integrity evidence for systems operating under Part 11 scope. |
| GxP investigations | Shows request, state, decision path, and outcome -- the four elements an investigation needs to reconstruct what happened. |
| Chain of custody | Supports witnessed handoff and custody movement records for samples, materials, data, and regulated artifacts. |
| Cyber / incident response | Separates attempted action, approved action, blocked action, and later investigation into distinct evidence layers. |
ALCOA+ in full
ALCOA+ is a data-integrity framework codified in FDA, MHRA, and WHO guidance for regulated electronic records. The nine elements:
One event, multiple review surfaces.
Pair with MMS for prevention plus proof.
MMS controls whether a consequential action can execute. Evidence Layer proves what happened around that decision.
| MMS | Evidence Layer |
|---|---|
| Pre-execution control | Post-decision proof |
| Prevents unsafe action | Proves decision context |
| Gates, thresholds, denials | Hashes, timestamps, receipts |
| Operational authorization | Audit and compliance evidence |
Make your audit trail harder to dispute.
Start with one decision class: release, override, model promotion, custody transfer, or privileged approval. Evidence Layer instruments the decision and produces a structured packet that survives later review.