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	17212
title	apps/workstation diverges from the FM style language — census the delta, then align the higher-polish app to the cockpit''s specs
state	Closed
labels	enhancementdesignai
assignees	[]
createdAt	Aug 15, 2026, 10:31 PM
updatedAt	Aug 15, 2026, 10:37 PM
githubUrl	https://github.com/neomjs/neo/issues/17212
author	neo-fable-clio
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Aug 15, 2026, 10:37 PM

apps/workstation diverges from the FM style language — census the delta, then align the higher-polish app to the cockpit's specs

Closed Backlog/active-chunk-16 enhancementdesignai

neo-fable-clio commented on Aug 15, 2026, 10:31 PM

Context

Operator observation (2026-08-15, same UX escalation series): apps/workstation sits at a visibly higher polish level than the cockpit's side panels — but it does NOT match the FM style specs; the two surfaces read as different products. As the cockpit's skin work lands (#17209/#17211), the divergence would otherwise widen.

Verified present: apps/workstation/ (app.mjs, model/, store/, view/, tour/) with its own resources/scss/src/apps/workstation/ (Viewport.scss, Workspace.scss).

Acceptance Criteria

Census first: a style-delta inventory of workstation against the FM style language (tokens, spacing rhythm, header/rail treatments, state colors, typography) — the census names each divergence with its file:selector coordinates and classifies it keep-as-intended / align. The census is a PR-body or ticket-comment artifact BEFORE alignment commits.
Alignment commits per the census dispositions — SCSS token/skin layers only, zero CSS-in-JS; shared tokens preferred over copied values (if a token layer gap forces copying, name it as follow-up rather than duplicating silently).
Both themes verified; no functional/DOM changes ride along (style-only lane).

Out of Scope

Cockpit-side work (#17209/#17210/#17211) · new shared-token architecture (census may PROPOSE it; building it is its own ticket if the delta demands one).

#17209 · #17211 · #13015 (FM umbrella).

Live latest-open sweep: latest 8 checked 2026-08-15T20:2xZ; no equivalent. A2A claim sweep: current-hour window clean.

Origin: operator escalation (session dd4568bd) · Retrieval Hint: "workstation style alignment FM specs census delta tokens"

apps/workstation diverges from the FM style language — census the delta, then align the higher-polish app to the cockpit's specs

Context

Acceptance Criteria

Out of Scope

Related