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	9408
title	Grid Core Integration & TreeGrid Accessibility
state	Closed
labels	enhancementaicoregrid
assignees	tobiu
createdAt	Mar 9, 2026, 11:59 AM
updatedAt	Mar 9, 2026, 7:17 PM
githubUrl	https://github.com/neomjs/neo/issues/9408
author	tobiu
commentsCount	2
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 7:17 PM

Grid Core Integration & TreeGrid Accessibility

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

Closed v12.1.0 enhancementaicoregrid

tobiu commented on Mar 9, 2026, 11:59 AM

Goal

Ensure GridContainer, GridBody, and Row correctly handle the dynamic flat-array sizing provided by the TreeStore and implement full WAI-ARIA treegrid attributes for maximum accessibility.

Details

Virtual Scroller Reaction:
- Verify that GridBody correctly responds to the TreeStore's mutate events when nodes expand/collapse (the count changes).
- Ensure aria-rowcount on the GridBody updates dynamically based on the current length of the flattened view.
- Ensure the VerticalScrollbar recalculates its height based on the new store.count.
A11y (Row Level ARIA):
- Update src/grid/Row.mjs -> createVdom().
- Map record.expanded to aria-expanded (true/false). Omit entirely for leaf nodes.
- Map record.depth to aria-level (1-based).
- Map record.siblingCount to aria-setsize.
- Map record.siblingIndex to aria-posinset (1-based).
- Note: The virtual scroller will naturally provide gapless aria-rowindex values based on the flattened visible array.
Data Layer Support for A11y Attributes:
- The TreeStore (or TreeModel) must provide depth, siblingCount, and siblingIndex for all records.
- Use Neo's "Soft Hydration" pattern to calculate these lazily when needed, or compute them once during loadData and store them directly on the raw data objects / records for O(1) retrieval during rapid scrolling.
Role Update:
- Add a config isTreeGrid: false to GridContainer.
- When true, switch the container's ARIA role from grid to treegrid.

tobiu added the enhancement label on Mar 9, 2026, 11:59 AM

tobiu added the ai label on Mar 9, 2026, 11:59 AM

tobiu added the core label on Mar 9, 2026, 11:59 AM

tobiu added the grid label on Mar 9, 2026, 11:59 AM

tobiu added parent issue #9404 on Mar 9, 2026, 11:59 AM

tobiu Mar 9, 2026, 12:09 PM

Input from Gemini 3.1 Pro:

✦ Implementation Guidance for Agents:

ARIA Mapping: The new WAI-ARIA attributes (aria-expanded, aria-level, aria-setsize, aria-posinset) MUST be applied directly to the row container.

Target File: Implement this mapping inside src/grid/Row.mjs within the createVdom() method.

Contiguous Indexing: Do not attempt to calculate complex aria-rowindex logic. Because the TreeStore provides a flattened array of visible nodes, rowIndex + 2 inside Row.mjs will naturally remain contiguous and gapless.

Role: Add an isTreeGrid boolean config to src/grid/Container.mjs. If true, the container's VDOM root should use role: 'treegrid' instead of role: 'grid'.

tobiu assigned to @tobiu on Mar 9, 2026, 12:10 PM

tobiu referenced in commit 4f93b95 - "feat(grid): Core Integration & TreeGrid Accessibility (#9408)" on Mar 9, 2026, 7:16 PM

tobiu cross-referenced by #9422 on Mar 9, 2026, 7:16 PM

tobiu Mar 9, 2026, 7:17 PM

Input from Gemini 3.1 Pro:

✦ I have completed the ARIA accessibility mappings for TreeGrids!

Added siblingCount and siblingIndex to TreeModel.mjs alongside an architectural note explaining the trade-off.

Added isTreeGrid to grid.Container which toggles the role="treegrid".

Mapped aria-expanded, aria-level, aria-posinset, and aria-setsize into the VDOM of grid.Row.

I have also created a follow-up ticket to address the TreeStore mutation logic as discussed.

Closing this ticket as complete.

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