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	14339
title	docs(agentos): refresh StrategicWorkflows.md — fix dead commands (ai:query/ai:query-memory) + bar + freshness
state	Closed
labels	documentationai
assignees	neo-gpt
createdAt	Jun 29, 2026, 1:23 PM
updatedAt	Jun 29, 2026, 7:34 PM
githubUrl	https://github.com/neomjs/neo/issues/14339
author	neo-opus-grace
commentsCount	0
parentIssue	14310
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 29, 2026, 7:34 PM
milestone	v13.1

docs(agentos): refresh StrategicWorkflows.md — fix dead commands (ai:query/ai:query-memory) + bar + freshness

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

neo-opus-grace commented on Jun 29, 2026, 1:23 PM

Part of #14310 · content rubric (narrative arc + dual-audience) + §Mandatory V-B-A grounding in #14310. Refs #14310.

Problem: learn/agentos/StrategicWorkflows.md references dead commands — npm run ai:query (×3) and ai:query-memory (×2), neither in package.json. (ai:query existed but was removed in #7631 "remove obsolete buildScripts/ai"; ai:query-memory is absent.) Operator-surfaced as a hallucinated-content V-B-A failure. The guide also predates the current bar (narrative arc + dual-audience + the moat framing).

Acceptance Criteria

Replace every dead command with the real mechanism — the MCP tools (query_raw_memories / query_hybrid_graph / get_local_issue_by_id / add_memory) or the correct npm script; verify every command/path reference against package.json + the filesystem.
Apply the content rubric: problem → why it matters → how → what's in it for YOU (explicit dual-audience: human AND LLM); narrative arc, not a feature list; never call Neo a "framework."
Freshness: align any stale model/Chroma/topology claims with current reality.

⚠️ V-B-A grounding (mandatory): package.json (the real ai:* scripts), the MCP tool surfaces (the real query/memory mechanism), git #7631 (the ai:query removal), the current source for any workflow described. Write from VERIFIED reality; capture evidence in the PR.

Files: learn/agentos/StrategicWorkflows.md.