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	9414
title	Refactor `Neo.data.Store` to unify Record Hydration
state	Closed
labels	enhancementairefactoringcore
assignees	tobiu
createdAt	Mar 9, 2026, 3:13 PM
updatedAt	Mar 9, 2026, 3:18 PM
githubUrl	https://github.com/neomjs/neo/issues/9414
author	tobiu
commentsCount	1
parentIssue	9404
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Mar 9, 2026, 3:18 PM

Refactor `Neo.data.Store` to unify Record Hydration

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

Closed v12.1.0 enhancementairefactoringcore

tobiu commented on Mar 9, 2026, 3:13 PM

Goal

Extract the duplicate lazy-instantiation ("hydration") logic currently found in Store.get() and Store.getAt() into a single, overridable protected method: hydrateRecord(item, index).

Context

In "Turbo Mode" (autoInitRecords: false), records are stored as raw JSON objects and are only instantiated into Neo.data.Record instances when accessed via get() or getAt(). Currently, both methods duplicate the logic for converting the object, updating me.map, me._items, me.internalIdMap, and the allItems collection.

By centralizing this logic into hydrateRecord(item, index), we establish a "Single Source of Truth" for the instantiation event. This is strictly required for subclasses like TreeStore that need to maintain their own secondary maps (#childrenMap) and must be notified exactly when a raw object's identity changes into a Record instance.

Acceptance Criteria

Create hydrateRecord(item, index) in src/data/Store.mjs.
Refactor get() and getAt() to simply call return this.hydrateRecord(super.get(key)) (or similar).
Ensure existing Store tests continue to pass.

tobiu added the enhancement label on Mar 9, 2026, 3:13 PM

tobiu added the ai label on Mar 9, 2026, 3:13 PM

tobiu added the refactoring label on Mar 9, 2026, 3:13 PM

tobiu added the core label on Mar 9, 2026, 3:13 PM

tobiu added parent issue #9404 on Mar 9, 2026, 3:13 PM

tobiu cross-referenced by #9415 on Mar 9, 2026, 3:13 PM

tobiu referenced in commit 3a143d5 - "refactor: Centralize Record hydration in Store (#9414) on Mar 9, 2026, 3:17 PM

tobiu Mar 9, 2026, 3:17 PM

Input from Gemini 3.1 Pro:

✦ Refactored Store.mjs to centralize lazy instantiation into hydrateRecord(item, index). get() and getAt() now delegate to this method.

Pushed to dev.

tobiu assigned to @tobiu on Mar 9, 2026, 3:17 PM

tobiu closed this issue on Mar 9, 2026, 3:18 PM

Refactor Neo.data.Store to unify Record Hydration

Goal

Context

Acceptance Criteria

Refactor `Neo.data.Store` to unify Record Hydration