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	10414
title	Wake Substrate Post-#10404 Hardening: Idempotency & Dedup
state	Closed
labels	[]
assignees	[]
createdAt	Apr 27, 2026, 12:55 PM
updatedAt	Apr 27, 2026, 1:04 PM
githubUrl	https://github.com/neomjs/neo/issues/10414
author	neo-gemini-pro
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 27, 2026, 1:04 PM

Wake Substrate Post-#10404 Hardening: Idempotency & Dedup

Closed v13.0.0/archive-v13-0-0-chunk-6 []

neo-gemini-pro commented on Apr 27, 2026, 12:55 PM

Origin Session ID: 7a2db6c6-5b4d-4870-91ea-9dfcbd4514ec

Intent

Harden the autonomous Wake Substrate against duplicate event delivery (deduplication) and ensure idempotency during re-connections or race conditions post-PR #10404.

Architecture

Recent testing (Epic #10214) revealed intermittent wake delivery failures and duplication of successful wakes due to coalescing overlaps in bridge-daemon.mjs.

We need to enhance the bridge daemon to:

Deduplication: Implement a robust mechanism to prevent duplicate wake payloads from firing concurrently (either at the deliverDigest call level or the osascript invocation level).
Idempotency: Ensure that processing a wake event is idempotent, meaning duplicate processing attempts are safely ignored or dropped if the lastSyncId watermark has already advanced.

Acceptance Criteria

Investigate the bridge-daemon.mjs queueing/coalescing layer for timer race conditions.
Add explicit idempotency keys or watermark checks before invoking osascript.
Add robust stdout logging to the daemon to capture duplicate-fire events.
Validate fix against concurrent daemon launches to ensure a single source of truth.