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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	feat(ai): expose Neural Link dock fixture helpers (#14816)
author	neo-gpt
state	Open
createdAt	8:44 PM
updatedAt	8:44 PM
closedAt
mergedAt
branches	`dev` ← `codex/14816-neural-link-dock-fixture`
url	https://github.com/neomjs/neo/pull/14818
contentTrust
projected
quarantined	0
signals	[]

Open

neo-gpt commented on 8:44 PM

Refs #14816

Draft code slice for the Neural Link dock SDK/fixture bridge. It exports NeuralLink_DockService from ai/services.mjs, adds getDockTopology() and executeDockOperation() to the whitebox Neural Link fixture, and pins those two surfaces in the existing SDK resilient-load spec.

Evidence: L2 (static SDK/fixture proof plus pre-commit source gates) -> L2 required for the bridge ACs. Residual: #14816 matrix-row AC is blocked until #14817 lands on dev, because learn/agentos/tooling/NeuralLinkCapabilityMatrix.md is introduced by #14817.

Deltas from ticket

This is intentionally draft-only: the code bridge is complete, but the #14783 matrix row cannot be flipped from gap status to fixture-supported status until #14817 merges.
The broad spacing delta in ai/services.mjs is mechanical check-block-alignment.mjs --fix compliance; the semantic SDK change is only the new DockService import, wrapper, and export.

Test Evidence

node --check ai/services.mjs
node --check test/playwright/fixtures.mjs
node --check test/playwright/unit/ai/services-resilient-load.spec.mjs
node buildScripts/util/check-block-alignment.mjs ai/services.mjs test/playwright/fixtures.mjs test/playwright/unit/ai/services-resilient-load.spec.mjs
git diff --check
npm run agent-preflight -- --no-fix ai/services.mjs test/playwright/fixtures.mjs test/playwright/unit/ai/services-resilient-load.spec.mjs
Commit hook passed: whitespace, shorthand, AiConfig test-mutation lint, JSDoc type lint, ticket archaeology, and staged block alignment.

Local focused unit runner note: npm run test-unit -- test/playwright/unit/ai/services-resilient-load.spec.mjs remained silent for roughly 90 seconds and was interrupted; which chroma returns chroma not found, matching the local unit webServer prerequisite issue seen on #14817. CI should supply the real unit verdict.

Post-Merge Validation

After #14817 lands, rebase this branch, update learn/agentos/tooling/NeuralLinkCapabilityMatrix.md so the dock rows no longer say fixture support is missing, change this body from Refs #14816 to Resolves #14816, and mark ready for review.

Commits

77f7c48405 — feat(ai): expose Neural Link dock fixture helpers (#14816)

Authored by Euclid (GPT-5, Codex Desktop). Session 6439a7c5-5f2f-4658-9226-835c317c7a0b.