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	12206
title	Promote portal canvas view-glue (bridge + CanvasWrapper) to shared
state	Closed
labels	enhancementairefactoring
assignees	neo-opus-ada
createdAt	May 30, 2026, 7:24 PM
updatedAt	May 30, 2026, 11:03 PM
githubUrl	https://github.com/neomjs/neo/issues/12206
author	neo-opus-ada
commentsCount	0
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 12205 Neutralize the portal offscreen renderer into a shared TimelineCanvas
blocking	[x] 12208 Extract the shared timeline contract into Neo.app.content.Component
closedAt	May 30, 2026, 11:03 PM

Promote portal canvas view-glue (bridge + CanvasWrapper) to shared

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementairefactoring

neo-opus-ada commented on May 30, 2026, 7:24 PM

Context

Part of epic #12207 (foundation step 2). The canvas bridge + wrapper are per-tickets today; PR/Discussion views need the same glue.

The Fix

Relocate apps/portal/view/news/tickets/TimelineCanvas.mjs (the App-worker bridge that measures DOM rects) + tickets/CanvasWrapper.mjs to a shared namespace; parameterize contentComponent per type via the existing contentComponent config seam (its only per-type coupling is two hardcoded imports). Generalize the shared cls neo-ticket-timeline-wrapper → neo-timeline-wrapper; per-type prefixes (e.g. portal-news-tickets-*) stay.

Acceptance Criteria

Tickets tab unchanged; the bridge + wrapper are reusable across content types via config.
The sections store key + .neo-timeline-item[data-record-id] selector are left untouched (canvas bridge contract).

Epic #12207. Depends on the renderer-neutralization step (foundation 1).

tobiu closed this issue on May 30, 2026, 11:03 PM

tobiu referenced in commit 6ee699b - "refactor(portal): promote canvas glue to shared Portal.view.content (#12206) (#12224) on May 30, 2026, 11:03 PM

Promote portal canvas view-glue (bridge + CanvasWrapper) to shared

Context

The Fix

Acceptance Criteria

Related