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	8389
title	Implement Releases Section using Shared Content View
state	Closed
labels	documentation
assignees	tobiu
createdAt	Jan 7, 2026, 4:59 PM
updatedAt	Jan 7, 2026, 11:19 PM
githubUrl	https://github.com/neomjs/neo/issues/8389
author	tobiu
commentsCount	0
parentIssue	8362
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 7, 2026, 11:19 PM

Implement Releases Section using Shared Content View

Closed v11.19.0/archive-v11-19-0-chunk-1 documentation

tobiu commented on Jan 7, 2026, 4:59 PM

Implement the "Releases" section in the Portal using the newly refactored shared content components.

Goal: Display release notes in the Portal using the same "Tree Nav + Content + Sections List" layout as the "Learn" section.

Scope:

Stores:
- Create apps/portal/store/Releases.mjs to fetch and manage the tree of release versions (likely from a releases.json index).
- Reuse or extend apps/portal/store/ContentSections.mjs for the right-hand sidebar.
View Construction:
- Create apps/portal/view/release/MainContainer.mjs extending apps/portal/view/shared/content/Container.mjs.
- Create apps/portal/view/release/MainContainerController.mjs.
- Create apps/portal/view/release/MainContainerStateProvider.mjs.
Wiring:
- In MainContainerStateProvider, map the generic tree store key to apps/portal/store/Releases.mjs.
- Map the generic sections store key to the section store.
Integration:
- Update apps/portal/view/news/TabContainer.mjs (or equivalent) to replace the "Releases" placeholder with the new MainContainer.
Routing:
- Configure the controller to handle /news/releases/{version} routes.

Dependencies:

Depends on the completion of #8388 (Refactor Learn).