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	9234
title	DevIndex: Split Methodology guide into Introduction and Methodology
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Feb 21, 2026, 9:51 PM
updatedAt	Feb 21, 2026, 9:58 PM
githubUrl	https://github.com/neomjs/neo/issues/9234
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 21, 2026, 9:58 PM

DevIndex: Split Methodology guide into Introduction and Methodology

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

Closed v12.0.0 documentationai

tobiu commented on Feb 21, 2026, 9:51 PM

Description

The current Methodology.md guide for DevIndex has evolved into a comprehensive manifesto covering project motivation, the AI era, funding disparities, and legal disclaimers, in addition to actual scoring and heuristic methodologies. This creates a structural imbalance where the "Why" and the "How" are conflated.

Requirements

Create a new Introduction.md guide.
Move the following sections from Methodology.md to Introduction.md:
- Legal Disclaimer
- Project Motivation & The "Invisibility" Problem (including AI Era & Open Source Sustainability)
- Technical Feasibility & The GitHub API Challenge (including the 50k cap and 20MB payload rationale)
- Data Science Use Cases
- Rich Data & Inclusivity
Refine Methodology.md to strictly focus on the "How":
- Keep "Scoring" (Commits, PRs, Issues, Code Reviews)
- Keep "Anomaly Detection & Pattern Recognition" (Velocity, Acceleration, Consistency heuristics and Impact Badges)
- Add details about the Meritocracy Filter algorithm (how threshold.json dynamically rises).
Update learn/guides/devindex/tree.json to include Introduction as the first item.

tobiu added the documentation label on Feb 21, 2026, 9:51 PM

tobiu added the ai label on Feb 21, 2026, 9:51 PM

tobiu referenced in commit a1ba5e3 - "docs(devindex): Complete Methodology split and OptOut links (#9234)" on Feb 21, 2026, 9:57 PM

tobiu assigned to @tobiu on Feb 21, 2026, 9:57 PM

tobiu Feb 21, 2026, 9:57 PM

Input from Gemini 3 Pro:

✦ I have completed the separation of the Methodology.md guide into Introduction.md and Methodology.md.

No content was lost. The "Why" is now correctly structured in the Introduction.md file, serving as an overview and manifesto. The "How" (Scoring, Meritocracy Filter logic, Heuristics, etc.) remains in Methodology.md.

I also made sure the Privacy & Opt-Out guide link is moved to the end of the Introduction.md where it is most contextually relevant. The files have been committed to dev and the tree.json structure was updated. Closing this issue.

tobiu closed this issue on Feb 21, 2026, 9:58 PM