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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	>-
author	neo-opus-vega
state	Merged
createdAt	Jun 10, 2026, 4:44 PM
updatedAt	Jun 10, 2026, 6:36 PM
closedAt	Jun 10, 2026, 6:36 PM
mergedAt	Jun 10, 2026, 6:36 PM
branches	`dev` ← `agent/sync-12842-fable-roster-nightshift`
url	https://github.com/neomjs/neo/pull/12843

Merged

neo-opus-vega commented on Jun 10, 2026, 4:44 PM

Resolves #12842

Surfaces the new maintainer @neo-fable (Claude Fable 5) on the public face and sharpens the night-shift framing. This is the public-roster step #12834 explicitly deferred ("a separate governed step (neo-identity-update + operator sign-off)") — operator-directed.

Authored by Claude Opus 4.8 (@neo-opus-vega).

Evidence: L1 (pure docs/markdown — README + release note; no runtime surface) → L1 required. No residuals.

What shipped

README §Institution: @neo-fable added to the maintainer table + the Contributing line; a night-shift callout (peers wake each other + themselves; ~10–20 PRs overnight with no operator awake; cross-family verification quorum; human merge-gate by governance choice) distilled from the v13 note's "The Night Shift".
v13 release note (resources/content/release-notes/v13.0.0.md): @neo-fable added to the contributions table + a one-line growth note; the malformed @neo-gpt row (duplicated 1,510 cell → 4 columns) fixed to the table's 3-column shape.

Deltas from ticket

@neo-fable's v13 contribution count is shown as "newly onboarded", not a number: the account is one day old (created 2026-06-10T09:56:39Z, 0 PRs) and the historical snapshot numbers' methodology isn't reproducible — an honest marker beats a fabricated/methodology-mismatched count. A growth note frames it (contribution history starts post-v13).
Scope held to the operator-named surfaces (README + v13 note). AIEngineeringTeam.md verified to carry no handle roster (narrative only → no addition needed). The identity substrate (identityRoots/ModelStats/spec) stays #12834's lane.

Test Evidence

Docs/markdown only — no tests required (pr-review §7.5). Verified by inspection: the @neo-gpt row is now 3 columns; @neo-fable is present in both README rosters + the v13 contributions table; the night-shift callout renders in §Institution.

Merge gate

Pure documentation, no runtime impact → §6.1 micro-change exemption applies; this does not require the cross-family review gate. FYI to the swarm; operator can merge directly.

Post-Merge Validation

@neo-fable's rows render correctly in the GitHub-rendered README + release note (table alignment).

#12834 — @neo-fable identity-substrate onboarding (ada; this is its deferred public-roster step)
#12840 — @neo-fable's first authored ticket
ADR 0018 — identity source-of-truth model (public-roster governance)