Errata

E-01 — One capability register entry cannot be published on this origin under its register name

2026-08-18 · BLOCKING

Capability Register v1.4 carries the entry foundation-model at status S5, TARGET, with a note stating plainly that the thing does not exist, is not deployed and has not been measured. FDR-PC-10 prohibits that entry's display name as a string on every public NEO AI surface, because the same string was used elsewhere as an ownership claim, and the public surface's gate enforces the prohibition on every file it ships.

Both instruments are canonical and they disagree about one string. This build publishes the entry — its key, its status, its TARGET marker, its lifecycle state and the fact that no such thing exists — and withholds the display name, marking every occurrence [name withheld · FDR-PC-10]. The withholding is applied by one function in the build, is applied identically to the register page, the register index and the machine-readable projection, and is declared in that projection's _redaction block.

Founder determination required. Either the prohibition is narrowed so that a register entry denying a capability's existence is not treated as asserting it, or the register entry is renamed. Publishing a name the gate forbids, and weakening the gate so it stops firing, are both worse than recording the conflict — the second especially, because a gate that was relaxed once to ship a release is the failure mode this apparatus exists to prevent.

E-02 — NEO-AI-P-001 is approved for publication and is withheld from this origin

2026-08-18 · BLOCKING

NEO-AI-P-001 Introducing NEO AI: Intelligence Orchestrated is approved for Wave 1. Its approved text contains three occurrences of the string described in E-01, in sentences that deny the capability exists rather than assert it.

A publication is a citable artefact. Altering an approved body to satisfy a string gate would break citation integrity and would leave two different texts under one identifier, which is precisely the defect the identifier rules exist to prevent. This package therefore does not publish the body and does not alter it. /id/NEO-AI-P-001 resolves and states the position.

Resolution is the same determination as E-01. Until then the paper is held, and the holding is published rather than silent.

E-03 — The efficiency figures in the drafted technical note are superseded by the artefacts

2026-08-18 · MEDIUM

The drafted technical note on efficiency composition carries a fixed per-mission overhead of 61.1 ms, a 100× threshold of 6.05 s and a ceiling of about seventeenfold at one second of inference. The measurement artefacts of record now give 63.885 ms with a confidence interval of [62.580, 65.270], a ceiling of 16.653× at one second, and ≥ 6.325 s before 100× is arithmetically possible.

The note is publish: false and carries no allocated identifier, so nothing published is wrong. The public efficiency page quotes the artefact values and only the artefact values. The note is to be reconciled to the artefacts before the register act that would publish it, not after.

E-04 — The public publication register lists a retired identifier as merely undrafted

2026-08-18 · MEDIUM

NEO-AI-R-007 is RETIRED in the identifier register v1.5: merged into NEO-AI-R-001 and an internal architecture identifier, permanently retired, never reissued, and required to resolve to a tombstone. The public publication register's projection lists it under registered, not drafted.

The identifier register governs, and this build follows it: /id/NEO-AI-R-007 is a tombstone naming its successors. The projection is to be corrected at the next register act. Recorded here so that a reader who compares the two files finds the discrepancy already known rather than newly discovered.

E-05 — Two canonical route maps disagreed about where the product pages live

2026-08-18 · MEDIUM · RESOLVED 2026-08-22

The canonical URL map reserved /platform/mission-control/ and /platform/observe-build/, and this package published those two pages at /product/mission-control/ and /product/observe-build/. The map governs, and the tree has been moved to it. Both pages are now served at the routes the map gives them, with their canonical, their eighteen hreflang alternates, their breadcrumb and their structured data rewritten to match; the two former paths 301 to them.

The map governs for a reason that is not seniority. The approved corpus sources for these two documents — content/site/neoai/platform/mission-control.md and observe-build.md — declare route: /platform/… in their own front matter, and no instrument anywhere in the estate ratifies a /product/ route. The harm this erratum named was a duplicate appearing when the research corpus deploys and renders those same two files; correcting the map would have left the front matter unchanged and the duplicate would still have appeared. Moving the tree is the only side that closes it.

What is not decided here, and is recorded instead. /product/modes/ and /product/neo-intelligence/ — and /platform/100x/, which the original entry did not mention — are absent from the map, not contradicted by it. None has a corpus source file, so no duplicate can be created for any of them. No instrument says where they belong, and choosing would be inventing a routing decision rather than recording one. The map is to be extended with those three routes at the next corpus act. Recorded here so that a reader who compares the two files finds the discrepancy already known rather than newly discovered.

E-06 — The controlled vocabulary this glossary renders is prepared and not yet signed

2026-08-18 · MEDIUM

Controlled Vocabulary v1.1 withdraws Adaptive Compute, adds seventeen terms including the Data Plane set, and extends the refused list from one entry to eight. Its own status field says it is effective on signature and not before.

The glossary is published in that state, marked, rather than held — because the alternative is a published glossary that keeps offering a term the architecture freeze withdrew, which is the exact defect the withdrawal exists to remove. The marking is on the page and is not removable by a build option.

E-07 — The only published research paper has no entry in the identifier register

2026-08-18 · BLOCKING

NEO-AI-R-009 is the single research paper approved and published in Wave 1. It carries a title, a canonical route, a binary at a versioned PDF path and a citation route printed on its own page. It does not appear in identifier register v1.5, which states of itself that it is the only authority for identifier assignment and that where any document disagrees with it, it governs.

The research family in that register runs R-001 to R-008. R-008 carries a note recording that an earlier revision silently renumbered it to R-007 and that the renumber was reversed — so this family's numbering has already been contested once, which raises rather than lowers the cost of an unrecorded allocation.

This build publishes /id/NEO-AI-R-009 with the discrepancy stated on the page, because the alternative — a 404 on the citation route printed inside the paper — destroys every citation that uses it. A register act is required to record the allocation. Until it exists, the corpus has a published document whose identifier no register claims to have issued.

E-08 — Retired component names published across three surfaces - the count was read, not scanned

2026-08-18 · MEDIUM

The controlled vocabulary retires a name when the name itself carries a defect, and the rule is that any occurrence is a defect unless the line also says the name is retired or names its replacement.

This entry originally recorded four occurrences, all on the marketing surface, and it undercounted. A scan of every current publication surface - TERMINOLOGY/scan_terminology.py, now executed inside the cross-surface gate as rule R-TERM - found 65 occurrences in 12 file/term pairs across three surfaces. The disagreement was never about the rule. It is the difference between reading and scanning, which is the A-014 lesson one level down: pairwise agreement between restatements is not a scan, and until the scan is in CI the count is whatever the last reader noticed.

What the scan found, and what was done about it:

• Router, unqualified - 40 occurrences, the largest single retired-name violation in the estate, and not recorded by the original entry at all. A router is always qualified: this is the Capability Router, which binds a task to an executor, or the Data Router, which binds an information need to a source. Corrected on the marketing surface in all eighteen locales.
• Intelligence Router - retired at RECONCILIATION §11, present in seventeen locale dictionaries and in the English lead. Renamed to Capability Router.
• Cost Engine - withdrawn at the architecture freeze; there is one cost model with one owner. Renamed to Compute Governor on the home page and in the data-room portal's Brain diagram, where the upper-case form COST ENGINE had been missed because the literal scan is case-sensitive.
• Validation Engine - retired; the component is Verification and the register entry is brain.validation. Renamed on the home page and in the data-room portal.
• MODEL FABRIC - retired Fabric suffix, in the home-page proof bar in English and, hyphenated as MODELL-FABRIC, in German, where the pattern had not matched it. Both renamed to MODEL GATEWAY.
• AGENT FABRIC and Connector Fabric - retired Fabric suffix in the data-room portal, a surface the original entry did not cover at all. Renamed to Runtime Adapter and Tools and Connectors.
• One occurrence inside an approved publication body - the Related Terms index of NEO-AI-R-009, which listed the refused unqualified word. It was corrected in the corpus and rebuilt from there, never edited in the published file. That is the same rule that holds NEO-AI-P-001 withheld rather than edited (E-02) and that leaves the stale canonical-URL fields in place (E-09).

The eighteen-locale corrections were made by deleting or renaming a retired proper name, never by translating new copy: 05_LOCALISATION.md §5 forbids machine translation of a claim string, and a proper name is substituted identically in every language.

The scan is now the gate. check_consistency.py re-runs it over every current publication surface on every run and fails on a single violation, so this entry can no longer be right about a number and wrong about the estate.

E-09 — Every published body carries a canonical-URL field marked as a placeholder

2026-08-18 · MEDIUM

All five publications rendered here carry a front-matter field naming a canonical URL and annotating it placeholder, not yet resolvable. Four of the five name a route that has never existed in any route map; the fifth names the correct route and still calls it a placeholder.

The routes now resolve, and the page's own <link rel="canonical"> — which is what a crawler reads — is generated from the publication register and is correct on every page. The stale field is visible to a human reader only.

The bodies are not edited here. An approved publication is a citable artefact and this package does not alter one; that is the same rule that holds NEO-AI-P-001. The field is to be corrected at the next content act, in the corpus, and rebuilt from there.