Evidence Dossier and receipt example

Synthetic worked example

Bind a runtime witness to a dossier claim

What does a computational provenance witness establish?

It binds execution environment, inputs, outputs, seeds, and artifacts to claim and dossier identifiers without claiming independent reproduction.

Starting inputs

A synthetic calculation claim

A calculation receipt identity

Hashed input and output artifacts

Runtime and environment metadata

Ordered execution

Work the example

  1. 1

    Validate the witness schema and receipt digest.

  2. 2

    Match dossier and claim identifiers.

  3. 3

    Match calculation receipt identities.

  4. 4

    Verify environment and artifact hashes.

  5. 5

    Retain the independentlyReproduced flag as false.

Expected outputs

  • A dossier-bound witness attachment
  • Execution-observed status
  • Explicit non-reproduction boundary

Verification checks

  • The witness digest recomputes.
  • Every attachment target exists.
  • Scientific validity remains uncertified.

Fail closed

Refusal conditions

  • Secrets appear in environment metadata.
  • The witness names another dossier.
  • One execution is called independent reproduction.

Digest-bound public fixture

Check the expected state

This fixture contains synthetic operational fields only. Its digest establishes fixture integrity, not scientific truth or a completed commercial transaction.

{
  "artifactKind": "runtime-witness",
  "schemaVersion": "maha-computational-witness/0.1",
  "input": {
    "claimId": "synthetic-claim-01",
    "randomSeed": "17",
    "inputArtifact": "sha256:synthetic-input",
    "outputArtifact": "sha256:synthetic-output"
  },
  "expected": {
    "executionObserved": true,
    "independentlyReproduced": false,
    "scientificValidityCertified": false
  },
  "artifactSha256": "sha256:66d41cd46b076b62206176f34453e76ba3253d1238c7baaa2056676c681f8e64"
}