CVP Errata

Canonical URL: /developers/cvp/errata
Role: Correction / history ledger — not a second normative document
Normative source of truth: /developers/cvp/spec/1.0 (the specification text alone)
Last updated: 2026-09-08
Overview: CVP

Implementers MUST treat the published specification as complete. Reading this ledger is optional history; it does not add obligations beyond what is already incorporated into the cited specification revision.

Data model (version-aware from day one; URL may stay flat):

Erratum:
  id: E1
  applies_to: CVP 1.0
  status: open | incorporated | superseded | withdrawn
  published_at: …
  incorporated_in: …   # when status = incorporated
  summary: …

Future anchors (optional): /developers/cvp/errata#cvp-1.0, or later /developers/cvp/spec/1.0/errata.

---

CVP 1.0

E1 — reference_scope

Field	Value
id	E1
applies_to	CVP 1.0
status	Incorporated
published_at	2026-09-05
incorporated_in	1.0.0-proposed final
summary	Each independent reference item MUST declare reference_scope ∈ { model | expected_values | numerical_behavior | all }; CVP-REF-01 PASS requires claim coverage by scope.

Normative text lives in the specification (CVP-REF-01). This entry is historical only.

---

E2 — Attestation example hygiene

Field	Value
id	E2
applies_to	CVP 1.0
status	Incorporated
published_at	2026-09-05
incorporated_in	1.0.0-proposed final
summary	Unsigned integrity mode MUST NOT imply a signature (key_id / signature / statement_sha256); signed mode includes all three.

Normative text lives in the specification (§11 attestation). This entry is historical only.

---

E3 — Proposed badge wording

Field	Value
id	E3
applies_to	CVP 1.0
status	Incorporated
published_at	2026-09-05
incorporated_in	1.0.0-proposed final
summary	While document_status is proposed, UI MUST show Proposed in the badge itself; bare CVP VERIFIED is forbidden until Stable.

Normative text lives in the specification (§16 conformance & badge copy). This entry is historical only.

---

E4 — Exact-integer numerical profile

Field	Value
id	E4
applies_to	CVP 1.0
status	Incorporated
published_at	2026-09-08
incorporated_in	1.0.0-proposed
summary	Exact integer IUT MUST declare representation=exact_integer, arithmetic (e.g. BigInt), comparison=exact_equality, tolerance=0. ULP fields (error_ulp, threshold_ulp, max_error_observed, precision_bits) MUST NOT be emitted. Host IEEE-754 is a runtime dependency, not the numeric model.

Normative text lives in the specification (§7 numerical policy). This entry is historical only.

---

Open errata

None. E1–E4 are incorporated into 1.0.0-proposed. No open errata are required before public Proposed release.

After Stable 1.0, newly discovered normative ambiguities SHOULD be recorded here as open errata (e.g. E5+) until incorporated into a revised specification revision.

---

Deferred (not errata)

Item	Notes
Formal JSON canonicalization (beyond sorted keys / whitespace)	Required before relying on signed manifest_sha256 cross-language
Signing infrastructure	Optional for Proposed; land before making signatures Required
Protocol validation on heterogeneous calculators	Gate for Stable 1.0, not for Proposed publication

---

Errata ledger — CVP 1.0 · E1–E4 incorporated