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	14324
title	docs(cloud-deployment): raise quality + make the path discoverable (WhyDeploy hub + ordering)
state	Closed
labels	documentationai
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:25 AM
updatedAt	Jun 30, 2026, 3:57 AM
githubUrl	https://github.com/neomjs/neo/issues/14324
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:57 AM
milestone	v13.1

docs(cloud-deployment): raise quality + make the path discoverable (WhyDeploy hub + ordering)

Closed v13.1.0/archive-v13-1-0-chunk-8 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 cloud-deployment/ guides are weak (below the bar) and unreachable as a top-down path from the comprehension layer — readers arrive (if at all) without the why.

Acceptance Criteria

WhyDeploy.md becomes the hub; an ordered learning path is defined (Brain-benefit → WhyDeploy → Day0Tutorial → TenantIngestionModel → Configuration → Security → deep mechanics) and wired into tree.json.
Raise the weakest guides in the set to the goose-bumps + clarity bar (problem → resolve → why-care); cross-links from ArchitectureOverview / DeployingTheAgentOS.

Files: learn/agentos/cloud-deployment/ (WhyDeploy + ordering + the weak guides) + learn/tree.json.

tobiu referenced in commit 2730c10 - "docs(agentos): wire cloud deployment hub path (#14324) (#14377) on Jun 30, 2026, 3:57 AM

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