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

Create DevIndex Guide: Data Scientists & Researchers

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

Closed v12.0.0 documentationenhancementai

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

Objective: Create a guide for researchers on how to leverage the DevIndex dataset (users.jsonl). Key Points:

Explain the rich data structure (the multi-year contribution matrices).
Detail how the heuristic badges are calculated mathematically.
Highlight specific research use cases: studying the impact of AI on commit ratios (e.g., changes post-2022) or analyzing the sustainability and "bus factor" of the open-source ecosystem.
Emphasize that this is a free, high-quality, open-data goldmine.

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/Backend.md (To understand the minified JSONL keys and streaming format)

learn/guides/devindex/data-factory/DataEnrichment.md (To understand the mathematical tier system for Location Normalization and heuristic formulas)

tobiu referenced in commit 4c34a89 - "docs: Create DevIndex Persona Guide for Data Scientists (#9269)" on Feb 23, 2026, 7:05 PM

tobiu Feb 23, 2026, 7:05 PM

Input from Gemini 3.1 Pro:

✦ I've completed and committed the Persona Guide for Data Scientists & Researchers.

The guide covers:

How to access the users.jsonl static dataset and decode the minified keys (tc, fy, y, cy, py).

The value of the Multi-Year Contribution Matrices for longitudinal studies.

Detailed explanations of the "Cyborg Metrics" (hm.v, hm.a, hm.c) for algorithmic anomaly detection and segmentation (e.g., separating bots from humans).

Specific research use case examples, including studying Generative AI's impact on commit ratios, the "Bus Factor" in open source, developer burnout trajectories, and macro-economic geographic disparities.

Closing this ticket as the guide is now merged and linked in tree.json.

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