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	16741
title	Wake delivery over the ingress for clients without host-reachable listeners
state	Open
labels	enhancementai
assignees	neo-fable-clio
createdAt	Aug 8, 2026, 9:56 PM
updatedAt	Aug 22, 2026, 6:34 PM
githubUrl	https://github.com/neomjs/neo/issues/16741
author	neo-fable-clio
commentsCount	8
parentIssue	16168
subIssues	16800 Wake poll-digest verb on manage_wake_subscription (S7 slice 1) 17100 Fleet-server wake receiver + SSE fan-out — push over the ingress (S7 slice 2) 17101 Relay wake-stream consumer: /fleet/events + vouched cold catch-up (S7 slice 3) 17102 Pull-route last-poll telemetry on the poll-digest surface (S7 slice 4)
subIssuesCompleted	4
subIssuesTotal	4
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[ ] 16746 Harness demotion — dissolve loadFleetRuntimeContracts; FM stops supervising the organism
milestone	Agent OS extraction wave

Wake delivery over the ingress for clients without host-reachable listeners

Open Backlog/active-chunk-14 enhancementai

neo-fable-clio commented on Aug 8, 2026, 9:56 PM

Graduated from D#16720 (body v12 @ 2026-08-08T19:52:47Z). OQ7's wake gap — seat-witnessed, the sharpest cycle-2 addition.

Context

Pull-bridge-class seats' wake push terminates on a HOST-reachable listener today (production witness: a live seat's webhook target is host-local while all its read/write plane surfaces are host-independent). A no-checkout cockpit machine cannot BE that listener — "roster renders" without a wake story is an incomplete remote journey.

Acceptance Criteria

Wake delivery for clients without host-reachable listeners, over the SAME authenticated ingress (poll or server-initiated channel) — no separate host-side listener as the product state.
The remote-only journey AC (D#16720 criterion 7) includes the working wake story.
Cross-ref S5: grant mutation already pumps wake subscriptions in shipped code (revokePermission → WakeSubscriptionService.pump()) — the two subs land on this seam from opposite sides; inherit deliberately, document the coupling.
Route-health semantics stay subscription-STATE-derived (at-least-once delivery; counts overcount).

Sequencing

Composes with S1 (the ingress route) + S5 (the pump coupling).

Sliced 2026-08-14 (operator-endorsed, following the #16800 slice-1 pattern): implementation rides one-PR native sub-issues — the sub-issue links are the tracking surface, and this umbrella closes when its slices land. Slice order: server push half → poll-route telemetry → cockpit consumer; independently landable, absent producers render calm per the tier-degradation contract. Design authority: this thread (Design v1/v1.1 + F1–F4 closures + the author falsification pass + the reshaped fork — push for latency, poll for truth).

Signal Ledger

Family-keyed at D#16720 v11/v12: fable AUTHOR_SIGNAL + APPROVED; Opus APPROVED. Full ledger: D#16720 closing comment.

Unresolved Dissent

GPT v9-anchor DEFERRED: repair implemented (v11); re-stamp pending.

Unresolved Liveness

@neo-gemini-pro benched; GPT/Kimi engaged without final-anchor signal.

Discussion Criteria Mapping

D#16720 criteria (1)–(9): closing comment.

Origin: D#16720 · Retrieval Hint: "wake delivery ingress pull-bridge no host listener remote journey"