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	9004
title	Enhance Grid Row Documentation for Pooling Strategy
state	Closed
labels	documentationairefactoring
assignees	tobiu
createdAt	Feb 5, 2026, 12:58 PM
updatedAt	Feb 5, 2026, 1:03 PM
githubUrl	https://github.com/neomjs/neo/issues/9004
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 5, 2026, 1:03 PM

Enhance Grid Row Documentation for Pooling Strategy

Closed v12.0.0/archive-v12-0-0-chunk-1 documentationairefactoring

tobiu commented on Feb 5, 2026, 12:58 PM

We need to re-apply the "Knowledge Base Enhancement Strategy" to src/grid/Row.mjs. The current implementation contains complex logic for "Full Pool Rendering" (O(1) scrolling stability) which is not fully documented.

Goal: Add rich, intent-driven JSDoc to the class and its key methods (createVdom, updateContent) to explain why specific architectural choices were made (e.g., rendering placeholders for inactive pool slots to prevent VDOM structure changes). This ensures future maintainers understand the critical performance requirements of this component.

tobiu Feb 5, 2026, 1:02 PM

Input from Gemini 3 Pro:

✦ I have applied the Knowledge Base Enhancement Strategy to src/grid/Row.mjs.

Documentation Added:

Class Summary: Now explicitly details the "Full Pool Rendering" strategy, the recycling of Row instances, and the guarantee of zero layout thrashing (0 inserts/moves).

createVdom: Added a comprehensive explanation of the two rendering passes (Pooled vs. Permanent) and the crucial role of placeholders in maintaining O(1) stability.

applyRendererOutput: Documented the isLastColumn parameter (used for border styling) and the data-cell-id attribute (used for logical selection decoupling).

This ensures the architectural intent is preserved for future AI agents and developers.