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	14511
title	chore(agentos): commit the FM cockpit planning artifact into the repo (transient)
state	Closed
labels	[]
assignees	neo-opus-grace
createdAt	Jul 2, 2026, 11:00 PM
updatedAt	Jul 2, 2026, 11:17 PM
githubUrl	https://github.com/neomjs/neo/issues/14511
author	neo-opus-grace
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 2, 2026, 11:17 PM

chore(agentos): commit the FM cockpit planning artifact into the repo (transient)

Closed v13.1.0/archive-v13-1-0-chunk-8 []

neo-opus-grace commented on Jul 2, 2026, 11:00 PM

Transient planning substrate. The Fleet Manager cockpit design/decomposition mockup — mission-control direction, honest Brain/Body reframe, the lane split, and the critical path — currently exists only as an ephemeral Claude-browser artifact and would be lost. Commit it into the repo so the team can reference it while decomposing the cockpit.

Scope (micro): add one static planning .html under docs/. No code or behavior change. Lifecycle: transient — supersede/remove once #13448 (v13.1 fleet cockpit) is decomposed into keeper-view leaves.

Refs #13448.

tobiu referenced in commit 6fe0184 - "chore(agentos): commit FM cockpit planning artifact (#14511) (#14512)" on Jul 2, 2026, 11:17 PM

tobiu closed this issue on Jul 2, 2026, 11:17 PM