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	9093
title	Refactor: DevRank Backend JSONL Persistence
state	Closed
labels	airefactoring
assignees	tobiu
createdAt	Feb 10, 2026, 7:05 PM
updatedAt	Feb 10, 2026, 7:51 PM
githubUrl	https://github.com/neomjs/neo/issues/9093
author	tobiu
commentsCount	1
parentIssue	9089
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Feb 10, 2026, 7:51 PM

Refactor: DevRank Backend JSONL Persistence

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

Closed v12.0.0 airefactoring

tobiu commented on Feb 10, 2026, 7:05 PM

Objective

Ensure the DevRank backend (Spider/Updater/Storage) natively supports the .jsonl format to maintain data integrity with the new Streaming Proxy architecture.

Rationale

Since we are migrating users.json to users.jsonl for performance (Epic #9089), the backend services must stop writing to the old JSON file. The Updater runs frequently, so any one-off conversion script will quickly become outdated. The backend itself must be the source of truth for JSONL.

Tasks

Refactor Storage.mjs:
- Implement readJSONL(path) and writeJSONL(path, items).
- Update updateUsers(newUsers) to append/rewrite in JSONL format.
- Ensure atomic writes (write to .tmp, rename) are preserved for JSONL.
Refactor Updater.mjs:
- Ensure it passes data compatible with the new storage methods (it likely already does, but verification is needed).
Migration Script (Final):
- A final, authoritative script to convert the latest users.json to users.jsonl and delete the old file (or archive it).

Dependencies

Blocked by #9090 and #9091 (Core Support).
Must be coordinated with #9092 (Frontend Switch) to avoid downtime.

tobiu added the ai label on Feb 10, 2026, 7:05 PM

tobiu added the refactoring label on Feb 10, 2026, 7:05 PM

tobiu added parent issue #9089 on Feb 10, 2026, 7:05 PM

tobiu assigned to @tobiu on Feb 10, 2026, 7:08 PM

tobiu referenced in commit 21abc63 - "refactor: Migrate DevRank to JSONL persistence and Streaming Proxy (#9093, #9092)" on Feb 10, 2026, 7:50 PM

tobiu Feb 10, 2026, 7:50 PM

Input from Gemini 3 Pro:

✦ I have successfully migrated the DevRank backend to use JSONL.

Changes

Storage.mjs: Updated readJson and writeJson to natively support .jsonl files (newline-delimited JSON). Added logic to detect the extension and switch parsing/serialization strategies.

config.mjs: Updated paths.users to point to users.jsonl.

Migration Script: Created and ran apps/devrank/services/migrateJsonToJsonl.mjs which successfully converted the existing 11k+ records to the new format and deleted the legacy file.

Verification

The migration script verified the record count (11043) match.

Storage logic for users.json legacy fallback remains (though unused by config).

This completes the backend persistence requirements.

tobiu closed this issue on Feb 10, 2026, 7:51 PM