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	9270
title	Create DevIndex Guide: Policy Makers & Gov Funding
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Feb 23, 2026, 6:13 PM
updatedAt	Feb 23, 2026, 7:22 PM
githubUrl	https://github.com/neomjs/neo/issues/9270
author	tobiu
commentsCount	2
parentIssue	9267
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 23, 2026, 7:22 PM

Create DevIndex Guide: Policy Makers & Gov Funding

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

Closed v12.0.0 documentationenhancementai

tobiu commented on Feb 23, 2026, 6:13 PM

Objective: Expand on the "Macro-Economic Analysis" to target policymakers looking to fund digital infrastructure. Key Points:

Provide a guide on how to filter by country to visualize the disparity between open-source consumption and production.
Provide hard, empirical data comparing outputs across regions (US, UK, Germany, India, China).
Use this data to justify the need for national and institutional FOSS infrastructure funding, demonstrating the massive unpaid labor currently driving the global software economy.

tobiu added the documentation label on Feb 23, 2026, 6:13 PM

tobiu added the enhancement label on Feb 23, 2026, 6:13 PM

tobiu added the ai label on Feb 23, 2026, 6:13 PM

tobiu added parent issue #9267 on Feb 23, 2026, 6:14 PM

tobiu assigned to @tobiu on Feb 23, 2026, 6:14 PM

tobiu Feb 23, 2026, 6:19 PM

Input from Gemini 3.1 Pro:

✦ Note for future agent session: Before starting work on this guide, you MUST read the following existing documentation as critical context:

learn/guides/devindex/Introduction.md (Provides the initial macro-economic breakdown of Germany vs. India vs. China that this guide will expand upon)

tobiu referenced in commit 8c13736 - "docs: Fix Mermaid pie chart title cutoff in PolicyMakers guide (#9270)" on Feb 23, 2026, 7:17 PM

tobiu Feb 23, 2026, 7:21 PM

Input from Gemini 3.1 Pro:

✦ I've completed and committed the Persona Guide for Policy Makers & Gov Funding.

Key actions taken:

Authored the guide highlighting the severe disparity between open-source consumption and production, providing concrete metrics for Germany, UK, US, India, and China.

Calculated the exact latest metrics from users.jsonl (as of Feb 23, 2026) to ensure the numbers are up-to-date and accurate in the guide.

Added a Mermaid pie chart to provide a compelling visualization of the regional share of Top 50k Contributors.

Fixed a Mermaid rendering issue where long titles were cut off by shortening the title to "Top 50k Contributors by Region" and adding overflow: visible to the SVG container inside resources/scss/src/component/wrapper/Mermaid.scss.

The guide is now linked in tree.json and pushed to the repository. Closing this issue.

tobiu closed this issue on Feb 23, 2026, 7:22 PM