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	9105
title	Refactor: DevRank Viewport Lazy Loading & Routing
state	Closed
labels	airefactoringperformance
assignees	tobiu
createdAt	Feb 11, 2026, 11:23 PM
updatedAt	Feb 11, 2026, 11:58 PM
githubUrl	https://github.com/neomjs/neo/issues/9105
author	tobiu
commentsCount	1
parentIssue	8930
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Feb 11, 2026, 11:58 PM

Refactor: DevRank Viewport Lazy Loading & Routing

Closed v12.0.0/archive-v12-0-0-chunk-2 airefactoringperformance

tobiu commented on Feb 11, 2026, 11:23 PM

Refactor DevRank Viewport for lazy loading and better routing architecture.

Tasks:

Create apps/devrank/view/home/MainContainer.mjs to encapsulate the Home view (Grid + Controls).
Update apps/devrank/view/Viewport.mjs:
- Use lazy loading (module: () => import(...)) for Home and Learn views.
- Remove activeIndex: 0 to allow the controller to handle routing.
Update apps/devrank/view/ViewportController.mjs:
- Add defaultHash: '/home'.

Reason: To improve initial load time and align with the Portal architecture.

tobiu Feb 11, 2026, 11:58 PM

Input from Gemini 3 Pro:

✦ I have successfully refactored the DevRank.view.Viewport for lazy loading and routing, and fixed a critical race condition in Neo.app.content.TreeList.

Changes:

Lazy Loading: Created apps/devrank/view/home/MainContainer.mjs and updated Viewport.mjs to use module: () => import(...) for both Home and Learn views.

Routing Fix: Set activeIndex: null in Viewport card layout and removed mainContentLayouts from ViewportController, allowing the controller to handle initial routing via defaultHash.

Race Condition Fix (TreeList): Updated src/app/content/TreeList.mjs to:

Check for Neo.isFunction(this.store?.load) in doLoadStore to prevent crashes when the store is not yet initialized.

Trigger doLoadStore in afterSetStore if contentPath is already set, ensuring the store loads even if the path was set before the store binding completed.

This ensures robust initialization and prevents double loading in other app sections (like Portal Releases) by checking this.contentPath before auto-loading in afterSetStore.