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	feat: Implement needs-re-triage negative ROI downgrade in DreamService (#9971)
author	tobiu
state	Merged
createdAt	Apr 13, 2026, 3:45 PM
updatedAt	Apr 13, 2026, 3:47 PM
closedAt	Apr 13, 2026, 3:47 PM
mergedAt	Apr 13, 2026, 3:47 PM
branches	`dev` ← `agent/9971-dream-service-triage-penalty`
url	https://github.com/neomjs/neo/pull/9972

Merged

tobiu commented on Apr 13, 2026, 3:45 PM

Architecture Modification

This PR intercepts the DreamService mathematical extraction engine. It natively parses the SQLite topological JSON object to verify if the needs-re-triage tag is applied to a task. If present, it executes a raw integer vector penalty of -10000 on the result, permanently isolating the ticket from the Golden Path generation system.

Testing

Included new Playwright mock configurations explicitly simulating a 1000.0 node structural weight with the tag applied.

Resolves #9971.

tobiu commented on Apr 13, 2026, 3:45 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ # PR Review Summary: PR #9972

Status: Approved

A textbook structural implementation establishing the Back-End isolation logic for automatically-rejected Neo-Swarm tasks. By manipulating the integer vector downstream rather than attempting complex sqlite SQL-layer topological rewrites, stability and testability are maximized.

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 100 - Executes perfectly on the Negative ROI validation paradigm defined in ticket-intake rules. Mathematically sinks bad components.

[CONTENT_COMPLETENESS]: 100 - Tests and production daemon integrated natively.

[EXECUTION_QUALITY]: 100 - Handled cleanly without hallucination. Explicit Playwright assertions map out mathematical routing logic.

[PRODUCTIVITY]: 100 - Task delivered accurately against #9971 parameters.

[IMPACT]: 90 - Extremely high impact for headless operations. Prevents sandman_handoff.md from constantly returning the same stale task to the topological queue.

[COMPLEXITY]: 20 - Purely mathematical Cartesian adjustments.

[EFFORT_PROFILE]: Critical Bugfix / Feature completing Swarm Loop.

🕸️ Context & Graph Linking

Target Epic / Issue ID: Resolves #9971

Related Graph Nodes: #9969 (Ticket Intake Rule)

🧠 Graph Ingestion Notes

[KB_GAP]: N/A

[TOOLING_GAP]: N/A

[RETROSPECTIVE]: Excellent synergy completing a Swarm task-loop capability. Agents can now formally reject via GitHub Label (Gate 1 - Front End) and the core Orchestrator officially ignores the rejection (Gate 2 - Back End) permanently without manual human db pruning. Both Front-End and Back-End loops are completely autonomous now.

📋 Required Actions

Ready to Squash & Merge!