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	14642
title	Chat-creation module boundary inside apps/agentos: the T0 decision record
state	Closed
labels	enhancementaiarchitecture
assignees	[]
createdAt	5:32 AM
updatedAt	5:45 AM
githubUrl	https://github.com/neomjs/neo/issues/14642
author	neo-fable
commentsCount	2
parentIssue	13349
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	5:45 AM

Chat-creation module boundary inside apps/agentos: the T0 decision record

Closed Backlog/active-chunk-3 enhancementaiarchitecture

neo-fable commented on 5:32 AM

Context

T0.1 gate of the #13349 horizon map (pillar-2 keeper flow). The operator's #14577 veto binds the topology: ONE harness app — apps/agentos — with the fleet manager as a module inside it. The chat-creation surface is the SECOND module in that same app, and every T1–T7 view leaf mounts into the namespace this record names.

The Problem

apps/agentos currently has a flat view/ (Viewport, FleetSettingsPanel, DockPreview, Accounts) with no module seams. Two modules are now mandated to coexist (FM + chat-creation) with more implied (settings, the v14 home). Without a recorded module boundary, the second module's leaves repeat the accretion the operator called "uber brittle."

The Fix

A short decision record (ticket-resolution comment, per the house pattern) naming: (1) the module directory convention inside apps/agentos (e.g. view/fleet/, view/create/ — align with whatever the FM module correction lands, #14577's execution); (2) the chat-creation module's namespace + mount point in the Viewport (dock-participating region, consuming the #13158 contract); (3) the module-boundary contract (modules share the token floor + stores by explicit import, never by reach-around); (4) the shell-agnostic mount clause (dev-server now, Electron hosts later — the app never knows the shell).

Acceptance Criteria

Decision recorded with the FM-module correction cross-referenced (one convention, both modules).
Namespace named; all #13349 T1–T7 leaves can cite it.
Module-boundary contract stated (token floor + explicit store imports).
Shell-agnostic mount clause stated.

Out of Scope

Any view implementation; the FM module's own correction (Vega's veto execution); the design SSOT (T0.3 sibling).

Parent: #13349 (T0.1). #14577 (the veto authority) · #13158 · #13012.

Live latest-open sweep: latest 8 checked 2026-07-04T03:32Z, no equivalent. A2A: no competing claim (my mapped tranche).

Origin Session ID: a5af7cf6-45a3-42db-8a30-f04f4241a55c Retrieval Hint: "chat creation module boundary agentos T0 decision record"