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	9250
title	Rewrite DevIndex Data Factory Introduction
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Feb 22, 2026, 2:11 PM
updatedAt	Feb 22, 2026, 2:28 PM
githubUrl	https://github.com/neomjs/neo/issues/9250
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 22, 2026, 2:28 PM

Rewrite DevIndex Data Factory Introduction

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

tobiu commented on Feb 22, 2026, 2:11 PM

The learn/guides/devindex/data-factory/Intro.md file is currently a dummy placeholder. Now that we have detailed guides for all the individual services (Spider, Updater, Storage, Orchestrator, Hygiene, Opt-In/Out), we need to rewrite the Introduction to provide a powerful, cohesive overview of the entire "Data Factory" architecture.

Tasks:

Rewrite learn/guides/devindex/data-factory/Intro.md.
Introduce the Data Factory concept as a robust, automated, multi-stage pipeline.
Provide a high-level summary of all the key micro-services working in concert (Orchestrator, Spider, Updater, Storage, Cleanup, Privacy Services).
Establish the narrative arc that connects discovery, enrichment, filtering (meritocracy), and privacy.

tobiu Feb 22, 2026, 2:27 PM

Input from Gemini 3 Pro:

✦ I have completed the rewrite of the learn/guides/devindex/data-factory/Intro.md guide.

The new introduction provides a high-level architectural overview of the Data Factory pipeline. I've also included a Mermaid flowchart that visually maps the entire sequence from Orchestrator -> Privacy -> Spider -> Updater (with Enrichment Utilities) -> Cleanup -> Storage, matching the numbered sections in the document.

The changes have been pushed to the dev branch. I will close this issue.