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	9676
title	Implement Native Edge Graph Database Engine
state	Closed
labels	enhancementaiarchitecture
assignees	tobiu
createdAt	Apr 4, 2026, 2:37 AM
updatedAt	Apr 4, 2026, 2:54 AM
githubUrl	https://github.com/neomjs/neo/issues/9676
author	tobiu
commentsCount	2
parentIssue	9673
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 2:54 AM

Implement Native Edge Graph Database Engine

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

Closedenhancementaiarchitecture

tobiu commented on Apr 4, 2026, 2:37 AM

Problem

The AI needs a way to store and traverse relational topologies (edges) alongside ChromaDB's semantic vector search to gain true architectural awareness of the Neo.mjs framework.

Proposed Solution

Implement the first iteration of the Neo.ai.graph.Database engine inside the ai/graph package, utilizing Neo.data.Store and lightweight NodeModel/EdgeModel definitions to optimize for zero-dependency execution and disk delta-serialization.

Tasks

Create ai/graph directory and classes (Database.mjs, NodeModel.mjs, EdgeModel.mjs).
Implement basic graph CRUD and topological traversal (getAdjacentNodes).
Create Playwright Unit Tests (test/playwright/unit/ai/graph/Database.spec.mjs).

tobiu added the enhancement label on Apr 4, 2026, 2:37 AM

tobiu added the ai label on Apr 4, 2026, 2:37 AM

tobiu added the architecture label on Apr 4, 2026, 2:37 AM

tobiu added parent issue #9673 on Apr 4, 2026, 2:37 AM

tobiu Apr 4, 2026, 2:45 AM

Input from Antigravity (Gemini 3.1 Pro):

✦ Phase 1 execution complete.

Neo.ai.graph.Database implementation pushed to branch dev.

Leveraged Neo.data.Store in autoInitRecords: false mode with ECMA2021 ??= syntax and standard for loops to minimize GC pressure during hot topological traversals.

Passed 100% simulated unit test criteria.

tobiu referenced in commit 7b62fb1 - "feat: Implement Graph Database Engine (#9676)" on Apr 4, 2026, 2:45 AM

tobiu referenced in commit 131ae48 - "refactor: Add reactive configs and Anchor docs to Graph DB (#9676)" on Apr 4, 2026, 2:51 AM

tobiu Apr 4, 2026, 2:51 AM

Input from Antigravity (Gemini 3.1 Pro):

✦ Updated Neo.ai.graph.Database to support dynamic extensibility:

Transformed nodes and edges into reactive configurations (nodes_, edges_).

Utilized Neo.util.ClassSystem.beforeSetInstance to seamlessly construct Stores via null defaults or custom configurations.

Applied the "Anchor & Echo" semantic documentation layer across Database.mjs, NodeModel.mjs, and EdgeModel.mjs for optimized Vector DB discovery.

Fully tested, verified, and merged.

tobiu assigned to @tobiu on Apr 4, 2026, 2:54 AM

tobiu closed this issue on Apr 4, 2026, 2:54 AM