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	9241
title	Add DevIndex Spider Engine Guide
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Feb 22, 2026, 12:18 PM
updatedAt	Feb 22, 2026, 12:22 PM
githubUrl	https://github.com/neomjs/neo/issues/9241
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 22, 2026, 12:22 PM

Add DevIndex Spider Engine Guide

Closed v12.0.0/archive-v12-0-0-chunk-4 documentationenhancementai

tobiu commented on Feb 22, 2026, 12:18 PM

Create a new guide at learn/guides/devindex/spider/Engine.md.
Document the Spider.mjs service, detailing its "bottom-up" discovery strategies (Network Walker, High Stars, Keyword, Temporal, Community/Stargazer) and the rationale behind finding "Hidden Whales".
Include a section on Strategy Evolution to explain how weights changed as the index grew.
Include a Mermaid sequence diagram illustrating the architectural flow.
Document resilience mechanisms: Backpressure Valve, Rate Limit Monitoring, and Checkpointing.
Update learn/guides/devindex/tree.json to include the new Spider Engine guide.

tobiu Feb 22, 2026, 12:21 PM

Input from Gemini 3 Pro:

✦ I have created the Engine.md guide. It includes the strategy evolution details, the Mermaid diagram for the architectural flow, and the resilience mechanics as discussed. The file has been committed and pushed to the repository. Closing the issue now.