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	11724
title	Production reference deployment profile + compose
state	Closed
labels	enhancementaibuild
assignees	neo-opus-ada
createdAt	May 21, 2026, 7:23 PM
updatedAt	May 22, 2026, 10:11 AM
githubUrl	https://github.com/neomjs/neo/issues/11724
author	neo-opus-ada
commentsCount	1
parentIssue	11720
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 11721 Cloud deployment topology + scheduler-task-taxonomy ADR
blocking	[]
closedAt	May 22, 2026, 10:11 AM

Production reference deployment profile + compose

Closed v13.0.0/archive-v13-0-0-chunk-12 enhancementaibuild

neo-opus-ada commented on May 21, 2026, 7:23 PM

Context

Sub C of Epic #11720 (Cloud Agent OS Deployment Readiness). MVP-critical. Blocked-by D0 #11721 (topology decision); builds on Sub B.

The Problem

There is no production-shaped reference deployment profile in-repo. docker-compose.yml runs only the KB/MC/Chroma baseline — the orchestrator, model provider, and reverse proxy are in no composition. Reverse-proxy refs (ai/mcp/deploy/proxy/{Caddyfile,nginx.conf}) are unwired and carry a port mismatch (proxy KB 3001 / MC 3002 vs compose KB 3000 / MC 3001). Backups are not redeploy-safe.

The Fix

Author the canonical production reference deployment profile under ai/deploy/: a copy-paste-ready docker-compose profile running the D0-decided topology (KB, MC, Chroma, orchestrator-or-ADR-justified-exclusion, model provider, reverse proxy); resolve the proxy↔compose port mismatch; wire the reverse proxy + TLS termination; redeploy-safe persistence — bind-mount .neo-ai-data/backups (+ a declared /data convention) so a container rebuild cannot discard backup artifacts.

Acceptance Criteria

A canonical production docker-compose reference profile exists, running the full D0-decided topology.
Reverse proxy + TLS termination wired into the profile; the port mismatch is resolved.
Redeploy-safe persistence: backups + data on bind-mounts/volumes that survive a container rebuild.
The profile is copy-paste-runnable (the Sub D Milestone-0 SSE healthcheck demo runs against it).

Out of Scope

The topology decision (D0 #11721) + the topology capability (Sub B).
Healthcheck / journey proof (Sub D).

Parent #11720 · blocked-by #11721 (D0) · #10803 (external exposure) · #10801 (reference Docker/compose artifacts) · Origin Discussion #11718 §5 Sub C.

Origin Session ID

8e1dc8ca-b5a5-4479-b3cf-31918eb4a5b2

tobiu referenced in commit 0d95739 - "feat(deploy): reference deployment profile + ingress (#11724) (#11747) on May 22, 2026, 10:11 AM

tobiu closed this issue on May 22, 2026, 10:11 AM