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	12208
title	Extract the shared timeline contract into Neo.app.content.Component
state	Closed
labels	enhancementairefactoring
assignees	neo-opus-ada
createdAt	May 30, 2026, 7:25 PM
updatedAt	May 31, 2026, 12:29 AM
githubUrl	https://github.com/neomjs/neo/issues/12208
author	neo-opus-ada
commentsCount	0
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[x] 12207 Rename timeline-node model/store TicketTimelineSection(s) → TimelineSection(s), [x] 12206 Promote portal canvas view-glue (bridge + CanvasWrapper) to shared
blocking	[x] 12209 Make portal content cross-link URLs per-content-type config
closedAt	May 31, 2026, 12:29 AM

Extract the shared timeline contract into Neo.app.content.Component

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

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

Context

Part of epic #12207 (foundation step 4). The per-type parsers (issue/PR/discussion) share scaffolding that belongs in the framework Component so each type only supplies its parser.

The Fix

Lift the SHARED scaffolding up into Neo.app.content.Component (or a TimelineContent base/mixin): the timeline-item / comment-item / body-item HTML templates, formatTimestamp, the sections-store push, and the IntersectionObserver wiring (it targets .neo-timeline-item[data-record-id] generically). Keep the issue-specific renderTimeline line-walker + the event-type/label/commit machinery in apps/portal/view/news/tickets/Component.mjs as the Issue specialization.

Architectural Reality

tickets/Component.mjs:271-402 (modifyMarkdown pipeline), :425-584 (renderTimeline), :479-489 (issue event-type table). The shared seam is the OUTPUT contract — all parsers emit the same {id, image|color, icon, name, tag} nodes + .neo-timeline-item HTML; the canvas never parses markdown.

Acceptance Criteria

Tickets tab unchanged.
A new content type can subclass the shared Component and supply only a modifyMarkdown/renderTimeline parser.

Epic #12207. Depends on foundation steps 2 + 3; unblocks the per-type views (7, 8) and step 5.

tobiu referenced in commit 1b9b684 - "refactor(portal): extract Portal.view.content.Component timeline base (#12208) (#12233) on May 31, 2026, 12:29 AM

tobiu closed this issue on May 31, 2026, 12:29 AM