Evidence Dossier and receipt example

Synthetic worked example

Render a PDF only after package verification

Why must the PDF remain a presentation layer?

The human-readable report is derived from already-verified package data and never becomes a second source of truth.

Starting inputs

A verified dossier JSON package

A deterministic section order

A fixed renderer version

No editable source claims in the PDF step

Ordered execution

Work the example

  1. 1

    Verify the dossier package first.

  2. 2

    Render only fields present in the verified object.

  3. 3

    Record the PDF file digest in a new package manifest.

  4. 4

    Check pagination and visible boundaries.

  5. 5

    Distribute JSON-LD with the PDF.

Expected outputs

  • A readable PDF report
  • A digest for the rendered file
  • The original machine-verifiable package beside it

Verification checks

  • Every PDF section maps to a package field.
  • The PDF digest changes after any rendering-byte change.
  • JSON-LD remains authoritative for machine verification.

Fail closed

Refusal conditions

  • The PDF contains new prose.
  • The PDF is generated from an unverified package.
  • A visual correction silently edits evidence.

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": {
    "verifiedPackage": true,
    "renderOrder": [
      "scope",
      "claims",
      "sources",
      "limitations"
    ],
    "renderer": "pinned"
  },
  "expected": {
    "pdfAddsClaims": false,
    "machinePackageIncluded": true
  },
  "artifactSha256": "sha256:61781468aefc03bc9064c4a536a4bb154cd3259d23bcc22b0d96aea45c084f79"
}