What a manifest carries

{
  "reference_set_version": "1",
  "space_id": "org.verstandard.space.clip-vit-b32/1.0",
  "items": [
    {
      "name": "01-gradient-scene.png",
      "content_sha256": "163dc8e9…",
      "pixel_sha256": "bd175fc1…",
      "vector_sha256": "2537406f…"
    }
  ]
}

(That is clip-vit-b32/manifest.json's first entry with each digest elided after eight characters. The prefixes are the real ones — an example digest in a document about not shipping example digests would be a poor joke.)

• content_sha256 — SHA-256 of the committed file's bytes, which is VER's identity.content_hash for that Asset.
• pixel_sha256 — the Canonical Buffer digest, verd.hashing.pixel_hash over verd.cpnp.canonicalize of those same bytes: `SHA-256("VER1:" + width + ":" + height + ":sRGB8:" ‖ raw)` per errata E10. Every reference item is an untagged RGB PNG, so CPNP-1 decodes, composites nothing, converts nothing and resizes nothing — the Canonical Buffer is the PNG's own pixels.
• vector_sha256 — SHA-256 of the packed vector octets defined below.

Draft §8.2 names these three facts per item in prose and defines no JSON Schema for the manifest — only the outer set_manifest_sha256 is schema-encoded. The shape above is the one RELEASE.md's worked example uses, and this directory adopts it unchanged so that the two do not describe different documents.

The items[] array is sorted bytewise-ascending by name, and the numeric filename prefix makes that order the documentation order too.