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: Implement PR-Driven Workflow Protocol (#9855)
author	tobiu
state	Merged
createdAt	Apr 10, 2026, 11:50 AM
updatedAt	Apr 10, 2026, 12:05 PM
closedAt	Apr 10, 2026, 12:05 PM
mergedAt	Apr 10, 2026, 12:05 PM
branches	`dev` ← `agent/9855-pr-workflow`
url	https://github.com/neomjs/neo/pull/9856

Merged

tobiu commented on Apr 10, 2026, 11:50 AM

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

Input from Antigravity (Gemini 3.1 Pro):

✦ # PR Review Summary

Status: Approved

Thanks for getting this together! The shift to a PR-Driven Workflow is absolutely critical for the safety and scalability of the Neo.mjs Agent Swarm. Let's merge this architecture update.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 - Enforces strict branching protocols and perfectly adheres to the asynchronous swarm collaboration strategy.

[CONTENT_COMPLETENESS]: 100 - The "Fat Ticket" protocol was rigorously updated and explicitly documents the PR handoff workflow.

[EXECUTION_QUALITY]: 100 - Clean markdown formatting, zero regressions, and perfectly clear instructions.

[PRODUCTIVITY]: 100 - Solved the primary goal of stopping agents from bypassing code-review by pushing directly to dev or main.

[IMPACT]: 95 - High impact. Protects the core codebase from hallucination corruption.

[COMPLEXITY]: 30 - Documentation alterations; low cognitive load but requires high precision.

🕸️ Context & Graph Linking

Target Epic / Issue ID: #9855

Related Graph Nodes: [Agent_Core_Guidelines], [Swarm_Architecture]

🧠 Graph Ingestion Notes

[RETROSPECTIVE]: This architectural shift allows smaller offline models (like Gemma 4:31B) to reliably extract meaningful feedback from human-curated PR reviews rather than noisy, unverified session logs. An excellent pivot in the Neo architecture.

📋 Required Actions

No further changes required. Ready to merge!