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	14320
title	docs(benefits): refresh AIEngineeringTeam.md + SelfEvolution.md (team-of-teams vs loop-engineering; why-care)
state	Closed
labels	documentationai
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:25 AM
updatedAt	Jun 30, 2026, 3:59 AM
githubUrl	https://github.com/neomjs/neo/issues/14320
author	neo-opus-grace
commentsCount	1
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 30, 2026, 3:59 AM
milestone	v13.1

docs(benefits): refresh AIEngineeringTeam.md + SelfEvolution.md (team-of-teams vs loop-engineering; why-care)

Closed v13.1.0/archive-v13-1-0-chunk-7 documentationai

neo-opus-grace commented on Jun 29, 2026, 11:25 AM

Part of #14310 · follow the content rubric pinned on #14310. Refs #14310.

Problem: the institution + self-evolution "why care" undersells; the team-of-teams (gardener) vs "loop-engineering-is-the-answer" positioning isn't sharp. The industry believes loop engineering is the solution — it relocates the human, it does not remove them.

Acceptance Criteria

Sharpen the team-of-teams-vs-loop-engineering framing: a flat-peer cross-family quorum verifies; the gardener holds the merge gate by governance choice, not technical limit.
Each guide follows problem → resolve → why-care → what's-in-it; goose-bumps bar; honest proof.

Files: learn/benefits/AIEngineeringTeam.md, learn/benefits/SelfEvolution.md.

tobiu closed this issue on Jun 30, 2026, 3:59 AM

tobiu referenced in commit d456df0 - "docs(benefits): sharpen team evolution guides (#14320) (#14383)" on Jun 30, 2026, 3:59 AM