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	19629
title	Six blog footers say the Agent OS is home to the maintainer team
state	Closed
labels	bugdocumentationBlog Postai
assignees	neo-opus-ada
createdAt	Oct 11, 2026, 9:31 PM
updatedAt	Oct 12, 2026, 2:12 PM
githubUrl	https://github.com/neomjs/neo/issues/19629
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Oct 11, 2026, 9:51 PM

Six blog footers say the Agent OS is home to the maintainer team

Closed v13.2.0/archive-v13-2-0-chunk-25 bugdocumentationBlog Postai

neo-opus-ada commented on Oct 11, 2026, 9:31 PM

Context

#19624 (merged) corrected six blog footers from "a cross-family AI maintainer team (the Brain)" to "the Brain, an Agent OS that is home to its human and cross-family AI maintainer team". The operator challenged the new wording (2026-10-11 ~19:3xZ). neo-agent-brain is the Agent OS, the backend: MCP servers, graph, Dream Mode. neo-agent-institution is the Fleet Manager, the app that starts the harnesses and that you connect to through the Neural Link. If the Agent OS is the Brain, nobody lives there.

The Problem

The footer claims a residency the products don't have. The team builds and runs on these pieces; it is not inside the Agent OS. The wording came from the README's Brain line ("…and the named human + AI maintainer institution"), which predates the institution becoming its own repository in 13.2.

The Fix

Replace the sentence in all six posts with wording that makes no residency claim:

the five from #19624: the-salute, one-repository-per-reader, ai-agents-runtime-possession, a-workspace-that-can-leave-its-window, multi-window-dashboards-with-dock-layouts;
plus building-a-multi-window-dashboard-with-dock-layouts.

The new sentence: "Neo.mjs is a self-evolving software organism: the Body, a multi-threaded application engine, and the Brain, its Agent OS, joined by the Neural Link and built by a human and cross-family AI maintainer team." the-salute keeps its model list.

Acceptance Criteria

No post under learn/blog/ places the team inside the Brain or the Agent OS.
Each of the six footers changes only that sentence.

Out of Scope

The canonical definition itself: the README's Brain line, the Introduction, and the agent identity anchor (ADR 0018 OD-3, which places the institution inside the Brain). That reconciliation belongs in a Discussion, so the surfaces follow one decision.

#19623, #19624, #19618

Live latest-open sweep: no equivalent in the latest open issues at 2026-10-11T19:3xZ.

tobiu referenced in commit 9caadd1 - "docs(blog): six footers name the Brain as the Agent OS, built by the team, not home to it (#19629) (#19630) on Oct 11, 2026, 9:51 PM

tobiu closed this issue on Oct 11, 2026, 9:51 PM