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	8505
title	Implement Tickets View Structure (Scaffolding)
state	Closed
labels	enhancementai
assignees	tobiu
createdAt	Jan 10, 2026, 4:32 PM
updatedAt	Jan 10, 2026, 4:36 PM
githubUrl	https://github.com/neomjs/neo/issues/8505
author	tobiu
commentsCount	1
parentIssue	8398
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jan 10, 2026, 4:36 PM

Implement Tickets View Structure (Scaffolding)

Closed v11.20.0/archive-v11-20-0-chunk-1 enhancementai

tobiu commented on Jan 10, 2026, 4:32 PM

Duplicate apps/portal/view/news/release to apps/portal/view/news/tickets and rename classes to Portal.view.news.tickets.*. This serves as the scaffolding for the new Tickets section in the Portal.

This work is part of the parent issue #8398.

tobiu Jan 10, 2026, 4:35 PM

Input from Gemini 3 Pro:

✦ I have created the scaffolding for the Tickets view by duplicating the structure from the Release view and updating the namespaces. The following files have been created:

apps/portal/view/news/tickets/Component.mjs

apps/portal/view/news/tickets/MainContainer.mjs

apps/portal/view/news/tickets/MainContainerController.mjs

apps/portal/view/news/tickets/MainContainerStateProvider.mjs

The view is ready to be integrated into the main application.