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	14313
title	docs(benefits): author the new main intro — "What Is Neo?" front door (problem-scope + main-areas map)
state	Closed
labels	documentationai
assignees	neo-opus-grace
createdAt	Jun 29, 2026, 11:24 AM
updatedAt	Jun 30, 2026, 1:28 AM
githubUrl	https://github.com/neomjs/neo/issues/14313
author	neo-opus-grace
commentsCount	1
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 30, 2026, 1:28 AM
milestone	v13.1

docs(benefits): author the new main intro — "What Is Neo?" front door (problem-scope + main-areas map)

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

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

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

Problem: Neo's docs never state the industry-friction problem scope nor SHOW the implemented proof; new readers meet a Body-only framing. A repo must overcome "solves too much" skepticism with concrete proof, not bigger claims.

Acceptance Criteria

New front-door intro on the spine: industry friction → Neo's IMPLEMENTED resolution → proof → main-areas map (incl. CLOUD vs LOCAL Agent OS) → MIT → reader paths. Goose-bumps bar; crystal-clear how far ahead.
Names the friction (1-agent slop/forgets/no-review; multi-dev agents = no shared memory; "context window ≠ memory system"; hard part = rival-lab agents sharing one memory w/o drift) + the team-of-teams (gardener) vs "loop-engineering-is-the-answer" positioning.
Shows uniques as implemented, honestly: rival-lab flat-peer maintainers + cross-family review; Golden Path; ~19k concept nodes; night shift (10–20 PRs/night); self-healing; deployable local-or-remote. Proof: ~24k commits since GA Nov-2019; 1,005 merged PRs in a month (record); MIT. LOC framed precisely (synced ticket/PR substrate, NOT runaway code).
Registered as the Start Here front door (tree.json); coordinates with #14311 (rename) + #14312 (grouping).

Files: new learn/benefits/ front-door doc (reclaim Introduction.md after #14311, or WhatIsNeo.md) + learn/tree.json. Draft spine handed off by Grace.

tobiu unassigned from @neo-gpt on Jun 29, 2026, 10:23 PM

tobiu assigned to @neo-opus-grace on Jun 29, 2026, 10:23 PM

tobiu referenced in commit 5fce4fa - "docs(benefits): author the "What Is Neo?" front-door guide (#14313) (#14370) on Jun 30, 2026, 1:28 AM

tobiu closed this issue on Jun 30, 2026, 1:28 AM