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	13733
title	who_is_online local-beacon mid-turn rescue (READ side) — #13498 AC2/AC3 leaf
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-grace
createdAt	Jun 21, 2026, 10:41 AM
updatedAt	Jun 21, 2026, 11:47 AM
githubUrl	https://github.com/neomjs/neo/issues/13733
author	neo-opus-grace
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 21, 2026, 11:47 AM

who_is_online local-beacon mid-turn rescue (READ side) — #13498 AC2/AC3 leaf

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

neo-opus-grace commented on Jun 21, 2026, 10:41 AM

Context

A narrow delivered leaf of #13498 — the AC2/AC3 read side: the local-only turn-presence beacon READ + the mid-turn rescue in whoIsOnline. Carved out so PR #13728 closes a fully-delivered leaf while #13498 stays open for AC4 (the beacon emission: mid-turn progress-refresh + a Claude turn-start hook), which is the remaining harness slice tracked on #13498.

#13498's AC1 (memory-recency PRIMARY, cross-topology) was already shipped; this leaf adds the local-only beacon corroboration layered on it.

Acceptance Criteria

TurnPresenceService.getFreshTurnPresence(agentIdentity, now) — reads the newest fresh active turn-presence beacon (freshUntil > now); null when no beacon (graceful absence).
WakeSubscriptionService._projectAgentLiveness rescues a memory-stale-but-beacon-fresh (mid-turn) agent to online in the stale-memory branch.
Local-only / never-gates-base: no beacon → the memory-recency verdict stands (beaconless/remote deployments never gated); the benched hard-gate is never upgraded.
Tested: rescue fires (stale-memory + fresh-beacon); stale-beacon non-gating; benched-not-rescued; no-beacon→no-op.

Delivered

PR #13728 — getFreshTurnPresence + the _projectAgentLiveness rescue; 72 WakeSubscriptionService + 5 TurnPresenceService specs green. Reviewed by @neo-opus-vega (live consumer case) + @neo-gpt (cross-family).

Board: #13 Agent Harness.

tobiu closed this issue on Jun 21, 2026, 11:47 AM