NEO AI Research Program
Updates
Register versions and corpus changes.
EN This publication is published in English only. Site navigation is available in 18 languages.
Register versions and what each one changed. A build output inside a corpus is a public surface: it is evidence of what the source said when the build ran, not of what the source says. Correcting a register without rebuilding leaves the corrected statement in a file nobody reads and the uncorrected statement on the host, so every register change here is paired with the rebuild that carried it onto this surface.
Corrections to published material are numbered separately, on the errata page.
| Register | Change |
|---|---|
Capability Register v1.1 | v1.1 added brain.evidence-layer, brain.evidence-ledger, assurance.eval-harness, mission.envelope. Corpus authors found these were mandated by the plane model but absent from the register, which made them unmentionable under LOCK v2 s2. |
Capability Register v1.3 | v1.3 Founder ratified the register's published S1-S5 maturity classifications. Individual capability lifecycle ratification states remain unchanged; register ratification is not evidence of deployment, target-environment testing or T4 capability ratification. |
Capability Register v1.4 | v1.4 recorded the architecture freeze in the public register: brain.router renamed Capability Router because an unqualified Router was ambiguous once four things routed; brain.cost-engine superseded by a single cost model with one owner, the separate component having been withdrawn; and the Data Plane added with its four parts, which the freeze identified as the layer that was missing rather than the layer that was wrong. No key was withdrawn, so no existing citation breaks. Added entries are UNCONFIRMED and none of them describes a deployed system. |
Publication Register v1.2 | PUBLIC PROJECTION. v1.2 adds two drafted technical notes that close gaps identified at architecture freeze. Both are publish=false and neither carries an allocated identifier: this file mirrors allocations and makes none. |
Controlled Vocabulary v1.1 | The extension is authorised by a vocabulary amendment that is prepared and not yet signed. This file is effective on signature and not before. v1.1 withdraws Adaptive Compute before signature, the concept having been rejected at architecture freeze as a name for a mechanism with no owner, and adds the Data Plane and efficiency-evidence terms the corpus now uses. |
Identifier Register v1.5 | Three reserved titles retitled to the scope of the documents now written against them. Same subject in every case, so no reissue and no renumber under register rule 1. SPEC-005 is deliberately NOT retitled: its registered title denotes a different specification and the collision is resolved by a new allocation, requested as erratum E-3. |