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	9577
title	Draft Release Notes: Storytelling & Narrative Arc
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Mar 27, 2026, 12:15 PM
updatedAt	Mar 27, 2026, 12:29 PM
githubUrl	https://github.com/neomjs/neo/issues/9577
author	tobiu
commentsCount	2
parentIssue	9569
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 27, 2026, 12:25 PM

Draft Release Notes: Storytelling & Narrative Arc

Closed v12.1.0/archive-v12-1-0-chunk-3 documentationai

tobiu commented on Mar 27, 2026, 12:15 PM

This sub-task focuses on refining the v12.1.0 release notes from a technical draft into a cohesive, high-impact narrative.

References

Analyze the storytelling, tone, and pacing of previous major architectural releases:

resources/content/release-notes/v12.0.0.md
resources/content/release-notes/v11.24.0.md
resources/content/release-notes/v11.23.0.md
resources/content/release-notes/v11.22.0.md

Objectives for the Next Session

Analyze: Read the reference .md files to internalize the desired Neo.mjs narrative style.
Review: Read the current technical draft of resources/content/release-notes/v12.1.0.md.
Elevate: Overhaul the transitions, headers, formatting, and tone to build a cohesive story connecting the major architectural leaps (TreeStore, Data Pipelines, Locked Columns, ScrollSync, MCP Security).

tobiu Mar 27, 2026, 12:25 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ The v12.1.0 release notes have been systematically elevated to match the bold, narrative-driven quality of previous major releases like v12.0.0.

The Cyborg Factor Continues: Inserted a new section immediately after the TL;DR to spotlight the 178-ticket / 22-day velocity. Brought in the TreeStore "Split-Brain" fix as a concrete example of the AI actively co-architecting and solving non-trivial bugs.

TreeStore & Data Pipelines: Refined the narrative tone, adding emphasis on O(1) nested rendering without massive VDOM overhead.

Locked Columns (The Compositor Challenge): Redesigned the "Known Limitation" block into an uncompromising engineering thesis on why exactly single-thread architectures fail under horizontal pressure, framing Epic #9486 as our decisive next step.

AI Agent OS & MCP Networking: Positioned this section natively as a massive core capability (SSE transport, OIDC/OAuth 2.1 Security Anchor) leading directly into the Learning Guides conclusion.

All changes have been successfully committed and pushed to the repository.

tobiu Mar 27, 2026, 12:29 PM

Input from Gemini 3.1 Pro (Antigravity):

✦ You are absolutely right. "Velocity Case Study" undersold the monumental engineering effort required for features like the TreeGrid.

I have pushed a follow-up commit that completely reframes the narrative:

Renamed all "Velocity Case Studies" to "Architectural Leaps" (e.g., Architectural Leap 1: The TreeStore & Data Pipeline Evolution).

Rewrote the TreeStore Architecture bullet points. I specifically documented the Dual-Layer Architecture (Structural Layer vs Projection Layer), the O(1) mathematical memory mapping, and how the top-down recursive Ancestor-Aware Filtering perfectly integrates with "Turbo Mode Soft Hydration". The text now explicitly reflects the incredible computational complexity of TreeStore.mjs.

2026-06-08T04:49:29Z @neo-gpt cross-referenced by #12734