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	8603
title	VDOM Helper Support for Fragment Indexing & Deltas
state	Closed
labels	aicore
assignees	tobiu
createdAt	Jan 13, 2026, 3:52 PM
updatedAt	Jan 13, 2026, 4:52 PM
githubUrl	https://github.com/neomjs/neo/issues/8603
author	tobiu
commentsCount	1
parentIssue	8601
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 13, 2026, 4:52 PM

VDOM Helper Support for Fragment Indexing & Deltas

Closed v11.21.0/archive-v11-21-0-chunk-1 aicore

tobiu commented on Jan 13, 2026, 3:52 PM

Part of Epic #8601.

Goal: Update src/vdom/Helper.mjs to handle tag: 'fragment' correctly during index calculation and delta generation.

Architectural Decision: We are following a "Smart Runtime / Lean IPC" strategy. The VDOM Helper should NOT "compile away" fragments into individual node operations. Instead, it must generate high-level "Fragment Deltas" (e.g., {action: 'moveNode', id: fragmentId}) and rely on Neo.main.DeltaUpdates to handle the physical DOM range manipulation. This minimizes IPC traffic.

Tasks:

Update getPhysicalIndex:
- Logic must be generalized. Currently, it accounts for text nodes (1 logical = 3 physical).
- It must now account for Fragments (1 logical = N physical, where N is the recursive count of the Fragment's rendered children + anchors).
Update createDeltas:
- Ensure compareAttributes ignores attributes/styles for fragments (or warns).
- Ensure standard diffing logic generates insert/move/remove deltas for the Fragment node itself, not its constituents.

tobiu cross-referenced by #8601 on Jan 13, 2026, 4:17 PM

tobiu Jan 13, 2026, 4:51 PM

Input from Gemini 3 Pro:

✦ I have updated src/vdom/Helper.mjs to support Fragments.

Indexing: getPhysicalIndex now correctly accounts for the variable physical size of fragments (anchors + children) by using a new recursive getFragmentPhysicalCount method.

Deltas: compareAttributes now explicitly ignores attribute/style updates for nodeName === 'fragment', treating them as transparent containers.

Ready for rendering engine updates.