§1 How to read the ledger
Every table below carries the same six columns.
ID — the item's stable identifier. Five namespaces appear:
| Prefix | Meaning |
|---|---|
D1–D15 | The fifteen Appendix D known issues of the Studio PRD |
E1–E29, N1–N6 | Items and editorial notes of the 1.0.1 errata annex |
REV-nn | Dispositions of the 23 August 2026 owner review (§10) |
ADR-000x | Architecture decision records under docs/adr/ |
VERxxx | Conformance-profile error codes (vera-profile/1.0) |
| everything else | Audit finding identifiers, verbatim from the audit report |
Historical spelling. Earlier working notes on this track cited the Appendix D issues as K<n>. K<n> is the same item as D<n>, cited in published documents as App. D #<n>. K is not a namespace of this ledger and no shipped document uses it; the mapping is recorded here only so that a reader holding an older note can resolve it.
Audit-ID disambiguation. Five auditors worked in parallel and eight identifiers collide across their reports. This ledger disambiguates with a suffix, and so does every other document on this track:
- bare
SPEC-nn— the standards-fresh-eyes auditor (specification text) SPEC-nn-emb— the embedding-index auditor (spaces, vectors, retrieval)SPEC-nn-core— the core-pipeline auditor (CPNP, hashing, record assembly)
The eight collisions are SPEC-01, SPEC-02, SPEC-03, SPEC-05, SPEC-06, SPEC-07, SPEC-08, SPEC-09. Every other identifier is unique.
Source — where the item came from: App. D #n for an Appendix D issue, §16.x for a Studio PRD §16 disposition, or the audit workstream that found it (audit/spec, audit/core, audit/embed, audit/wire, audit/tests).
Classification — the change class the item belongs to, as classified by the audit. This is a property of the change, not of where it shipped:
| Value | Meaning |
|---|---|
editorial | Wording; no requirement changes |
patch-correction | Corrects or disambiguates an existing requirement without adding capability |
additive-1.1 | Needs a new field, value, or capability |
breaking-major | Would change a pixel_hash universe, remove a field, or narrow a value space |
open-ADR | Blocked on a decision that has not been made |
implementation-only | A defect of the reference implementation, not of the standard |
process | Repository, test, or tooling hygiene |
Disposition — where the item actually landed: fixed-in-1.0.1, drafted-in-1.1, validator-rule VERxxx, ADR-000x, fixed in this branch, or documented. Classification and disposition can disagree, and where they do the reason is stated: several patch-correction items were deferred to 1.1 because ADR-0002 capped the 1.0.1 schema delta at three changes.
Status — Closed (a decision exists and has shipped), Draft — ratification required (drafted in 1.1, not ratified), Open (a decision is required), Deferred (recorded, deliberately not acted on).