Skip to content
VERASPEC
Repository
Errata ledgerstable

§3 Errata annex items E1–E29

The normative content of each item is in the annex; this table records only its classification and status. Source column lists the findings each item resolves.

Five items — E3, E6, E7, E8, E9 — resolve a place where 1.0.0 admitted two readings that produced different Canonical Buffers. Resolving an ambiguity selects one reading, so Records produced under a non-selected reading are non-conformant and their pixel_hash values are withdrawn, not recomputed. One item — E15 — is a deliberate relaxation of 1.0.0. COMPATIBILITY.md §4.1 and §4.2 state both classes in full; the rows below mark them.

IDTitleSourceClassificationDispositionStatus
E1The identity gradient overstates what pixel_hash survivesSPEC-01, SPEC-07, MOD-02, THESIS-01, SPEC-PIXHASH-TOLpatch-correctionfixed-in-1.0.1Closed
E2image.width/height are Canonical Buffer dimensionsSPEC-04, SPEC-01-core, WIRE-33patch-correctionfixed-in-1.0.1Closed
E3The quantize step is a scale, not a clipCPNP-04, SPEC-11breaking-major (as audited)fixed-in-1.0.1 — ambiguity resolved, scaling selected; clip-reading pixel_hash values withdrawn (COMPATIBILITY.md §4.1)Closed
E4Alpha compositing operates in the 8-bit domainSPEC-05, CPNP-11patch-correctionfixed-in-1.0.1Closed
E5Rendition selection happens at decodeSPEC-06, CPNP-02patch-correctionfixed-in-1.0.1Closed
E6One orientation source, and out-of-range values are uprightSPEC-09, CPNP-08, SPEC-ORIENT-OORpatch-correctionfixed-in-1.0.1 — ambiguity resolved, EXIF tag 274 selected (COMPATIBILITY.md §4.1)Closed
E7Animated sources: first frame, definedSPEC-10patch-correctionfixed-in-1.0.1 — ambiguity resolved, coalesced logical frame 0 selected (COMPATIBILITY.md §4.1)Closed
E8A present-but-unusable ICC profile fails closedCPNP-07, SPEC-26, CPNP-06 · §16.2patch-correctionfixed-in-1.0.1 — ambiguity resolved; canonical identity withdrawn entirely for such assets (COMPATIBILITY.md §4.1)Closed
E9CPNP-1 consumes only an embedded ICC profileSPEC-08patch-correctionfixed-in-1.0.1 — ambiguity resolved, no other colour metadata consumed (COMPATIBILITY.md §4.1)Closed
E10The pixel_hash preimage, byte for byteSPEC-12, SPEC-13patch-correctionfixed-in-1.0.1; the domain-tag/cpnp_version coupling is a declared 1.x limitationClosed
E11What a preserved raw segment is, per containerREC-03, EX-01, SCH-16patch-correctionfixed-in-1.0.1; validator-rule VER1302Closed
E12"Conformant decoder", definedCPNP-05, WIRE-23, EMB-03 · §16.1patch-correctionfixed-in-1.0.1; the first implementation profile and reference corpus were published 25 August 2026 at standards/decoder-corpus/1/ (verd-pillow/1; one toolchain evaluated — the second is RELEASE.md row 14's evidence)Closed
E13Conformance-table correctionsSPEC-03, SPEC-21, SPEC-09-emb (embedding-index), REC-08, SCH-15patch-correctionfixed-in-1.0.1 — "full space descriptor" = the complete §6.1 field set, reference plus the per-kind preprocessing members; validator-rule VER404/VER405Closed
E14Reconciliation precedence, completedSPEC-17patch-correctionfixed-in-1.0.1Closed
E15Redaction: which shape goes where, and the raw-preservation carve-outSPEC-02, SCH-14 · §16.5open-ADR → additive-1.1fixed-in-1.0.1 for the shape — the one deliberate relaxation: preservation is subordinate to redaction, the segment MUST be omitted (COMPATIBILITY.md §4.2); mandatoriness decided by ADR-0006 for 1.1 records only (§10 REV-18); validator-rule VER1001/VER1002/VER1005 unchanged for 1.0.xClosed
E16record_id and created_at, definedSPEC-15, SPEC-16, REC-09, REC-10, IMPL-RECORD-ID-COLLIDES, WIRE-24patch-correctionfixed-in-1.0.1; validator-rule VER1201–VER1204Closed
E17The signature payload, definedSPEC-14patch-correctionfixed-in-1.0.1; validator-rule VER1401–VER1403Closed
E18space_id is unique within a RecordApp. D #14, WIRE-32patch-correctionfixed-in-1.0.1; validator-rule VER401Closed
E19Grade is derived from source.class, not carriedSPEC-23, SPEC-06-emb, TEST-GRADE-TOKEN, WIRE-09patch-correctionfixed-in-1.0.1 — normative derivation table, no new fieldClosed
E20Fused recipe inputs, definedSPEC-08-emb, SCRIPT-FUSED-RECIPE-INPUTSpatch-correctionfixed-in-1.0.1; validator-rule VER704Closed
E21Availability: family naming, other segments, and basis scopeApp. D #9, SCH-12, SCH-13, SPEC-03-core, REC-05, SPEC-AVAIL-BASIS-SCOPEpatch-correctionfixed-in-1.0.1; per-family basis and other states are drafted-in-1.1 §10.3Closed
E22Digest encodings and registered perceptual algorithmsHASH-02, SCH-07, App. D #1patch-correctionfixed-in-1.0.1 — schema delta 1; full parameter pinning deferred to the 1.1 registryClosed
E23Validators MUST assert format and contentEncodingSCH-01, SCH-02patch-correctionfixed-in-1.0.1 — profile strictness; validator-rule VER202Closed
E24Vector carriage: exactly one, dtype inheritance, and byte layoutSCH-08, SCH-09, App. D #15, REC-07, WIRE-10, WIRE-11patch-correctionfixed-in-1.0.1; validator-rule VER601–VER606, VER1301; mandatoriness is ADR-0008Closed
E25source_bytes_ref points at the Asset content_hash coversSCH-18patch-correctionfixed-in-1.0.1; validator-rule VER1305Closed
E26The shipped example artifacts are illustrative, not verifiedApp. D #13, EX-01, EX-02, EX-03, EX-04 · §16.13patch-correctionfixed-in-1.0.1 — five example edits (a)–(e) plus a standing illustrative-artifact noticeClosed
E27pixel_hash is a grouping key, never a primary keyApp. D #7, SPEC-27, DOCTRINE-PIXHASH-HALF-APPLIED, MIG-04, WIRE-22 · §16.11patch-correctionfixed-in-1.0.1 — non-normative guidance; CLAUDE.md corrected in this branchClosed
E28C2PA state consistency, and what "MUST be validated" means in 1.0SCH-17, App. D #12, REC-02patch-correctionfixed-in-1.0.1; validator-rule VER1101/VER1103; unverifiable is drafted-in-1.1 §6Closed
E29model.weights_sha256 has no defined preimage in 1.0.xApp. D #5, SC-01, SC-02, SC-03, MOD-04patch-correction (normative scope note)fixed-in-1.0.1 — 1.0.x values are comparable only within a producer; the interoperable construction is ADR-0007's bundle manifest, drafted-in-1.1 §4Closed