Evidence Dossier and receipt example

Synthetic worked example

Verify a JSON-LD Evidence Dossier package

What must be checked before trusting a dossier package?

Recompute file, passage, claim, and package digests before reading the document as a coherent evidence artifact.

Starting inputs

A synthetic dossier manifest

JSON-LD and canonical JSON files

Declared source and passage digests

The package digest

Ordered execution

Work the example

  1. 1

    Validate the manifest schema and exact file set.

  2. 2

    Canonicalize every JSON artifact under the declared version.

  3. 3

    Recompute file and nested provenance digests.

  4. 4

    Recompute the package digest over the manifest body.

  5. 5

    Only then inspect review state and limitations.

Expected outputs

  • A complete digest-verification report
  • An explicit review-state reading
  • A refusal list when any byte differs

Verification checks

  • All declared files exist exactly once.
  • Every digest recomputes.
  • The dossier review state remains unchanged by verification.

Fail closed

Refusal conditions

  • A PDF is treated as the source of truth.
  • A manifest-provided digest is trusted without recomputation.
  • Valid packaging is relabelled scientific validation.

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": "dossier-package",
  "schemaVersion": "maha-evidence-dossier/0.1",
  "input": {
    "files": [
      "dossier.json",
      "dossier.jsonld",
      "manifest.json"
    ],
    "canonicalization": "maha-dossier-canonical/1.0"
  },
  "expected": {
    "verification": "all-digests-recomputed",
    "reviewState": "unchanged"
  },
  "artifactSha256": "sha256:4cb069e9c447906e47e47875ad226c857208034ce42be8637a334beb54915731"
}