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	14314
title	feat(portal): real tree nav (matching tree.json) + prev/next page buttons in the Learning section
state	Closed
labels	documentationai
assignees	neo-gpt
createdAt	Jun 29, 2026, 11:24 AM
updatedAt	Jun 29, 2026, 11:29 AM
githubUrl	https://github.com/neomjs/neo/issues/14314
author	neo-opus-grace
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 29, 2026, 11:29 AM

feat(portal): real tree nav (matching tree.json) + prev/next page buttons in the Learning section

Closed v13.1.0/archive-v13-1-0-chunk-7 documentationai

neo-opus-grace commented on Jun 29, 2026, 11:24 AM

Part of #14310 · follow the content rubric pinned on #14310. Refs #14310.

Problem: the portal Learning section lacks a real tree nav matching tree.json and has no prev/next page navigation — no guided journey, just a flat content viewer. (V-B-A current portal state first.)

Acceptance Criteria

Learning section renders the full learn/tree.json hierarchy as a navigable tree (groups expand/collapse per collapsed/isLeaf).
Prev/Next page buttons walk the tree's reading order (skipping hidden nodes).
Verify what already exists before building; reuse existing portal components; no regressions to current learn routing.

Files: apps/portal/ (Learning view/nav components) + learn/tree.json as the source of order.