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	9423
title	TreeStore Full CRUD Support & Structural Mutations
state	Closed
labels	enhancementarchitecturecore
assignees	tobiu
createdAt	Mar 9, 2026, 7:41 PM
updatedAt	Mar 9, 2026, 7:54 PM
githubUrl	https://github.com/neomjs/neo/issues/9423
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 7:54 PM

TreeStore Full CRUD Support & Structural Mutations

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

Closed v12.1.0 enhancementarchitecturecore

tobiu commented on Mar 9, 2026, 7:41 PM

Goal

To provide full CRUD operations (remove, splice, move) for the Neo.data.TreeStore, ensuring that the internal data maps (#childrenMap, #allRecordsMap) and the ARIA sibling stats remain perfectly synchronized with the visible flat array.

Context

Currently, the TreeStore supports data ingestion (add) and visibility toggling (expand/collapse). However, invoking standard Collection mutation methods like remove or splice will only affect the visible items array, causing memory leaks and structural corruption in the internal Tree maps.

This is a critical prerequisite for advanced TreeGrid features like Drag & Drop reordering and moving child nodes between parents.

Requirements

Override splice: Implement a custom splice method in TreeStore that acts as the single source of truth for all mutations.
Removal Logic: When a node is removed:
- Recursively identify and remove all its descendants from #allRecordsMap.
- Remove the node from its parent's array in #childrenMap.
- If the node (or any descendants) was currently visible (expanded), calculate the flat delta and pass it to super.splice().
Move Logic (Drag & Drop Prep): Handle cases where an existing node is "added" again but with a different parentId.
- Remove from the old parent's #childrenMap.
- Add to the new parent's #childrenMap.
Recalculate ARIA Stats: After any structural change to a parent's children array, invoke updateSiblingStats(parentId) on all affected parents to ensure siblingCount and siblingIndex remain accurate for O(1) rendering reads.

tobiu assigned to @tobiu on Mar 9, 2026, 7:41 PM

tobiu added the enhancement label on Mar 9, 2026, 7:41 PM

tobiu added the architecture label on Mar 9, 2026, 7:41 PM

tobiu added the core label on Mar 9, 2026, 7:41 PM

tobiu added parent issue #9404 on Mar 9, 2026, 7:41 PM

tobiu referenced in commit c5c4e40 - "feat(data): Implement TreeStore.splice for full CRUD support (#9423)" on Mar 9, 2026, 7:53 PM

tobiu Mar 9, 2026, 7:53 PM

Input from Gemini 3.1 Pro:

✦ I have implemented the custom TreeStore.splice() method to act as the single source of truth for all structural mutations.

Key achievements:

Removals: Recursively cleans up deep descendants from #allRecordsMap and #childrenMap, preventing memory leaks and calculating the correct flat delta for the visible array.

Additions/Moves: Properly ingests new nodes or reparents moved nodes into the structural maps.

ARIA Stats: Recalculates siblingCount and siblingIndex for all parents affected by the mutation.

Fallback Mutations: Fires a manual mutate event even if the target nodes are hidden, ensuring secondary systems like Store.count remain in sync.

The add() override was removed entirely, as Collection.add() inherently funnels through this new, robust splice() method.

Closing as complete.

tobiu closed this issue on Mar 9, 2026, 7:54 PM