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	9939
title	Epic: Autonomous Worker Dispatcher Pipeline (RLAIF Phase 2)
state	Closed
labels	epicaiarchitecture
assignees	tobiu
createdAt	Apr 12, 2026, 8:58 PM
updatedAt	May 17, 2026, 9:19 PM
githubUrl	https://github.com/neomjs/neo/issues/9939
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 9952 Sandman Handoff: Top 5 Actionable Tasks Dashboarding, [ ] 9954 Epic: The Self-Healing Protocol
blocking	[]
closedAt	May 17, 2026, 9:19 PM

Epic: Autonomous Worker Dispatcher Pipeline (RLAIF Phase 2)

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

tobiu commented on Apr 12, 2026, 8:58 PM

Context

The DreamService (Sandman) pipeline is now structurally stabilized and successfully calculating the Mathematical Golden Path at the end of the REM sleep cycle. The background daemon formally outputs sandman_handoff.md populated with the top priority OPEN issue mapped dynamically against the system's current vector context.

Scope

We must implement the Agent Dispatcher orchestrator. This service will act as the native bridge from REM Sleep back to Active Execution by:

Natively reading sandman_handoff.md.
Extracting the Target Node ID context.
Spawning headless, autonomous V8 agent instances (Dev Agent / QA Agent) sequentially to execute the top priority context dynamically without human prompts.
Feeding the results into the Automated Playwright Evaluator (#9905) for reward propagation.

Origin Session

Origin Session ID: af26000d-914a-4eb0-8d28-2c09e9cb4cb5

tobiu added the epic label on Apr 12, 2026, 8:58 PM

tobiu added the ai label on Apr 12, 2026, 8:58 PM

tobiu added the architecture label on Apr 12, 2026, 8:58 PM

tobiu assigned to @tobiu on Apr 12, 2026, 8:59 PM

tobiu marked this issue as being blocked by #9954 on Apr 13, 2026, 1:13 PM

tobiu marked this issue as being blocked by #9952 on Apr 13, 2026, 1:13 PM