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	14169
title	Cross-harness wake Tier-2: fleet manager — centralized scheduled re-invoke for the cloud swarm (v13.2 harness)
state	Closed
labels	enhancementaiarchitecturemodel-experience
assignees	[]
createdAt	Jun 27, 2026, 1:21 AM
updatedAt	Jun 27, 2026, 1:34 AM
githubUrl	https://github.com/neomjs/neo/issues/14169
author	neo-opus-vega
commentsCount	1
parentIssue	13012
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 27, 2026, 1:34 AM

Cross-harness wake Tier-2: fleet manager — centralized scheduled re-invoke for the cloud swarm (v13.2 harness)

Closed v13.1.0/archive-v13-1-0-chunk-7 enhancementaiarchitecturemodel-experience

neo-opus-vega commented on Jun 27, 2026, 1:21 AM

Problem

Tiers 0/1 are per-agent bridges. The full solution is a fleet manager that centrally schedules / re-invokes the cloud swarm — but that is the agent-harness / fleet-manager scope (Epic #13012, v13.2), not v13.1.

Fix shape

A fleet manager owning per-agent lifecycle + scheduled re-invoke (Tier-2 of Discussion #14145).
Subsumes Tiers 0/1 once live.

Acceptance Criteria

(v13.2) Fleet manager schedules / re-invokes cloud-swarm agents centrally.
Tiers 0/1 degrade gracefully under it.

Scope

v13.2 — agent-harness / fleet-manager. Parent #13012. Filed now to preserve substrate (operator: "if we pull them in or not, new tickets → otherwise lost substrate"). From Discussion #14145.

Live latest-open sweep: scanned 25-latest + Epic #13012; not ticketed. No duplicate.

Authored by Vega (Claude Opus 4.8, Claude Code). Origin Session ID: 1bb8a27b-ae0d-4668-a9a2-acbbe2387512