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	docs: Enforce ''Resolves'' keyword for automatic PR closure (#9859)
author	tobiu
state	Merged
createdAt	Apr 10, 2026, 12:13 PM
updatedAt	Apr 10, 2026, 12:14 PM
closedAt	Apr 10, 2026, 12:14 PM
mergedAt	Apr 10, 2026, 12:14 PM
branches	`dev` ← `agent/9859-enforce-resolves-keyword`
url	https://github.com/neomjs/neo/pull/9860

Merged

tobiu commented on Apr 10, 2026, 12:13 PM

Updates the ticketing protocol and PR templates to mandate the Resolves #[ID] string, ensuring GitHub closes the target issues upon merge securely. Resolves #9859.

tobiu commented on Apr 10, 2026, 12:13 PM

Input from Antigravity (Gemini 3.1 Pro):

✦ # PR Review Summary

Status: Approved

Excellent update. Catching the fact that Closes didn't correctly trigger github's auto-close inside #9856 was crucial. Specifying Resolves explicitly saves a huge amount of manual tracking work. Let's merge!

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 - Maintaining a clean state across GitHub tracking objects is necessary for the graph.

[CONTENT_COMPLETENESS]: 100 - Both the PR Template and the Core Guidelines have been updated accurately.

[EXECUTION_QUALITY]: 100 - Clean markdown modifications.

[PRODUCTIVITY]: 100 - The primary goal of standardizing the Resolves keyword has been achieved.

[IMPACT]: 60 - Medium impact, specifically fixing issue pipeline hygiene.

[COMPLEXITY]: 10 - Highly isolated, simple documentation changes.

🕸️ Context & Graph Linking

Target Epic / Issue ID: Resolves #9859

Related Graph Nodes: [Agent_Core_Guidelines], [Ticketing_Protocol]

🧠 Graph Ingestion Notes

[RETROSPECTIVE]: Consistently enforcing the exact GH keyword triggers is vital when bridging autonomous agent networks with legacy tracking systems. Always verify that GitHub receives the correct literal string.

📋 Required Actions

Code perfectly reflects what was discussed. Ready for merge.