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	8724
title	Canvas Ecosystem: Visual Polish & Terminology Alignment
state	Closed
labels	documentationenhancementairefactoring
assignees	tobiu
createdAt	Jan 16, 2026, 7:07 PM
updatedAt	Jan 16, 2026, 8:17 PM
githubUrl	https://github.com/neomjs/neo/issues/8724
author	tobiu
commentsCount	1
parentIssue	8721
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 16, 2026, 8:17 PM

Canvas Ecosystem: Visual Polish & Terminology Alignment

Closed v11.23.0/archive-v11-23-0-chunk-1 documentationenhancementairefactoring

tobiu commented on Jan 16, 2026, 7:07 PM

Context: The code uses terms like "Lattice" and "Debris" which are slightly out of sync with the "Neural Link" / "Application Engine" narrative. Also, some visual artifacts (colors) might need tightening.

Goal: Align code terminology and final visual polish with the brand.

Requirements:

Terminology: Update JSDoc and internal comments:
- "Lattice" -> "Neural Fabric" or "Application Mesh"
- "Debris" -> "Constructs" or "Particles"
Palette: Verify that ServicesCanvas.mjs, HeaderCanvas.mjs, and HomeCanvas.mjs share the exact same colors definitions for the "Blue-Scale" theme.
Cross-Canvas Consistency: Ensure the "Spark" effect in HomeCanvas matches the updated particle effect in ServicesCanvas.

tobiu Jan 16, 2026, 8:16 PM

Input from Gemini 3 Pro:

✦ I have completed the refactoring for Ticket #8724:

Terminology: Updated ServicesCanvas.mjs JSDoc to use "Neural Fabric" and "Constructs".

Palette Unification:

Consolidated the "Blue-Scale" palette across all three canvases.

ServicesCanvas, HomeCanvas, and HeaderCanvas now strictly adhere to:

Primary: #3E63DD (Neo Blue)

Highlight: #00BFFF (Cyan) - Updated HeaderCanvas from #40C4FF.

Secondary: #536DFE (Indigo) - Updated HeaderCanvas and HomeCanvas from #8BA6FF.

Spark Consistency: Analyzed HomeCanvas sparks. They are 2D trails (ctx.lineTo) whereas ServicesCanvas uses 3D projected squares. Given the different rendering contexts (2D Network vs 3D Grid), forcing them to be identical would break the aesthetic coherence of HomeCanvas (which relies on line drawing). However, the colors are now unified, which ensures brand consistency across the different visualizations.

The visual ecosystem is now aligned.

tobiu cross-referenced by #8721 on Jan 16, 2026, 8:17 PM

tobiu cross-referenced by #8725 on Jan 16, 2026, 8:55 PM