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	9418
title	Create Data Normalizer Architecture (`Neo.data.normalizer.Base` & `Tree`)
state	Closed
labels	enhancementaiarchitecturecore
assignees	tobiu
createdAt	Mar 9, 2026, 4:45 PM
updatedAt	Mar 12, 2026, 3:45 PM
githubUrl	https://github.com/neomjs/neo/issues/9418
author	tobiu
commentsCount	1
parentIssue	9449
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 12, 2026, 3:45 PM

Create Data Normalizer Architecture (`Neo.data.normalizer.Base` & `Tree`)

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

Closed v12.1.0 enhancementaiarchitecturecore

tobiu commented on Mar 9, 2026, 4:45 PM

Goal

Introduce a Neo.data.normalizer.Base class and a concrete Neo.data.normalizer.Tree implementation to decouple geometric data shaping from Stores and Parsers.

Context

In our modernized data pipeline (Connection -> Parser -> Normalizer -> Store), the Normalizer is responsible for taking native JavaScript objects (yielded by a Parser) and reshaping them for the Store. For the Tree Grid epic, external APIs often return nested hierarchical data, while Neo.data.TreeStore requires a flattened 1D array with parentId relationships.

Acceptance Criteria

Create src/data/normalizer/Base.mjs defining the standard interface for structural normalization and metadata extraction (like totalCount).
Create src/data/normalizer/Tree.mjs. This normalizer must take a nested JS object array (e.g., children properties), recursively flatten it into a 1D array, and inject parentId links before passing the data to the TreeStore.
Update Store configs to accept a normalizer property.

tobiu added the enhancement label on Mar 9, 2026, 4:45 PM

tobiu added the ai label on Mar 9, 2026, 4:45 PM

tobiu added the architecture label on Mar 9, 2026, 4:45 PM

tobiu added the core label on Mar 9, 2026, 4:45 PM

tobiu added parent issue #9404 on Mar 9, 2026, 4:45 PM

tobiu cross-referenced by #9420 on Mar 9, 2026, 4:46 PM

tobiu assigned to @tobiu on Mar 9, 2026, 4:46 PM

tobiu cross-referenced by #9449 on Mar 12, 2026, 3:20 PM

tobiu removed parent issue #9404 on Mar 12, 2026, 3:21 PM

tobiu added parent issue #9449 on Mar 12, 2026, 3:21 PM

tobiu referenced in commit ebeec39 - "feat: Create Data Normalizer Architecture (#9418)" on Mar 12, 2026, 3:43 PM

tobiu Mar 12, 2026, 3:45 PM

Input from Gemini 3.1 Pro:

✦ I have implemented the new Neo.data.normalizer.Base and Neo.data.normalizer.Tree architecture as requested.

Changes Made:

src/data/normalizer/Base.mjs: Created the base class that defines the normalize(data) interface to handle structural reshaping and metadata extraction.

src/data/normalizer/Tree.mjs: Created a specific implementation that traverses hierarchical JSON structures based on a childrenProperty, flattens the tree into a 1D array, and injects parentId and isLeaf data natively. Memory optimization is also applied by removing the raw nested children arrays since the TreeStore uses #childrenMap.

src/data/Store.mjs: Added the normalizer_ reactive config.

test/playwright/unit/data/normalizer/Tree.spec.mjs: Added a test suite that successfully tests single objects, basic flattening, structural injection (isLeaf, parentId), custom configurations (childrenProperty, keyProperty), and the extraction of totalCount.

Tests executed and all 331 unit tests pass flawlessly.

The code has been committed and pushed under #9418.

tobiu closed this issue on Mar 12, 2026, 3:45 PM

Create Data Normalizer Architecture (Neo.data.normalizer.Base & Tree)

Goal

Context

Acceptance Criteria

Changes Made:

Create Data Normalizer Architecture (`Neo.data.normalizer.Base` & `Tree`)