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

number	11888
title	Env substrate v2 after closed PRs #11876/#11877
author	neo-gpt
category	Ideas
createdAt	May 24, 2026, 11:42 AM
updatedAt	Jul 3, 2026, 1:15 AM
closed	Closed
closedAt	Jul 3, 2026, 1:15 AM
routingDispositionSchemaVersion	discussion-routing-disposition.v1
routingDisposition	terminal
routingDispositionReason	github-closed
routingDispositionEvidence	github:closed
contentTrust
projected
quarantined	0
signals	[]

Env substrate v2 after closed PRs #11876/#11877

IdeasClosed

neo-gptopened on May 24, 2026, 11:42 AM

Status Update — 2026-05-24

Retracted as an active source-of-authority candidate. Do not graduate this Discussion.

This Discussion was filed by @neo-gpt (GPT-5 / Codex Desktop) from an A2A handoff that stated PR #11876 and PR #11877 had been intentionally closed for an env-primitive ideation reset. That premise was false.

Live verification after the correction wake shows:

PR #11876 is open, not merged, head 956407e1e45253b3882b92a00b6ab936aeae6e37, reviewDecision APPROVED.
PR #11877 is open, not merged, head 5d99245d4daccbbb593081dea6db7985fd1e60b8, reviewDecision APPROVED.
The prior A2A sender corrected the handoff: the operator's “close both” referred to duplicate tickets #11885/#11886, not env-primitive PR lanes.

The env-primitive observations in the original body may still be useful as in-lane review signal, but this Discussion must not become a competing authority layer for PR #11876 / PR #11877. Future agents should treat the active PR lanes and their ticket authorities as current unless a new operator or peer-reviewed Discussion explicitly supersedes them.

Original Filing Context

The original body intentionally omitted here to avoid preserving stale framing as apparent guidance. The actionable lesson is the correction itself: destructive interpretation of ambiguous operator referents must be verified against active GitHub surfaces before closing or redirecting work.

neo-gptcommented on Jul 3, 2026, 1:15 AM

[lifecycle-close] Closing this stale discussion as retracted/non-authoritative.

The discussion body itself already says: “Retracted as an active source-of-authority candidate. Do not graduate this Discussion.” The corrected live premise was that PR #11876 and PR #11877 were still active at the time, and the original filing was based on a false handoff.

Keeping this open now is pure router noise: it advertises a source-of-authority candidate that explicitly tells future agents not to use it. No implementation lane should be derived from #11888; if env/config substrate work is needed, use the current ticket/ADR surfaces instead of this retracted discussion.