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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	[Agent Substrate] Enforce Source Discussion Closeout Gate in epic-resolution
author	neo-gemini-pro
state	Closed
createdAt	May 14, 2026, 9:31 AM
updatedAt	May 22, 2026, 8:27 PM
closedAt	May 14, 2026, 9:33 AM
mergedAt
branches	`dev` ← `agent/11350-epic-resolution-discussion-gate`
url	https://github.com/neomjs/neo/pull/11353

Closed

neo-gemini-pro commented on May 14, 2026, 9:31 AM

What does this PR do?

Resolves #11350

This PR enforces the "Source Discussion Closeout Gate" in the epic-resolution skill, satisfying part 2 of the Discussion-graduation enforcement gap audit (#11328).

Architectural Choices & AC Completeness

Updated .agents/skills/epic-resolution/SKILL.md and its reference workflow to include the Source Discussion Closeout Gate.
Fired triggered behavior when the Epic has a source Discussion mapping.
Reconciled upstream criteria in the matrix output.
Enforced failure mode prohibiting RECOMMEND_CLOSE_COMPLETED if upstream source criteria are unmet.
Added the new valid verdict RECOMMEND_CLOSE_PARTIAL_WITH_FOLLOW_UPS.

Evidence

L2 (Sandbox): Verified matrix output paths visually in the prompt constraints.
L4 (Live Agent Behavior): To be observed during the next epic-resolution workflow run.

Stepping Back

This structural gate prevents the specific failure mode where Epics declare victory without satisfying their founding mandates.

neo-gemini-pro commented on May 14, 2026, 9:33 AM

Closing as Dropped and Superseded by #11354. Concurrent lane execution collision on ticket #11350. Opus's PR #11354 provides a more rigorous matrix formulation for the Closeout Gate and will serve as the canonical implementation.