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	16428
title	[DATA-SYNC-ALARM] Data Sync Pipeline: 21 consecutive failures since 2026-08-02T20:13:14Z
state	Closed
labels	[]
assignees	[]
createdAt	Aug 3, 2026, 9:51 AM
updatedAt	Aug 5, 2026, 2:19 PM
githubUrl	https://github.com/neomjs/neo/issues/16428
author	github-actions
commentsCount	20
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	21
signals	[]
blockedBy	[]
blocking	[]
closedAt	Aug 5, 2026, 2:19 PM

[DATA-SYNC-ALARM] Data Sync Pipeline: 21 consecutive failures since 2026-08-02T20:13:14Z

Closed Backlog/active-chunk-12 []

github-actions commented on Aug 3, 2026, 9:51 AM

Standing alarm — one per breach episode. This issue is maintained by dataSyncWatchdog.mjs: the body is refreshed on every breach evaluation and the issue closes automatically on recovery. Streak: 21 consecutive failures on dev. Last success: 2026-08-02T20:13:14Z [QUARANTINED_URL: github.com]. Latest failure: run 30981780309 [QUARANTINED_URL: github.com]. Corpus facets (committed dev; a green pipeline cannot attest to this backlog):

facet	last commit on `dev`	age	status
`issues`	2026-08-02T20:41:06Z	61.3h	STALE
`pulls`	2026-08-02T20:41:06Z	61.3h	STALE
`discussions`	2026-08-02T20:41:06Z	61.3h	STALE
Breach reasons:

21 consecutive failures (threshold 3)
last success is 61.8h old (threshold 24h)
corpus facet issues is 61.3h old (threshold 48h)
corpus facet pulls is 61.3h old (threshold 48h)
corpus facet discussions is 61.3h old (threshold 48h) The pipeline is degrading silently: runs fail on schedule and nothing else surfaces it. Root-cause work (if any) is tracked elsewhere; this issue only carries the alarm.

tobiu referenced in commit cdd34c5 - "fix(ci): the Data Sync failure lead states the observed class, not a credential cause it cannot know (#16530) (#16531) on Aug 5, 2026, 1:24 PM