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	6851
title	Learning Content: declarative component trees VS imperative vdom trees
state	Closed
labels	enhancement
assignees	[]
createdAt	Jun 21, 2025, 7:33 PM
updatedAt	Oct 23, 2025, 12:55 AM
githubUrl	https://github.com/neomjs/neo/issues/6851
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 21, 2025, 9:36 PM

Learning Content: declarative component trees VS imperative vdom trees

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

Closed v10.0.0-alpha.4 enhancement

tobiu commented on Jun 21, 2025, 7:33 PM

(No description provided)

tobiu added the enhancement label on Jun 21, 2025, 7:33 PM

tobiu referenced in commit 20f524a - "Learning Content: declarative component trees VS imperative vdom trees #6851" on Jun 21, 2025, 7:34 PM

tobiu referenced in commit eabc288 - "#6851 mental model shift" on Jun 21, 2025, 7:39 PM

tobiu referenced in commit 625c566 - "#6851 mental model shift extended" on Jun 21, 2025, 7:49 PM

tobiu referenced in commit a3fb8c5 - "#6851 mental model shift extended" on Jun 21, 2025, 7:50 PM

tobiu referenced in commit 77e67b6 - "#6851 refined structure" on Jun 21, 2025, 8:21 PM

tobiu referenced in commit 2be9f73 - "#6851 polishing" on Jun 21, 2025, 8:22 PM

tobiu referenced in commit e513598 - "#6851 polishing" on Jun 21, 2025, 8:25 PM

tobiu referenced in commit 2891ed1 - "#6851 polishing" on Jun 21, 2025, 8:26 PM

tobiu referenced in commit faf5392 - "#6851 polishing" on Jun 21, 2025, 8:29 PM

tobiu referenced in commit aa2871e - "#6851 polishing" on Jun 21, 2025, 8:41 PM

tobiu referenced in commit 247e647 - "#6851 polishing" on Jun 21, 2025, 8:43 PM

tobiu referenced in commit 39c4bf4 - "#6851 re-added onHomeRoute()" on Jun 21, 2025, 8:50 PM

tobiu referenced in commit e59f09c - "#6851 typo fix" on Jun 21, 2025, 8:54 PM

tobiu referenced in commit d36b362 - "#6851 comments" on Jun 21, 2025, 8:56 PM

tobiu referenced in commit 3a960ad - "#6851 comment" on Jun 21, 2025, 9:01 PM

tobiu referenced in commit 35c1758 - "#6851 comment" on Jun 21, 2025, 9:06 PM

tobiu referenced in commit 70b853a - "#6851 App => Viewport" on Jun 21, 2025, 9:11 PM

tobiu referenced in commit 61f7faa - "#6851 md table update" on Jun 21, 2025, 9:21 PM

tobiu referenced in commit 187369e - "#6851 Framework-Specific Migration Notes update" on Jun 21, 2025, 9:34 PM

tobiu closed this issue on Jun 21, 2025, 9:36 PM