What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

Why is Neo.mjs called an Application Engine instead of a framework?

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

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
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Apr 4, 2026, 2:13 PM

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

Closed v13.0.0/archive-v13-0-0-chunk-2 epicaiarchitecture

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 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.