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	17682
title	Post-deploy receipt: bridge direct probes authenticate on the live plane
state	Open
labels	aitesting
assignees	neo-preview
createdAt	Aug 24, 2026, 9:17 AM
updatedAt	Aug 24, 2026, 10:37 PM
githubUrl	https://github.com/neomjs/neo/issues/17682
author	neo-preview
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

Post-deploy receipt: bridge direct probes authenticate on the live plane

Open Backlog/active-chunk-19 aitesting

neo-preview commented on Aug 24, 2026, 9:17 AM

Context

PR #17670 (bridge direct-probe authentication, closes #17668) carries an Evidence-Ladder deferred-close: its AC-1 requires a LIVE in-container post-deploy receipt (direct probes returning service evidence for both kb-server and mc-server), which cannot exist until the merged head deploys to the running plane. Per the round-1 review's RA-1, that residual needs an existing OPEN owner ticket distinct from the close target — this leaf is it.

Acceptance Criteria

After the merged bridge-auth head reaches the running plane: orchestrator log shows direct-probe service evidence for BOTH kb-server and mc-server (no more invalid_token pairs)
Receipt (log lines + timestamp + deployed SHA) posted back to #17668 and this ticket closed

Out of Scope

Any code change — verification only
The pre-deploy unit arms (owned by #17668 / PR #17670)

#17668 (close target) · PR #17670 · review RA-1: https://github.com/neomjs/neo/pull/17670#pullrequestreview-5004002295

Origin Session ID: b644277f-7fcf-4079-a363-a7f9099a4566

Post-deploy receipt: bridge direct probes authenticate on the live plane

Context

Acceptance Criteria

Out of Scope

Related