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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	docs(learn): add workspace-vs-repository guide (#6777)
author	neo-gpt
state	Closed
createdAt	Jun 25, 2026, 9:35 AM
updatedAt	Jul 27, 2026, 12:07 AM
closedAt	Jun 25, 2026, 11:29 AM
mergedAt
branches	`dev` ← `codex/6777-workspace-vs-repo-docs`
url	https://github.com/neomjs/neo/pull/13993
contentTrust
projected
quarantined	0
signals	[]

Closed

neo-gpt commented on Jun 25, 2026, 9:35 AM

Resolves #6777

Adds a Getting Started learning guide that explains when to build in a generated npx neo-app workspace versus a neomjs/neo repository fork, documents that the build programs keep the same command surface in both layouts, and gives migration checklists for moving an app in both directions.

Evidence: L1 (static docs/tree lint) -> L1 required (docs-only close target). Residual: none.

Deltas from ticket

The implementation places the deeper guide under learn/gettingstarted/WorkspaceVsRepository.md, registers it in learn/tree.json, links it from .github/GETTING_STARTED.md and learn/gettingstarted/Setup.md, and regenerates the checked-in Portal SEO outputs that mirror learn routes.

Test Evidence

git diff --cached --check
npm run ai:lint-tree-json
rg -n "WorkspaceVsRepository|Workspace or Repository Fork" learn apps/portal/llms.txt apps/portal/sitemap.xml .github/GETTING_STARTED.md

Post-Merge Validation

Open /learn/gettingstarted/WorkspaceVsRepository in the Portal app and verify it renders under Getting Started.

Commit

a8b0101af6 - docs(learn): add workspace-vs-repository guide (#6777)

Authored by Euclid (GPT-5, Codex Desktop). Session 019efd84-2ba3-7441-9ce6-04896f1c5cb9.

tobiu commented on Jun 25, 2026, 11:29 AM

why are you picking up tickets that are several years old? without mapping them to the current reality? rejected.