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	10319
title	chore(ai): define and implement heartbeat concurrency semantics
state	Closed
labels	enhancementaitestingagent-role:devagent-task:in-progressarchitecture
assignees	neo-gpt
createdAt	Apr 25, 2026, 4:53 AM
updatedAt	May 1, 2026, 10:38 PM
githubUrl	https://github.com/neomjs/neo/issues/10319
author	neo-gemini-pro
commentsCount	3
parentIssue	10311
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	May 1, 2026, 10:38 PM

chore(ai): define and implement heartbeat concurrency semantics

Closed v13.0.0/archive-v13-0-0-chunk-6 enhancementaitestingagent-role:devagent-task:in-progressarchitecture

neo-gemini-pro commented on Apr 25, 2026, 4:53 AM

Context

As part of Epic #10311 (Swarm Autonomy Phase 1), the swarm-heartbeat.sh script will poll and wake up active terminal sessions.

The Problem

If wake N is mid-work (e.g. an agent is currently processing a complex task or running tests) and wake N+1 fires from the cronjob, the system's behavior is currently unspecified. Without defined concurrency semantics, overlapping heartbeats could corrupt session context, queue redundant tasks, or interrupt long-running inferences.

The Fix

Define the concurrency semantics for overlapping heartbeats (e.g. skip if active, queue if idle, or abort-and-restart).
Implement a lock or semaphore in the outer wrapper or Memory Core to enforce these semantics.
Ensure that active agents are not disturbed by subsequent pulses while they are WORKING.

Acceptance Criteria

Concurrency rules for heartbeat pulses are defined.
Lock mechanism (file-based, SQLite-based, or wrapper-level) is implemented to prevent concurrent pulse collisions.

Origin Session ID: dd277d9c-8f9c-44c7-8607-cb68bc42fac0

tobiu referenced in commit 987144f - "feat(ai): add heartbeat concurrency mutex helper (#10319) (#10598) on May 1, 2026, 10:38 PM

tobiu closed this issue on May 1, 2026, 10:38 PM