What is the 'Neural Link'?

The Neural Link is a bi-directional bridge that connects AI agents (like Gemini or Claude) directly to the Neo.mjs runtime. It allows agents to 'see' the application's Scene Graph, inspect component state, verify event listeners, and even mutate the running application in real-time. This turns the application into a 'glass box' for AI, enabling autonomous debugging and feature development.

Why is Neo.mjs called an 'Application Engine' instead of a framework?

Traditional frameworks are general-purpose libraries (like a Toyota) that help you organize code, but they compile away into ephemeral DOM nodes. Neo.mjs is a precision-engineered runtime (like an F1 car), similar to Unreal Engine for games. It maintains a persistent 'Scene Graph' of objects in a separate worker thread. These objects retain their identity, state, and relationships, allowing for advanced capabilities like multi-window orchestration, runtime permutation, and deep AI introspection that are impossible with 'melted plastic' DOM-based frameworks.

What is 'Context Engineering'?

Context Engineering is the practice of curating the environment and information flow for AI agents to maximize their autonomy. In Neo.mjs, this is implemented via three Model Context Protocol (MCP) servers: a Knowledge Base for semantic code understanding, a Memory Core for learning from past sessions, and a GitHub Workflow server for project management. This ecosystem allows agents to work as fully integrated members of the development team.

What is 'Object Permanence' in the context of Neo.mjs?

In Neo.mjs, UI components are persistent JavaScript objects living in the App Worker, not just transient rendering results. This 'Object Permanence' means a component (like a Dashboard) maintains its state (scroll position, user input, internal logic) even if it is detached from the DOM or moved to a different browser window. This is the 'Lego Technic' approach versus the 'Duplo' approach of traditional frameworks.

What is an 'Agent Operating System'?

Neo.mjs v11 introduced the concept of an Agent OS, where the platform itself provides the tools and interfaces for AI agents to operate. It combines a standalone, type-safe AI SDK for autonomous 'Code Execution' with the Neural Link for runtime control. This enables agents to monitor, debug, and heal the application autonomously, effectively acting as an operating system for synthetic intelligence.

How does Neo.mjs handle multi-window applications?

Neo.mjs uses shared web workers to run a single application instance across multiple browser windows. All windows share the same application state and data in real-time. Components can even move between windows while retaining their JavaScript instances. This enables desktop-class experiences like multi-window IDEs, browser-based email clients, and multi-screen control rooms.

What makes Neo.mjs different from React, Angular, or Vue?

Neo.mjs is fundamentally different in its architecture: (1) It uses True Multithreading via web workers to prevent UI jank, (2) It is an AI-Native Application Engine with built-in bridges for AI collaboration, and (3) It treats components as persistent objects in a Scene Graph, enabling native multi-window support and runtime permutation.

Frontmatter

id	9869
title	Unified Data Sync Pipeline (DevIndex, Portal Indexes, and SEO)
state	Closed
labels	enhancementaibuild
assignees	[]
createdAt	Apr 10, 2026, 7:32 PM
updatedAt	Apr 10, 2026, 7:35 PM
githubUrl	https://github.com/neomjs/neo/issues/9869
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 10, 2026, 7:35 PM

Unified Data Sync Pipeline (DevIndex, Portal Indexes, and SEO)

Name: Neo.mjs Application Engine
Author: Neo.mjs

Closedenhancementaibuild

tobiu commented on Apr 10, 2026, 7:32 PM

Overview

The DevIndex automation pipeline originally only scraped opt-in/opt-out statuses and generated the users.jsonl output. However, the neomjs/portal application relies on an array of generated indices (tickets.json, labels.json, releases.json) and raw Markdown ticket content (resources/content/issues and issue-archive) to natively render live tracking without needing a full framework version bump. Additionally, SEO files like sitemap.xml and llms.txt should represent the live state of the site.

Task

Rename and harden the existing devindex-pipeline.yml into a fully unified data-sync-pipeline.yml.

Architecture Additions:

Rebuild Indexes & SEO: Automatically loop in buildScripts/docs/index/*.mjs and buildScripts/docs/seo/generate.mjs to keep our knowledge index and LLM map fresh.
Content Synchronization: Ensure the raw markdown ticket contents (issues, issue-archive) are correctly copied to the neomjs/pages GitHub Pages root so that the Portal Ticket Explorer does not hit a 404 when querying newly created tickets.
Atomicity: The pipeline will commit all locally generated indexes to the neo repo, and propagate them symmetrically to neomjs/pages via a single bot push.

Avoided Pitfalls

Using cp -r for resources/content/* initially poses a problem since a ticket moving from issues to issue-archive would not be natively deleted in temp_pages. We avoid ghost collisions by running a clean rm -rf on the target directories inside the clone, copying fresh, and using git add -A node_modules/neo.mjs/resources/content/ to let git natively resolve diffs and deletions.

tobiu added the enhancement label on Apr 10, 2026, 7:32 PM

tobiu added the ai label on Apr 10, 2026, 7:32 PM

tobiu added the build label on Apr 10, 2026, 7:32 PM

tobiu referenced in commit 07e8572 - "feat: Unified Data Sync Pipeline (#9869)" on Apr 10, 2026, 7:32 PM

tobiu cross-referenced by PR #9870 on Apr 10, 2026, 7:32 PM

tobiu referenced in commit a7e9b73 - "feat: Unified Data Sync Pipeline (#9869) (#9870)" on Apr 10, 2026, 7:35 PM

tobiu closed this issue on Apr 10, 2026, 7:35 PM