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	13774
title	chore(ai): redact a confidential deployment identifier from synced content mirrors
state	Closed
labels	ai
assignees	neo-opus-vega
createdAt	Jun 21, 2026, 4:14 PM
updatedAt	Jun 21, 2026, 4:32 PM
githubUrl	https://github.com/neomjs/neo/issues/13774
author	neo-opus-vega
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 21, 2026, 4:32 PM

chore(ai): redact a confidential deployment identifier from synced content mirrors

Closed v13.1.0/archive-v13-1-0-chunk-5 ai

neo-opus-vega commented on Jun 21, 2026, 4:14 PM

Incident remediation (confidentiality, gate-9). A confidential deployment identifier leaked into the synced GitHub content mirrors under resources/content/. The live GitHub surfaces are already scrubbed by the team; the synced content mirrors do not reliably auto-update via re-sync (operator-flagged), so the current (non-archive) mirrors need a manual redaction.

Scope (this ticket): the current non-archive resources/content/ mirrors still carrying the identifier — 1 discussion mirror + 4 PR mirrors (the real contributor-handle ticket #9366 is intentionally excluded; that handle is legitimate). Replace with the operator-locked generic placeholder.

Out of scope / tracked separately by peers: the resources/content/archive/ mirrors (bulk) + the sync-pipeline write-guard that prevents re-introduction.

Self-assigned. Authored by @neo-opus-vega (Vega).

tobiu referenced in commit 5c5ad39 - "chore(ai): redact confidential deployment identifier from current content mirrors (#13774) (#13775) on Jun 21, 2026, 4:32 PM

tobiu closed this issue on Jun 21, 2026, 4:32 PM

tobiu referenced in commit 75d4984 - "chore(security): redact confidential deployment identifier from archive content mirrors (#13774) (#13779) on Jun 21, 2026, 5:43 PM