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	8628
title	[Docs] Apply Knowledge Base Enhancement Strategy to Fragment Implementation
state	Closed
labels	documentationaicore
assignees	tobiu
createdAt	Jan 14, 2026, 2:14 AM
updatedAt	Jan 14, 2026, 2:21 AM
githubUrl	https://github.com/neomjs/neo/issues/8628
author	tobiu
commentsCount	1
parentIssue	8601
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jan 14, 2026, 2:21 AM

[Docs] Apply Knowledge Base Enhancement Strategy to Fragment Implementation

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

Closed v11.21.0 documentationaicore

tobiu commented on Jan 14, 2026, 2:14 AM

Apply the 3.2. Knowledge Base Enhancement Strategy (from AGENTS_STARTUP.md) to the artifacts produced by Epic #8601.

Goal: Ensure the new Fragment architecture is fully discoverable and semantically indexed by the AI Knowledge Base.

Scope: Review and enhance JSDoc comments for:

src/container/Fragment.mjs
- Add @summary and detailed architectural context.
- Add "semantic signposts" (e.g., "wrapperless grouping", "phantom container").
src/vdom/Helper.mjs
- Document the indexing logic (1 logical = N physical).
src/main/DeltaUpdates.mjs
- Document the "Fragment Deltas" strategy in insertNode, moveNode, removeNode.
src/container/Base.mjs
- Document the atomic move logic in insert and remove.

Requirements:

Use intent-driven comments (WHY, not just WHAT).
Add @see links to relevant tests and the example app.
Ensure @summary tags are present on modified classes/methods.

tobiu added the documentation label on Jan 14, 2026, 2:14 AM

tobiu added the ai label on Jan 14, 2026, 2:14 AM

tobiu added the core label on Jan 14, 2026, 2:14 AM

tobiu added parent issue #8601 on Jan 14, 2026, 2:14 AM

tobiu assigned to @tobiu on Jan 14, 2026, 2:20 AM

tobiu Jan 14, 2026, 2:21 AM

Input from Gemini 3 Pro:

✦ I have enhanced the JSDoc documentation for the Fragment implementation across the codebase, applying the Knowledge Base Enhancement Strategy.

Changes:

src/container/Fragment.mjs:

Added a comprehensive @summary.

Explained "Wrapperless Rendering" and "Layout Participation".

Added semantic signposts: "Phantom Node", "Ghost Container", "Transparent Container".

Added @see links to Neo.vdom.Helper and the reference example Neo.examples.container.fragment.MainContainer.

src/vdom/Helper.mjs:

compareAttributes: Explained the "transparency" optimization (ignoring attributes).

getFragmentPhysicalCount: Documented the 2 (anchors) + children formula.

getPhysicalIndex: Explained the mapping between logical (1 item) and physical (N nodes) indices.

src/main/DeltaUpdates.mjs:

moveNode: Documented the "Atomic Move" logic (using moveBefore) and the Fragment fallback (range extraction via XPath).

Added context to helper methods getFragmentStart, getFragmentSibling, and getFragmentNodes.

src/container/Base.mjs:

removeAt: Documented the critical keepMounted parameter for preserving component state during atomic moves.

These updates ensure that the AI Knowledge Base can now semantically understand and retrieve information about the Fragment architecture, including why it works the way it does.

tobiu closed this issue on Jan 14, 2026, 2:21 AM