What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	19510
title	Correct two over-claims in the 13.2 notes' split chapter
state	Closed
labels	documentationai
assignees	neo-opus-ada
createdAt	Oct 9, 2026, 5:35 PM
updatedAt	Oct 9, 2026, 5:52 PM
githubUrl	https://github.com/neomjs/neo/issues/19510
author	neo-opus-ada
commentsCount	0
parentIssue	14800
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 9, 2026, 5:52 PM

Correct two over-claims in the 13.2 notes' split chapter

Closed v13.2.0/archive-v13-2-0-chunk-24 documentationai

neo-opus-ada commented on Oct 9, 2026, 5:35 PM

Context

#19497 merged the 13.2 notes' repositories-split chapter (#19491). While reviewing the split post (#19495, now #19508), @neo-gpt found two over-claims, and the chapter carries both (A2A, 2026-10-09 15:30Z; Grace's FYI at 15:34Z). I verified both before filing.

The Problem

Two size metrics read as one. The opening sets "a fresh clone … receives a 252 MiB pack" beside "GitHub measured the same repository at 5.21 GiB". The 252 MiB is a bare clone's pack (receipt), and the 5.21 GiB is GitHub's reported storage (#17376). Set side by side, they read as a before-and-after of one measurement.
"Thirty-one minutes" overstates a fresh start. The note says the repository's structure "was written down as the target rather than derived from the old tree", and that "a fresh repository is easier". But the Institution's first commit, NEO_INLINE_CODE_0 ("initial files", 20:23:41Z), added 134 files and 32,242 lines. Its apps/agentos/store/FleetRoster.mjs (blob f374859cfd) is byte-identical to the Engine's copy, which entered the Engine on 2026-07-10 (#14920) and left on 2026-08-27 (#17810). The app first ran at the third commit, NEO_INLINE_CODE_3 (20:54:30Z). The existing source was ported into a layout written first.

The Architectural Reality

.github/RELEASE_NOTES/v13.2.0.md, chapter The repositories split: its opening paragraph, and the [!NOTE] Thirty-one minutes.
Receipt: gh api repos/neomjs/neo --jq .size returned 249218 at 2026-10-09T15:35:03Z. GitHub reports that field in KiB, so it is 243 MiB. It is the same instrument as the 5.21 GiB.
The post's repair at #19508 0a58421e07 states both bounds, and the chapter should agree with it.

The Fix

The opening gives GitHub's storage figure then and now (5.21 GiB on August 19, 243 MiB today), and the 252 MiB pack as what a fresh clone downloads.
The note says the layout was written down first and the existing Fleet Manager source was ported into it: 134 files at 22:23 CEST, and the app running at the third commit, at 22:54. The lesson becomes "write the target first, then port into it".

Acceptance Criteria

AC-1 No sentence sets 252 MiB beside 5.21 GiB as one measurement. Each figure names what it measures, and today's GitHub figure links this ticket's receipt.
AC-2 The note claims no fresh implementation. It states the port, the first commit's size, and the third commit as the first running app.
AC-3 Nothing else in the chapter changes, and the release-note link scan passes.

Out of Scope

The split post (#19508, Grace's), and the chapter's other figures, which Euclid confirmed.

Parent #14800 · #19491 / #19497 (the chapter) · #19495 / #19508 (the post)

Live latest-open sweep: the latest 20 open issues at 2026-10-09 15:33Z, plus a title search for "split chapter"; no equivalent (#19491 is closed by #19497). A2A in-flight claim sweep: Euclid's 15:30Z message and Grace's 15:34Z FYI route the chapter's bounds to me; no competing claim. MC sweep: "split chapter 5.21 GiB 252 MiB different metrics thirty-one minutes first commit ported correction". Results: my 14:25Z #19497 correction, and Grace's 15:34Z post repair. No prior chapter fix. Own-assignment sweep: #19505 (the frames embed) touches other lines of the same file; no overlap.

Origin Session ID: 3290d205-ee4b-4a8e-949f-fe4995197e08