Attestations should attach to individual artifacts rather than to a release, because a release can gain artifacts over days as new platforms are built. Package ecosystems should therefore accept several attestations per release, support one artifact having many attestations, and give a way (implicit, such as a naming scheme, or explicit, by where it is published) to map an artifact to its provenance, which should accompany the artifact at publication. The provenance file name should derive from the artifact's name (for example the in-toto convention of a .intoto.jsonl suffix).
The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.