What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	8658
title	Docs: Create ''Neural Timeline'' Architecture Guide
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Jan 15, 2026, 12:41 AM
updatedAt	Jan 15, 2026, 12:50 AM
githubUrl	https://github.com/neomjs/neo/issues/8658
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 15, 2026, 12:50 AM

Docs: Create 'Neural Timeline' Architecture Guide

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closed v11.22.0 documentationai

tobiu commented on Jan 15, 2026, 12:41 AM

We are creating a new technical guide to document the "Neural Timeline" implementation.

Goal: Document the advanced "Coordinator Pattern" used to synchronize DOM elements (App Worker) with a physics-based Canvas visualization (Shared Worker).

Content Strategy:

The Coordinator Pattern: Explain how TimelineCanvas.mjs (App Worker) acts as the "eyes" for the blind TicketCanvas.mjs (Shared Worker) by translating DOMRects into canvas coordinates.
Physics Engine: Deep dive into the "Traffic Model" physics (acceleration/deceleration based on node proximity) and the "Squash & Stretch" visual effects.
Data-Driven Visuals: Explain the "Chameleon Pulse" effect, where the animation color interpolates based on the semantic state of the nearest ticket (e.g., Red for Bugs).
Optimization: Document the "Zombie Loop" prevention strategy (unmount cleanup) and the efficient use of ResizeObserver.

Deliverables:

New guide file: learn/guides/advanced/NeuralTimeline.md.
Update learn/tree.json to include the new guide under the "Advanced Architecture" section.

tobiu added the documentation label on Jan 15, 2026, 12:41 AM

tobiu added the ai label on Jan 15, 2026, 12:41 AM

tobiu assigned to @tobiu on Jan 15, 2026, 12:50 AM

tobiu referenced in commit 89c9773 - "docs: Add Neural Timeline guide and enhance Canvas Architecture guide (#8658)" on Jan 15, 2026, 12:50 AM

tobiu Jan 15, 2026, 12:50 AM

Input from Gemini 3 Pro:

✦ I have created the "Neural Timeline (App Worker Coordination)" guide. It covers:

Architecture: The Coordinator Pattern (App Worker as "eyes", Shared Worker as "renderer").

Physics: Traffic Model and Squash & Stretch effects.

Data-Driven Visuals: Chameleon Pulse effect.

Optimization: Zombie Loop defense.

The guide is located at learn/guides/advanced/NeuralTimeline.md. I also enhanced the CanvasArchitecture.md guide with detailed physics explanations and code snippets. Both guides have been added to learn/tree.json under the new "Advanced Architecture" section.

tobiu closed this issue on Jan 15, 2026, 12:50 AM