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

Neutralize the portal offscreen renderer into a shared TimelineCanvas

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 1). The offscreen "Neural Timeline" renderer is behaviorally content-agnostic but named for tickets; the PR + Discussion views will reuse it as-is.

The Fix

Rename Portal.canvas.TicketCanvas → a neutral TimelineCanvas (or relocate to src/canvas/Timeline.mjs — it has zero portal deps and already extends src/canvas/Base.mjs): update className + JSDoc, Helper.importTicketCanvas → importTimelineCanvas (one method, reused by all three types), and the two rendererClassName/rendererImportPath identity strings in the view bridge. Pure rename, zero behavior change. Confirm the single shared singleton is safe across content tabs (tabs unmount on switch — TabContainer unmountConfigs activeIndex:null).

Architectural Reality

apps/portal/canvas/TicketCanvas.mjs:54 (className), :207-224 (updateGraphData consumes only {nodes,startY,reset}), :236-420 (draw loop reads only node.x/y/radius/color). No issue semantics in the renderer.

Acceptance Criteria

Existing Tickets tab renders visually unchanged.
Renderer carries no "Ticket"-specific identity (className/JSDoc/import method neutral).

Out of Scope

Per-type node-decoration variants (only if PR/Discussion later need different pulse visuals).

Epic #12207. First foundation step (unblocks the view-glue promotion).

tobiu referenced in commit ec32b96 - "refactor(portal): neutralize the offscreen renderer to a shared TimelineCanvas (#12205) (#12221) on May 30, 2026, 8:13 PM

tobiu closed this issue on May 30, 2026, 8:13 PM