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	>-
author	neo-opus-ada
state	Closed
createdAt	Jun 21, 2026, 6:38 PM
updatedAt	Jul 27, 2026, 12:07 AM
closedAt	Jun 21, 2026, 6:55 PM
mergedAt
branches	`dev` ← `agent/sync-revert-mirror-redaction`
url	https://github.com/neomjs/neo/pull/13787
contentTrust
projected
quarantined	0
signals	[]

Closed

neo-opus-ada commented on Jun 21, 2026, 6:38 PM

Resolves #13786. Reverts #13775 + #13779.

Summary

Restores the synced content mirrors to their REAL upstream authorship. The gate-9 mirror-redaction (#13775 / #13779) wrongly edited real third-party GitHub content — tickets / PRs / discussions authored by real external contributors from their own accounts. That (1) corrupts real authorship / identity and (2) causes recurring hourly data-sync dev-branch conflicts (the pipeline re-syncs the real upstream content, which conflicts with the redacted mirrors every hour). §critical_gates#9 (no client names in public artifacts) governs OUR-authored artifacts, NOT the mirror of real third-party content.

Deltas

Revert #13779 — 43 archive mirror files restored to as-authored.
Revert #13775 — 5 current mirror files restored to as-authored.
Net: synced content = exactly as authored upstream; zero hand-redaction remains.

Test Evidence

Evidence: L1 — clean revert, no conflicts; real upstream content confirmed restored in the affected files. No code changed — a pure content-mirror restore on a sanctioned agent/sync-* branch (the pipeline's own content, un-edited).

Post-Merge Validation

Hourly data-sync rebases cleanly onto dev (no recurring conflict).
gate-9 redaction tooling (#13772 / #13773 / #13776) re-scoped to our-authored surfaces only — NOT the sync write path.

neo-opus-ada commented on Jun 21, 2026, 6:55 PM

Closing — a revert restores the STALE (pre-patch) content, i.e. it re-introduces the very leak. The real fix is a forward RE-SYNC of the stale resources/content/** mirror from the team-patched GitHub source. Not a revert, not a script. Ref #13786.