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	9194
title	Zero Overhead Record Architecture & Grid Dynamic Column Fixes
state	Closed
labels	epicaiarchitectureperformancecore
assignees	tobiu
createdAt	Feb 17, 2026, 2:35 PM
updatedAt	Feb 23, 2026, 5:10 PM
githubUrl	https://github.com/neomjs/neo/issues/9194
author	tobiu
commentsCount	0
parentIssue	null
subIssues	9193 Implement Virtual Fields for Zero-Overhead Records 9195 Fix GridBody Column Position Sync on DataField Change 9197 Add Regression Test for Dynamic Grid Columns 9198 Cleanup Redundant GridContainer Logic 9199 Benchmark Grid Horizontal Scroll Performance 9201 Docs: Dynamic Grids Guide 9202 Investigate CSS Optimizations for Grid Rendering (Desktop Scaling) 9203 Investigate Grid Scrolling Performance via Column Ablation Strategy 9204 Profile Main Thread Activity for Desktop Grid Scrolling 9205 Debug SyncAligns Layout Thrashing during Grid Scroll 9206 Commit Playwright Profiling Infrastructure & DomEvents Optimization 9207 Verify Playwright Overhead with Native Scroll Benchmark
subIssuesCompleted	12
subIssuesTotal	12
blockedBy	[]
blocking	[]
closedAt	Feb 23, 2026, 5:10 PM

Zero Overhead Record Architecture & Grid Dynamic Column Fixes

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

Closed v12.0.0 epicaiarchitectureperformancecore

tobiu commented on Feb 17, 2026, 2:35 PM

This Epic encapsulates the architectural shift to "Zero Overhead" records using virtual fields and the necessary fixes to the Grid component to support dynamic column remapping at runtime.

Strategic Goal

To achieve a flat memory profile for Neo.data.Record instances even with hundreds of calculated fields (e.g., yearly stats), while ensuring the Neo.grid.Container can robustly handle dynamic dataField changes without breaking virtual scrolling.

Scope

Core Architecture: Implement virtual: true in RecordFactory to generate prototype-based getters instead of instance properties.
Model Refactoring: Update DevIndex.model.Contributor to utilize virtual fields for O(1) access to raw data arrays.
Grid Stability: Fix regressions in Neo.grid.Body where dynamic changes to column dataFields cause desynchronization in columnPositions and row recycling maps, leading to rendering artifacts during horizontal scroll.
Verification: Implement reproduction test cases to validate the fix and ensure no future regressions.

Roadmap

#9193 Implement Virtual Fields in RecordFactory & Update Model
Fix GridBody Column Position Sync on DataField Change (To be created)
Create Reproduction Test Case for Dynamic Grid Columns (To be created)

tobiu added the epic label on Feb 17, 2026, 2:35 PM

tobiu added the ai label on Feb 17, 2026, 2:35 PM

tobiu added the architecture label on Feb 17, 2026, 2:35 PM

tobiu added the performance label on Feb 17, 2026, 2:35 PM

tobiu added the core label on Feb 17, 2026, 2:35 PM

tobiu added sub-issue #9193 on Feb 17, 2026, 2:35 PM

tobiu added sub-issue #9195 on Feb 17, 2026, 2:36 PM

tobiu assigned to @tobiu on Feb 17, 2026, 2:38 PM

tobiu cross-referenced by #9193 on Feb 17, 2026, 2:40 PM

tobiu added sub-issue #9197 on Feb 17, 2026, 3:18 PM

tobiu added sub-issue #9198 on Feb 17, 2026, 3:20 PM

tobiu added sub-issue #9199 on Feb 17, 2026, 3:33 PM

tobiu added sub-issue #9201 on Feb 17, 2026, 4:13 PM

tobiu added sub-issue #9202 on Feb 18, 2026, 12:53 PM

tobiu added sub-issue #9203 on Feb 18, 2026, 1:08 PM

tobiu added sub-issue #9204 on Feb 18, 2026, 2:12 PM

tobiu added sub-issue #9205 on Feb 18, 2026, 3:23 PM

tobiu cross-referenced by #9206 on Feb 18, 2026, 4:07 PM

tobiu added sub-issue #9206 on Feb 18, 2026, 4:07 PM

tobiu added sub-issue #9207 on Feb 19, 2026, 11:17 AM

tobiu referenced in commit 6ca0d13 - "feat: Add GPU-accelerated E2E benchmark infrastructure (#9194) on Feb 19, 2026, 12:57 PM

tobiu closed this issue on Feb 23, 2026, 5:10 PM