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	9422
title	Update TreeStore to manage ARIA sibling fields on mutations
state	Closed
labels	enhancementarchitecturecoregrid
assignees	tobiu
createdAt	Mar 9, 2026, 7:16 PM
updatedAt	Mar 9, 2026, 7:40 PM
githubUrl	https://github.com/neomjs/neo/issues/9422
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 7:40 PM

Update TreeStore to manage ARIA sibling fields on mutations

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

Closed v12.1.0 enhancementarchitecturecoregrid

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

Goal

To ensure O(1) performance in the rendering hot path, the and properties are maintained directly on the records. The must be updated to automatically manage these fields when the tree structure mutates.

Context

This is a follow-up to Epic #9404 and sub-task #9408. We made a deliberate architectural trade-off to prioritize fast reads during 60-120fps scrolling over fast writes during data mutations.

Tasks

Update to intercept , , and operations.
Implement logic to find the parent node of the mutated items.
Iterate over the array for that parent to recalculate and update and (1-based) for all siblings.
Ensure these updates fire appropriate events so the UI can update if those siblings are currently visible.

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

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

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

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

tobiu added the grid label on Mar 9, 2026, 7:16 PM

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

tobiu changed title from Manage ARIA sibling fields on TreeStore mutations to Update TreeStore to manage ARIA sibling fields on mutations on Mar 9, 2026, 7:19 PM

tobiu referenced in commit b3c85f6 - "feat(data): Manage ARIA sibling fields on TreeStore ingest (#9422)" on Mar 9, 2026, 7:39 PM

tobiu Mar 9, 2026, 7:40 PM

Input from Gemini 3.1 Pro:

✦ I have implemented the updateSiblingStats logic during the ingestion phase (add()), ensuring that siblingCount and siblingIndex are properly initialized for all nodes (visible and hidden) as they enter the TreeStore.

However, as discussed during the architectural review, full CRUD support (removing nodes, moving nodes via drag & drop) requires a dedicated effort to override splice() or remove() to ensure #childrenMap and #allRecordsMap remain synchronized. This is outside the scope of simple ARIA ingestion.

I am closing this issue as the ingestion portion is complete, and we will create a dedicated Epic sub-task for "TreeStore Full CRUD Support".

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