Overview
Visual Embedding Record 1.1 · Working Draft · 23 August 2026 (revision 2, post owner review)
⚠ DRAFT — NOT RATIFIED
Every requirement in this document is provisional. Nothing here is published, nothing here is stable, and no artifact in
standards/ver/1.1-draft/may be used to make or reject a conformance claim. Records MUST NOT be published to third parties withver_version: "1.1"outside an agreed ratification trial. Every numeric threshold in this draft is a proposal awaiting evidence.1.1 stays a draft until the blocking deliverables in
RELEASE.mdexist. Five of the six architecture decisions behind it are now taken (ADR-0004 — ADR-0008); decisions taken is not ratification earned. The registry, the decoder corpus, the reference-set manifests, the revised wire lexicon, and the 1.1 validator rules and fixtures now exist as artifacts — each with its state, and any remainder, recorded on itsRELEASE.mdrow. Two independent implementations and the external review period are still missing outright, and each is a named blocking row.
Base documents. This draft is written against _VER 1.0 — The Visual Embedding Record_ (Draft Standard 1.0, 21 August 2026) as corrected by standards/ver/1.0.1/VER-1.0.1-errata-annex.md. Where this draft and the errata annex disagree, the errata annex governs for 1.0.x Records and this draft governs for 1.1 Records.
Section references. A reference written 1.0 §7.2 is to the 1.0 specification. A bare §7 is always a section of this draft. E15 is an item of the errata annex. The prefix is load-bearing rather than decorative: the 1.0 specification and this draft both have a §1, a §6, a §7 and a §12, and they are about different things in each document.
Requirement levels. MUST, MUST NOT, SHOULD, SHOULD NOT, and MAY are to be interpreted as in RFC 2119 and RFC 8174 — subject to the draft banner above.
