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	14734
title	Wedge live evidence: five-state render-verify + whitebox-NL e2e for the keeper chat surface
state	Closed
labels	enhancementai
assignees	[]
createdAt	Jul 4, 2026, 11:58 AM
updatedAt	5:38 AM
githubUrl	https://github.com/neomjs/neo/issues/14734
author	neo-fable
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	5:38 AM

Wedge live evidence: five-state render-verify + whitebox-NL e2e for the keeper chat surface

Closed Backlog/active-chunk-3 enhancementai

neo-fable commented on Jul 4, 2026, 11:58 AM

Context

Split from #14720 at PR review cycle 1 (the close-target/evidence RA): the state-binding leaf (PR #14727) is unit-proven through the real spine, but the LIVE evidence — browser render-verify of the five states against the merged SSOT artifact, and the whitebox-NL e2e driving the visible surface — requires the merge train (#14712 → #14719 → #14727) plus the SSOT (#14692) on dev. Deferring evidence ACs on a closing ticket would close them unmet; they live here instead.

Acceptance Criteria

Live render-verify: all five states render as drawn against apps/agentos/design/chat-creation-plan.html (the house browser-rig discipline; computed-style probes, not screenshot-guessing).
Whitebox-NL e2e: mount AgentOS, drive the intake through Neural Link semantic selectors (the #14705 loopback pattern is the template), assert the happy wedge (typed intent → materialized grid in the stage → registry record) and the refusal wedge (gate-refused blueprint → ERROR state text carries the reason verbatim → retry recovers) from the LIVE surface.
The no-background-calls / route-parser invariants re-asserted at the e2e grain.

Blocked-by

PR #14712 · PR #14719 · PR #14727 (the train) · #14692's SSOT artifact on dev (verify at claim).

#14720 (the state-binding leaf this evidences — its PR resolves it; THIS ticket carries the live-proof ACs) · #14705 (the whitebox loopback template) · #14645/PR #14692 (the drawn bar) · parent #13349.

First-claim: @neo-fable at the train's merge; claimable by anyone — the spec stands alone.

Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "wedge live evidence render verify whitebox e2e five states keeper chat surface"

Wedge live evidence: five-state render-verify + whitebox-NL e2e for the keeper chat surface

Context

Acceptance Criteria

Blocked-by

Related