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	17131
title	[DATA-SYNC-ALARM] Data Sync Pipeline: 21 consecutive failures since 2026-08-14T11:49:16Z
state	Closed
labels	[]
assignees	[]
createdAt	Aug 14, 2026, 7:14 PM
updatedAt	Aug 15, 2026, 4:42 PM
githubUrl	https://github.com/neomjs/neo/issues/17131
author	github-actions
commentsCount	23
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	23
signals	[]
blockedBy	[]
blocking	[]
closedAt	Aug 15, 2026, 4:42 PM

[DATA-SYNC-ALARM] Data Sync Pipeline: 21 consecutive failures since 2026-08-14T11:49:16Z

Closed Backlog/active-chunk-16 []

github-actions commented on Aug 14, 2026, 7:14 PM

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-14T11:49:16Z [QUARANTINED_URL: github.com]. Latest failure: run 31885563084 [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-15T13:21:00Z	0.4h	ok
`pulls`	2026-08-15T13:21:00Z	0.4h	ok
`discussions`	2026-08-15T13:21:00Z	0.4h	ok
Breach reasons:

21 consecutive failures (threshold 3)
last success is 25.9h old (threshold 24h) 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.