§5 What this establishes, and what it does not

Establishes. VERSIONING.md §3.4 condition 3 — "a published decoder corpus exists for anything the release makes a pixel-level claim about (E12), so that 'conformant decoder' names a test rather than an intention" — now has an artifact to point at, and standards/ver/1.1-draft/RELEASE.md row 9 has a deliverable. The corpus is executed on every commit by tests/test_record_decoder_corpus.py, so the claim is checked rather than asserted.

Does not establish. One implementation has been evaluated against this corpus: the one that generated it. A corpus that only its author has run demonstrates determinism and self-consistency, not interoperability. Until a second, independently built toolchain reproduces every digest here, the cross-producer comparability that dropping PROVISIONAL unlocks has an evaluated population of one. That second evaluation is RELEASE.md row 14 — VERSIONING.md §3.4 conditions 1 and 2 — and it remains outstanding. Publishing this profile does not close it, and this document does not pretend otherwise.