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

id	13786
title	revert: synced content mirrors are real third-party GitHub authorship — un-redact, leave as authored
state	Closed
labels	bugaiarchitectureneeds-re-triage
assignees	[]
createdAt	Jun 21, 2026, 6:38 PM
updatedAt	3:20 PM
githubUrl	https://github.com/neomjs/neo/issues/13786
author	neo-opus-ada
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 23, 2026, 10:01 PM

revert: synced content mirrors are real third-party GitHub authorship — un-redact, leave as authored

Closed v13.1.0/archive-v13-1-0-chunk-5 bugaiarchitectureneeds-re-triage

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

Problem

The gate-9 mirror-redaction (#13775 current mirrors, #13779 archive mirrors) wrongly altered real third-party GitHub content — tickets / PRs / discussions authored by real external contributors from their own accounts. Two harms:

Identity corruption — editing a real contributor's authored content (replacing a term inside their own ticket text) corrupts their authorship/identity. We must leave their content exactly as authored.
Recurring data-sync dev corruption — the hourly data-sync pipeline re-syncs the real upstream content, which then conflicts every hour with the redacted mirrors → repeated dev-branch rebase corruption.

Root cause (the misread)

§critical_gates#9 no client names in public artifacts governs our-authored artifacts (our PRs, issues, commits, code, docs, A2A) — NOT the synced mirror of real third-party GitHub content. The synced resources/content/** is pipeline-owned and reflects real upstream authorship; it must not be hand-edited.

Fix

Revert #13779 + #13775 (restore the mirrors exactly as authored).
Re-scope gate-9 redaction tooling (#13772/#13773, #13776) to our-authored surfaces only — NOT the sync write path (redacting on sync would re-corrupt real content + re-trigger the conflicts).

Acceptance

dev mirrors restored to real upstream content; no hand-redaction remains.
Hourly data-sync rebases cleanly (no recurring conflict).

Surfaced by @neo-opus-ada under operator escalation.