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	9684
title	Epic: AI - The "Strategic Co-Founder" Orchestrator (Sub-Epic of #9671)
state	Closed
labels	epicaiarchitecture
assignees	tobiu
createdAt	Apr 4, 2026, 2:04 PM
updatedAt	Apr 4, 2026, 2:13 PM
githubUrl	https://github.com/neomjs/neo/issues/9684
author	tobiu
commentsCount	1
parentIssue	9671
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 2:13 PM

Epic: AI - The "Strategic Co-Founder" Orchestrator (Sub-Epic of #9671)

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

Closedepicaiarchitecture

tobiu commented on Apr 4, 2026, 2:04 PM

Problem / Context

We have established a Native Knowledge Graph and bridged it to our ChromaDB semantic vectors to cure "Session Amnesia" via the Context Priming Engine (GraphRAG Hybrid). However, the [Frontier] node—which dictates the agent's startup context—is currently static.

Proposed Solution

We need an orchestration layer: the "Strategic Co-Founder" (Librarian/Coordinator Sub-Agent). This orchestration layer will actively manage the [Frontier] node. When project priorities pivot (e.g. from optimizing the Graph Database to building out Next.js UI), this sub-agent will inject those new priorities into the Graph's Edge relationships in real-time.

Frontier Mutations: Agents will have the capability to query and alter the [Frontier] node weights.
Sub-Agent Delegation: Establish a "Librarian" protocol to orchestrate shifting project contexts.
Cross-Session Coherence: Ensure that pivots executed in one session immediately influence the initialization of the next via get_context_frontier().

tobiu added the epic label on Apr 4, 2026, 2:04 PM

tobiu added the ai label on Apr 4, 2026, 2:04 PM

tobiu added the architecture label on Apr 4, 2026, 2:04 PM

tobiu added parent issue #9671 on Apr 4, 2026, 2:07 PM

tobiu assigned to @tobiu on Apr 4, 2026, 2:08 PM

tobiu referenced in commit fdf7407 - "docs: Add Strategic Co-Founder Protocol to AGENTS.md (#9684) on Apr 4, 2026, 2:12 PM

tobiu Apr 4, 2026, 2:13 PM

Input from Gemini 2.5 Pro (Antigravity):

✦ The "Strategic Co-Founder" Orchestrator infrastructure is complete.

Implemented native mutateFrontier capabilities in GraphService and MemoryService.

Exposed mutate_frontier as an MCP tool for agent use.

Added the "Strategic Co-Founder Protocol" to AGENTS.md (Section 5) which legally mandates agents to update the [Frontier] node whenever the human user explicitly pivots the task domain.

The core infrastructure for orchestrating strategic direction is live. Further Librarian workflows may be introduced as needed.

tobiu closed this issue on Apr 4, 2026, 2:13 PM