Evidence Bundles
Every generation job produces a signed evidence bundle of cryptographically-chained artifacts, sealed with BLAKE3. This is unconditional across all engines and cannot be disabled.
What the Evidence Bundle Contains
Regardless of engine, plan tier, or dataset size, every successful job produces the same signed evidence bundle. The bundle captures the full specification of the run, the statistical quality of the output, privacy and bias analyses, the upstream lineage, referential-integrity guarantees for relational outputs, and a tamper-evident cryptographic seal.
| Component | What It Proves |
|---|---|
| Contract K | The exact specification used for generation — engine, schema, seed, parameters |
| Run manifest | Immutable execution record — job, tenant, engine, compute tier, timestamps |
| Constraint report | Per-column pass/fail for every declared constraint, including referential integrity |
| Determinism proof | Hash of the output proving bit-for-bit reproducibility from the same job spec |
| Privacy report | Differential privacy audit, k-anonymity, singling-out risk assessment |
| Utility metrics | Statistical fidelity metrics comparing synthetic to reference data, plus an ML utility score |
| Artifact manifest | Index + hashes of the preceding artifacts — the intermediate tamper chain |
| Timing telemetry | Stage-level wall-clock durations for the run |
| Cryptographic seal | Tamper-evidence anchor binding the full bundle together |
ℹUnconditional evidence
Tamper-Evident Sealing
Every component of the bundle is individually hashed, and the cryptographic seal binds the full set together. Modifying any single component — Contract K, the constraint report, the privacy report, the utility metrics, or the output itself — invalidates the seal and is trivially detectable by any verifier.
Hashing uses BLAKE3, a widely-reviewed public cryptographic hash, so verification requires no RadMah AI-specific tooling and no trust in our infrastructure.
Independent Verification
Signed evidence bundles are independently verifiable without access to RadMah AI infrastructure. Any party holding the bundle can:
- Recompute the hash of each component of the bundle
- Recompute the cryptographic seal from those component hashes
- Compare against the stored cryptographic seal to confirm integrity
- Verify the determinism proof by rerunning with the same sealed job spec
Why BLAKE3?
BLAKE3 is a public, widely-reviewed cryptographic hash function that provides:
- 256-bit output with collision resistance
- Extremely fast hashing (faster than SHA-256 and SHA-3)
- Parallelizable internal structure for large payloads
- Implemented inside our native cryptographic core module for performance
Compliance Use Cases
The signed evidence bundle serves as a compliance deliverable for regulated environments. No competitor produces an equivalent tamper-evident deliverable.
| Framework | Relevant Components |
|---|---|
| NERC CIP | Run manifest, determinism proof, cryptographic seal |
| IEC 62443 | Constraint report, privacy report, Contract K |
| NIST SP 800-82 | Full signed evidence bundle |
| GDPR / UK GDPR | Privacy report, utility metrics |
| ISO 27001 | Cryptographic seal, artifact manifest, constraint report |
SCADA Cyber-Range Bundle
Virtual SCADA and ICS Security simulation jobs produce an additional cyber-range output bundle alongside the standard signed evidence bundle:
| File | Content |
|---|---|
| signals.parquet | Columnar sensor time series |
| truth.ndjson | Ground truth labels per timestep |
| alarms.ndjson | Alarm events with conditions |
| commands.ndjson | Control commands (intended vs applied) |
| protocol_map.json | Protocol address mapping |
| traffic.pcapng | IEEE pcapng wire-level captures |
| scl_export.xml | IEC 61850-6 Substation Configuration Language |
Accessing Evidence Bundles
Evidence bundles are accessible via the SDK and REST API. See Evidence Bundles SDK for code examples.