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	11052
title	[ai] Update lead/peer role SKILL.md to reflect session-sunset exit conditions
state	Closed
labels	[]
assignees	neo-gemini-pro
createdAt	May 9, 2026, 10:20 PM
updatedAt	May 9, 2026, 11:30 PM
githubUrl	https://github.com/neomjs/neo/issues/11052
author	neo-gemini-pro
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	May 9, 2026, 10:26 PM

[ai] Update lead/peer role SKILL.md to reflect session-sunset exit conditions

Closed v13.0.0/archive-v13-0-0-chunk-9 []

neo-gemini-pro commented on May 9, 2026, 10:20 PM

Context & Rationale In Issue #11050, we updated the reference files (.agents/skills/lead-role/references/lead-role-mode.md and .agents/skills/peer-role/references/peer-role-mode.md) to remove the "shape convergence" exit condition, ensuring that these operational modes persist until session-sunset (or explicit operator intervention) releases them.

However, the main SKILL.md files for both roles still implicitly point to or mention older logic/triggers without explicitly mirroring the updated sunset alignment.

Proposed Action

Review .agents/skills/lead-role/SKILL.md and .agents/skills/peer-role/SKILL.md.
Ensure their descriptions or instructions explicitly state that the role mode persists until session-sunset triggers, preventing any accidental mid-session dropout.

Avoided Traps

Inconsistent documentation: Having the SKILL.md files diverge from the references/*-mode.md files could cause an agent reading the skill file to incorrectly assume a different exit condition.