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	9098
title	Feat: Integrate Documentation Viewer into DevRank
state	Closed
labels	documentationaifeature
assignees	tobiu
createdAt	Feb 11, 2026, 10:29 AM
updatedAt	Feb 11, 2026, 10:42 AM
githubUrl	https://github.com/neomjs/neo/issues/9098
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 11, 2026, 10:42 AM

Feat: Integrate Documentation Viewer into DevRank

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

Closed v12.0.0 documentationaifeature

tobiu commented on Feb 11, 2026, 10:29 AM

Integrate the shared Neo.app.content documentation viewer into the DevRank application to display the DevRank documentation (learn/guides/devrank).

Tasks:

Implement Data Layer (Models & Stores) for Content in DevRank.
Implement View Layer (MainContainer, Controller, StateProvider) for the "Learn" section.
Add "Learn" button to DevRank HeaderToolbar.
Implement routing logic in ViewportController to switch between "Home" (Grid) and "Learn" views.
Ensure documentation loads correctly from learn/guides/devrank.
Update apps/devrank/view/Viewport.mjs to include the MainContainer.

tobiu added the documentation label on Feb 11, 2026, 10:29 AM

tobiu added the ai label on Feb 11, 2026, 10:29 AM

tobiu added the feature label on Feb 11, 2026, 10:29 AM

tobiu added parent issue #8930 on Feb 11, 2026, 10:29 AM

tobiu referenced in commit d17828d - "feat: Integrate Documentation Viewer into DevRank (#9098)" on Feb 11, 2026, 10:41 AM

tobiu Feb 11, 2026, 10:41 AM

Input from Gemini 3 Pro:

✦ I have integrated the documentation viewer into DevRank.

Changes Implemented:

Data Layer: Created DevRank.store.Content and DevRank.store.ContentSections (and their models) to handle documentation data.

View Layer:

Created DevRank.view.learn.MainContainer (extending Neo.app.content.Container).

Configured it to load content from learn/guides/devrank/.

Implemented routing and state management for the documentation view.

UI Integration:

Updated DevRank.view.Viewport to include the new MainContainer.

Added a "Learn" button to DevRank.view.HeaderToolbar.

Updated DevRank.view.ViewportController to switch between the "Home" (Grid) and "Learn" views.

The DevRank application now features a fully functional "Learn" section powered by the shared framework content viewer.

tobiu closed this issue on Feb 11, 2026, 10:42 AM

tobiu assigned to @tobiu on Feb 11, 2026, 10:42 AM