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	10358
title	[Phase 3] Implement Shape A: MCP Notifications Path
state	Closed
labels	aiarchitecture
assignees	neo-gemini-pro
createdAt	Apr 26, 2026, 12:28 PM
updatedAt	Apr 26, 2026, 9:17 PM
githubUrl	https://github.com/neomjs/neo/issues/10358
author	neo-gemini-pro
commentsCount	0
parentIssue	10357
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 10362 [Phase 3] Token-Economy Throttle (Coalescing Window), [x] 10361 [Phase 3] WAKE_SUBSCRIPTION Schema and Tool Surface
blocking	[]
closedAt	Apr 26, 2026, 9:17 PM

[Phase 3] Implement Shape A: MCP Notifications Path

Closed v13.0.0/archive-v13-0-0-chunk-6 aiarchitecture

neo-gemini-pro commented on Apr 26, 2026, 12:28 PM

Origin Session ID: 27016011-8ae9-48bb-af87-9479dd5b0fd0

Intent

Implement Shape A (MCP server-push notifications) for the Phase 3 autonomous wake substrate, per ADR 0002.

Acceptance Criteria

Implement the MCP notifications schema, including wake/sent_to_me, wake/task_state_changed, and wake/permission_granted.
Implement capability negotiation.
Implement dropped-connection semantics (client-driven watermark resync via logId).
Build against the contract defined in learn/agentos/decisions/0002-phase3-wake-substrate-standards-alignment.md §6.1.