What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9248
title	Add DevIndex Data Factory Guide: Updater Service
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Feb 22, 2026, 1:49 PM
updatedAt	Feb 22, 2026, 2:03 PM
githubUrl	https://github.com/neomjs/neo/issues/9248
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 22, 2026, 2:02 PM

Add DevIndex Data Factory Guide: Updater Service

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v12.0.0 documentationenhancementai

tobiu commented on Feb 22, 2026, 1:49 PM

The Updater.mjs service is the most complex component of the DevIndex pipeline. We need comprehensive documentation to explain its workflow, error handling, and data enrichment strategies.

Tasks:

Create learn/guides/devindex/data-factory/Updater.md covering Updater.mjs.
Explain the core workflow: Fetch -> Enrich -> Filter (Meritocracy Logic) -> Persist.
Document the "Safe Purge Protocol" (Self-Healing) for handling transient vs. fatal errors.
Explain the complex GraphQL batching strategy for multi-year contribution histories and the fallback mechanisms for 502/504 errors.
Include Mermaid diagrams to illustrate the batch processing flow and error handling logic.
Provide code snippets to clarify critical sections (e.g., rate limit checks, rename recovery).
Update learn/guides/devindex/tree.json to include the new guide.

tobiu added the documentation label on Feb 22, 2026, 1:49 PM

tobiu added the epic label on Feb 22, 2026, 1:49 PM

tobiu added the ai label on Feb 22, 2026, 1:49 PM

tobiu assigned to @tobiu on Feb 22, 2026, 1:49 PM

tobiu referenced in commit 1817d5e - "docs: Add Data Factory guide for Updater Service (#9248)" on Feb 22, 2026, 1:58 PM

tobiu Feb 22, 2026, 1:59 PM

Input from Gemini 3 Pro:

✦ I have completed the tasks outlined in this issue:

Created learn/guides/devindex/data-factory/Updater.md covering the Updater.mjs service.

Documented the Fetch, Enrich, Filter, and Persist core workflows, including the complex GraphQL chunking mechanism.

Explained the "Safe Purge Protocol" for handling renaming, bad seeds, and transient errors, complete with a flow diagram.

Included the "Checkpointing & State Persistence" section to explain how data integrity is maintained using saveInterval.

Illustrated the flows using structured mermaid diagrams.

Updated learn/guides/devindex/tree.json to include the new Updater guide.

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

tobiu referenced in commit 0cf446d - "docs: Add profile query snippet to Updater guide for transparency (#9248)" on Feb 22, 2026, 2:01 PM

tobiu closed this issue on Feb 22, 2026, 2:02 PM

tobiu removed the epic label on Feb 22, 2026, 2:03 PM

tobiu added the enhancement label on Feb 22, 2026, 2:03 PM