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	9451
title	Create Pipeline Cornerstone and Refactor Store Implementation
state	Closed
labels	enhancementaiarchitecturecore
assignees	tobiu
createdAt	Mar 12, 2026, 7:22 PM
updatedAt	Mar 17, 2026, 7:57 PM
githubUrl	https://github.com/neomjs/neo/issues/9451
author	tobiu
commentsCount	0
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 17, 2026, 7:57 PM

Create Pipeline Cornerstone and Refactor Store Implementation

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

Closed v12.1.0 enhancementaiarchitecturecore

tobiu commented on Mar 12, 2026, 7:22 PM

Goal

Establish Neo.data.Pipeline as the central orchestrator for data transformation and remote execution, and remove the brittle remote instantiation logic from Neo.data.Store.

Context

Currently, Neo.data.Store attempts to directly manage the cross-worker instantiation of its Normalizer (via afterSetNormalizer). This is an abstraction leak; a Store should not be hardcoded to Neo.worker.Data or manage remote IDs.

We need a dedicated Neo.data.Pipeline class. The Store will aggregate a Pipeline using ClassSystemUtil.beforeSetInstance(). The Pipeline takes over the responsibility of owning the Connection, Parser, and Normalizer, and importantly, orchestrating whether they run locally in the App Worker or remotely in the Data Worker.

Acceptance Criteria

Create src/data/Pipeline.mjs extending Neo.core.Base.
Give Pipeline the following reactive configs: workerExecution (default 'app'), connection_, parser_, and normalizer_.
Use ClassSystemUtil.beforeSetInstance inside the Pipeline to instantiate these sub-components.
If workerExecution: 'data', the Pipeline should use Neo.worker.Data.createInstance to spawn the actual Connection, Parser, and Normalizer instances exclusively inside the Data Worker (meaning the App Worker Pipeline only holds the configs, not the instances), storing the remote ID.
Refactor Neo.data.Store: Remove afterSetNormalizer and afterSetParser. Introduce a pipeline_ config that uses ClassSystemUtil.beforeSetInstance to create the Pipeline.
The Store's load() method should delegate to this.pipeline.read().

tobiu added the enhancement label on Mar 12, 2026, 7:22 PM

tobiu added the ai label on Mar 12, 2026, 7:22 PM

tobiu added the architecture label on Mar 12, 2026, 7:22 PM

tobiu added the core label on Mar 12, 2026, 7:22 PM

tobiu added parent issue #9449 on Mar 12, 2026, 7:23 PM

tobiu cross-referenced by #9449 on Mar 12, 2026, 7:24 PM

tobiu assigned to @tobiu on Mar 12, 2026, 7:25 PM

tobiu changed title from Create Connection.Base and Establish Connection -> Parser Hierarchy to Create Pipeline Cornerstone and Refactor Store Implementation on Mar 12, 2026, 10:02 PM

tobiu cross-referenced by #9453 on Mar 12, 2026, 10:03 PM

tobiu cross-referenced by #9502 on Mar 17, 2026, 6:46 PM

tobiu referenced in commit 6c3cc3a - "feat(data): Create Pipeline Cornerstone (#9451) on Mar 17, 2026, 7:00 PM

tobiu referenced in commit e6538be - "fix(data): Refine Pipeline IPC and unbreak Store load (#9451) on Mar 17, 2026, 7:00 PM

tobiu referenced in commit 9f20ea5 - "refactor(data): Refine Pipeline IPC and improve self-healing (#9451) on Mar 17, 2026, 7:00 PM

tobiu closed this issue on Mar 17, 2026, 7:57 PM