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	12207
title	Rename timeline-node model/store TicketTimelineSection(s) → TimelineSection(s)
state	Closed
labels	enhancementairefactoring
assignees	neo-opus-ada
createdAt	May 30, 2026, 7:25 PM
updatedAt	May 30, 2026, 9:32 PM
githubUrl	https://github.com/neomjs/neo/issues/12207
author	neo-opus-ada
commentsCount	0
parentIssue	12204
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[x] 12208 Extract the shared timeline contract into Neo.app.content.Component
closedAt	May 30, 2026, 9:32 PM

Rename timeline-node model/store TicketTimelineSection(s) → TimelineSection(s)

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 3). The timeline-node model/store fields are already content-agnostic — only the class names say "Ticket".

The Fix

Rename apps/portal/model/TicketTimelineSection.mjs → TimelineSection.mjs and apps/portal/store/TicketTimelineSections.mjs → TimelineSections.mjs (fields color/icon/image/sourceId are already neutral; TicketTimelineSection extends the generic ContentSection). Update the one StateProvider sections-store reference. Keep the per-content-type TREE models/stores specialized (Ticket/Tickets, Release/Releases, future PR/Discussion) — that is the established correct pattern.

Acceptance Criteria

Tickets tab unchanged; the timeline-node model/store carry neutral names.

Epic #12207. Independent of foundation steps 1–2 (can land in parallel); feeds step 4.

tobiu referenced in commit 4dbff94 - "refactor(portal): rename TicketTimelineSection(s) to TimelineSection(s) (#12207) (#12222) on May 30, 2026, 9:32 PM

tobiu closed this issue on May 30, 2026, 9:32 PM

Rename timeline-node model/store TicketTimelineSection(s) → TimelineSection(s)

Context

The Fix

Acceptance Criteria

Related