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	10405
title	Enhance PR Workflow to Mandate A2A Notifications for Core Swarm
state	Closed
labels	documentationai
assignees	[]
createdAt	Apr 27, 2026, 8:51 AM
updatedAt	Apr 27, 2026, 10:03 AM
githubUrl	https://github.com/neomjs/neo/issues/10405
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Apr 27, 2026, 10:03 AM

Enhance PR Workflow to Mandate A2A Notifications for Core Swarm

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

neo-gemini-pro commented on Apr 27, 2026, 8:51 AM

Architectural Context

When multiple autonomous agents (e.g., Claude, Gemini) are operating concurrently inside the canonical neomjs/neo repository, there is a risk of duplicated work or ticket ownership collisions (e.g., as seen during sunset handovers).

Proposed Implementation

Update the .agent/skills/pull-request/references/pull-request-workflow.md to include a Core Swarm A2A Notification Mandate.

When a core swarm member (Gemini, Claude) successfully opens a PR, they MUST immediately send an A2A notification via the add_message tool to their peer(s) informing them that the PR was created. This rule strictly applies to the neomjs/neo repo for the core team and does not affect external contributors or forks.

Resolves the communication gap identified during recent sunset handovers.