Platform · Evidence

Every run produces a multi-artefact BLAKE3 evidence bundle.

Contract hash roots the chain. Per-step proof packets capture inputs / outputs / parameters / hardware / timing. Quality gates fail-closed. BLAKE3 Merkle root seals every release; attach an optional Ed25519 signature when you configure a signing key. The SDK ships an offline verifier — any tampering of the chain is immediately visible without trusting the runtime.

bundle.tar.zst
01contract.json
02run_log.ndjson
03artefacts.ndjson
04quality.json
05privacy.json
06utility.json
07telemetry.json
08sbom.json
09chain_seal.json
integrity verified · Ed25519 (when configured)
What's in the bundle

Nine artefacts, one chain.

Every run emits all nine. The final release_seal.json chains BLAKE3 hashes of the prior eight, making the bundle uniquely identifiable and tamper-evident. Offline verifier recomputes the chain in under a second.

contract.json01

The sealed contract — entities, relations, constraints, seed. The root of the chain.

run_log.ndjson02

Per-step proof packet — inputs, outputs, parameters, hardware, timing, tool code version.

artefacts.ndjson03

Inventory of every data artefact produced (name, size, content hash, MIME).

quality.json04

Per-column distributional drift, adversarial detectability, correlation preservation, constraint-violation counts. Fail-closed gates.

privacy.json05

Disclosure risk, membership-inference resistance, attribute-inference resistance, and the method used.

utility.json06

Downstream-task utility score plus task-specific utility metrics.

telemetry.json07

Entity counts, total rows, warnings surfaced during the run.

sbom.json08

Software bill of materials — every library + engine version that produced this bundle.

chain_seal.json09

Cryptographic hash of the canonical concatenation of the prior artefacts. An optional digital signature is attached when the customer's signing key is configured.

Trust no runtime

Verify any bundle offline.

The SDK ships rady evidence verify <bundle> — no network, no credentials. It recomputes the BLAKE3 chain, validates the optional Ed25519 signature against your trust root, and reports the Merkle root.

Exit 0 on success, 1 on any mismatch. Script it into CI. An auditor can re-verify any archived bundle on a fresh laptop without any RadMah AI dependency alive.

bash
$ rady evidence verify ./bundle.tar.zst

╭──────────────────────────────────────────────────╮
│ Verify → OK                                      │
│   Integrity           OK                         │
│   Signature           Ed25519 verified           │
│   Merkle root         b34bb1a5c7d2…e9fa          │
│   Bundle hash         f7c82e18a4bb…0e2d          │
│   Reason              integrity + Ed25519 verified│
╰──────────────────────────────────────────────────╯
(exit 0)
Deterministic replay

Same contract, same seed.
Byte-identical output.

The contract hash + seed together pin every stochastic source: RNG streams, cuDNN algorithm selection, cuBLAS workspace, thread counts, library versions. Re-run the same sealed job on a different cluster and the dataset hash matches byte-for-byte.

Makes regulatory replay a one-command exercise. Makes A/B debugging possible without "it worked on my machine" ambiguity.

determinism.json
{
  "contract_hash":     "a8f3b21c…a7e2",
  "seed":              42,
  "library_versions": {
    "python":  "3.13.12",
    "torch":   "2.5.1",
    "blake3":  "1.0.5"
  },
  "determinism": {
    "mode":          "strict",
    "final_hash":    "7e41ba90…c4d8",
    "rng_streams":   [ /* per-op stream fingerprints */ ],
    "cublas_workspace": ":4096:8"
  }
}

Evidence is how the platform works, not a feature.

Every run emits a multi-artefact bundle. Every customer gets the offline verifier. No premium tier.

Try a sample verify See CCTP physics engine