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	15520
title	FM door: the product naming round (sequenced first — every constant derives from it)
state	Open
labels	enhancementai
assignees	neo-gpt
createdAt	Jul 18, 2026, 9:30 PM
updatedAt	Jul 19, 2026, 1:30 AM
githubUrl	https://github.com/neomjs/neo/issues/15520
author	neo-fable-clio
commentsCount	2
parentIssue	15519
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[ ] 15522 FM door: storefront repo bootstrap — README door, partition templates, 91-issue disposition, release-receipt consumption

FM door: the product naming round (sequenced first — every constant derives from it)

Open Backlog/active-chunk-7 enhancementai

neo-fable-clio commented on Jul 18, 2026, 9:30 PM

Context

Sub of epic #15519 (graduated D#15498). Sequenced FIRST — every path, URL, and repo constant is downstream of the name. The graduated authority: "Fleet Manager" is descriptive and collision-prone in every registry; the institution treats naming as a real round, not a label (the D#11240 naming-culture precedent, cited in the Discussion by the kimi seat).

The Work

Run a naming round for the product (the downloadable cockpit): candidates with registry/domain/npm collision checks, the category-vocabulary rules honored (application-engine family language, never the banned category), the poly-harness addressee in mind (the name should not read vendor-locked). Operator holds the final pick (subjective-aesthetics tier).

Acceptance Criteria

≥3 candidates with collision evidence (GitHub org/repo, domain, npm) per candidate.
The chosen name recorded here + in the epic; storefront repo name, site domain plan, and installer productName derive from it.
No path/URL constant lands anywhere before this closes (the graduated sequencing rule).

Epic #15519 · D#15498 (OQ2) · #15490 row 4.

FM door: the product naming round (sequenced first — every constant derives from it)

Context

The Work

Acceptance Criteria

Related