How a Record cites a snapshot

provenance.registry names the snapshot the Record's registry-dependent values were minted against — its version and sha256, optionally its uri:

{
  "provenance": {
    "registry": {
      "version": "1",
      "sha256": "ea0fab7379049ff86e77be87d7db84efd818177ba6d5e5e66fd82ab34b9c09a5",
      "uri": "https://verstandard.org/registry/snapshots/1/registry.json"
    },
    "chain": [
      {
        "at": "2026-08-25T09:15:00Z",
        "actor": "did:plc:example",
        "action": "export",
        "tool": "example-pipeline/1.2.3"
      }
    ]
  }
}

The 1.1 draft schema requires provenance.registry whenever the chain carries a bare token outside the sixteen the specification itself defines; an authority-namespaced token (com.example.pipeline/watermark) needs no snapshot, because its authority defines it.

Note what that means for snapshot 1 specifically: its provenance_action list is exactly the sixteen §2.3 defines, so no Record needs to cite snapshot 1 in order to resolve a token. Citing it, as above, states which snapshot the Record was minted against. The citation becomes load-bearing at the first snapshot that registers a seventeenth action.