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	8930
title	Epic: DevIndex - The GitHub Meritocracy Index
state	Closed
labels	epicai
assignees	tobiu
createdAt	Feb 1, 2026, 4:19 PM
updatedAt	Feb 23, 2026, 5:12 PM
githubUrl	https://github.com/neomjs/neo/issues/8930
author	tobiu
commentsCount	1
parentIssue	null
subIssues	8931 Feat: DevRank Scaffolding & Data PoC 8932 Feat: DevRank UI - Grid & Controls Implementation 8933 Feat: Discovery Engine Data Enrichment 8934 Feat: DevRank Grid Expansion 8935 Feat: Yearly Breakdown Columns & Heatmap 8936 Fix: RecordFactory mapping logic not triggering for missing source keys 8937 Feat: Discovery Engine - The Spider 8938 Feat: UI Filtering Logic 8939 Feat: Country Flag Column 8940 Feat: Activity Sparkline Column 8941 Feat: Implement Neo.form.field.CountryFlagPicker 8942 Refactor: DevRank Grid Location Column (VDOM + SCSS) 8943 Feat: Interactive Living Sparklines 8944 Feat: Sparkline Pulse Animation 8945 Feat: Sparkline `usePulse` Config 8946 Feat: Sparkline Physics & Visuals 8947 Docs: Sparkline Knowledge Base Enhancement 8957 Fix: Sparkline Pulse Artifact Persistence 8958 Enhancement: Sparkline Scanner Text Positioning 8959 Feat: Implement hideMode for Grid Columns to support OffscreenCanvas buffering 8960 Fix: Vertical scrolling causes OffscreenCanvas loss in Grid cells 8961 Fix: Memory Leak in Neo.component.Canvas due to missing destroy() 8962 Perf: Apply CSS containment to Grid Rows 8963 Feat: Smooth Data Transitions for Sparklines 8997 Feat: DevRank Selection Model Tab 9005 Feat: Refactor Portal Header to Framework (using Dynamic Worker Arch) 9006 Refactor DevRank Controls Button to Header Toolbar 9007 Feat: Enhance DevRank Grid Styling (Dark Theme) 9022 Feat: DevRank Backend Service Architecture 9023 Feat: DevRank User Lifecycle Management 9024 Refactor: Optimize DevRank User Index Storage 9025 Feat: DevRank Data Enrichment (LinkedIn & Orgs) 9026 Chore: Commit DevRank Data Artifacts 9027 Chore: Add DevRank CLI Scripts to package.json 9028 Refactor: DevRank Updater Checkpointing 9029 Feat: DevRank Relevance Threshold 9030 Refactor: DevRank Data Naming Convention & Whitelist 9031 Feat: DevRank Cleanup Service 9032 Feat: DevRank Spider Random Walk Strategy 9033 Refactor: DevRank Spider Checkpointing 9034 Feat: DevRank Grid - LinkedIn & Organizations Columns 9035 Feat: GitHubOrgs Component & Grid Column 9036 Perf: Optimize GitHub Avatar Sizes 9037 Refactor: Dynamic Year Fields in Contributor Model 9038 Style: DevRank Grid Selection Overrides Heatmap 9039 Feat: Support .env token auth for DevRank Services 9040 Refactor: Make DevRank Manager a Singleton 9041 Enhancement: Add Spider Summary Logs 9042 Enhancement: Dynamic High Star Ranges for Spider 9043 Enhancement: DevRank Updater Smart Scheduling & Logs 9044 Fix: DevRank Updater Infinite Loop & Tracker Pruning 9045 Feat: DevRank Active Pruning & Auto-Cleanup 9046 Fix: DevRank Tracker Timestamp Update Logic 9047 Feat: DevRank Whitelist Synchronization & Protection 9048 Feat: DevRank CLI Interactive Prompts (Inquirer) 9049 Docs: Knowledge Base Enhancement for DevRank Services 9054 Perf: Optimize GitHubOrgs with Node Pooling & Visibility 9055 Feat: Configurable renderFullPool for GitHubOrgs Component 9053 Perf: Optimize CountryFlag to Prevent Grid Reflows 9052 Perf: Optimize Sparkline Backpressure & Investigate Grid Reflows 9051 Enhancement: Polish Country Field & Inline Label Support 9050 Perf: Optimize DomAccess.syncAligns to avoid scroll thrashing 9056 Fix: CountryFlag not resetting when value is null 9057 Refactor DevRank Controls: Split Search & Reorder Fields 9058 Feat: DevRank Location Normalizer & Data Enrichment 9059 Optimize & Minify DevRank Data Schema 9062 Fix: Cleanup Service incompatible with minified schema 9063 Perf: Refactor Updater to use Lightweight Contribution Counters 9064 Feat: Implement ''Commits Only'' Toggle for DevRank Grid 9065 Feat: Persist Yearly Commits Array in DevRank Data 9078 Feat: DevRank Heatmap CSS Transitions 9079 Feat: DevRank Header "Show Off" Kinetic Scroll Effect 9080 Perf: DevRank Header Adaptive Backpressure 9081 Feat: DevRank Global Animation Toggle 9082 Refactor Portal Content Viewer to Framework Component 9083 Feat: DevRank GitHub API Rate Limit Protection 9084 Enhancement: DevRank Atomic File Persistence 9085 Feat: DevRank Spider Community Discovery Strategy 9086 Feat: DevRank Spider CLI Strategy Selection 9087 Fix: Broken GitHub Rate Limit Detection and Graceful Exit 9088 Fix: DevRank Spider Premature Exit (Split Core/Search Rate Limits) 9096 Feat: GitHub API Secondary Rate Limit Handling & Concurrency Tuning 9097 Feat: Include Repository Creations in DevRank Contributions 9098 Feat: Integrate Documentation Viewer into DevRank 9099 Fix: Add missing Google Fonts to DevRank index.html 9100 Perf: Remove unused Material Icons from Portal index.html 9103 Fix: DevRank Spider 422 Error on Complex Queries 9104 Refactor: DevRank Folder Structure 9105 Refactor: DevRank Viewport Lazy Loading & Routing
subIssuesCompleted	89
subIssuesTotal	89
blockedBy	[]
blocking	[]
closedAt	Feb 23, 2026, 5:12 PM

Epic: DevIndex - The GitHub Meritocracy Index

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

Closed v12.0.0 epicai

tobiu commented on Feb 1, 2026, 4:19 PM

This epic tracks the development of "DevRank", a Neo.mjs application designed to index and rank GitHub contributors based on their all-time total contributions, irrespective of repository popularity or follower count.

The goal is to create a meritocratic index of the open-source ecosystem, powered by a sophisticated discovery engine ("The Spider") and a high-performance Neo.mjs frontend.

Core Components

Data Pipeline: A Node.js-based discovery engine to fetch, validate, and aggregate user contribution data from the GitHub GraphQL API.
The Index: A local JSON database of contributors, initially populated via "Impact" (Top Repos) and "Network" (Spider) vectors.
The UI: A Neo.mjs application to visualize the index with advanced filtering, sorting, and performance metrics.

Roadmap

Scaffolding & PoC: Initialize the App structure and implement the "Deep Scan" data fetching proof-of-concept.
Discovery Engine: Implement the "Spider" algorithm to expand the contributor graph.
UI Implementation: Build the Grid and Analytics view.
Optimization: Refine data storage and API usage.

tobiu added the epic label on Feb 1, 2026, 4:19 PM

tobiu added the ai label on Feb 1, 2026, 4:19 PM

tobiu added sub-issue #8931 on Feb 1, 2026, 4:20 PM

tobiu added sub-issue #8932 on Feb 1, 2026, 4:26 PM

tobiu added sub-issue #8933 on Feb 1, 2026, 4:38 PM

tobiu added sub-issue #8934 on Feb 1, 2026, 4:38 PM

tobiu added sub-issue #8935 on Feb 1, 2026, 4:59 PM

tobiu added sub-issue #8936 on Feb 1, 2026, 5:25 PM

tobiu added sub-issue #8937 on Feb 1, 2026, 5:43 PM

tobiu added sub-issue #8938 on Feb 1, 2026, 5:43 PM

tobiu added sub-issue #8939 on Feb 1, 2026, 5:44 PM

tobiu added sub-issue #8940 on Feb 1, 2026, 5:44 PM

tobiu added sub-issue #8941 on Feb 1, 2026, 6:31 PM

tobiu added sub-issue #8942 on Feb 1, 2026, 6:59 PM

tobiu added sub-issue #8943 on Feb 2, 2026, 1:26 AM

tobiu assigned to @tobiu on Feb 2, 2026, 1:26 AM

tobiu added sub-issue #8944 on Feb 2, 2026, 1:57 PM

tobiu added sub-issue #8945 on Feb 2, 2026, 2:04 PM

tobiu added sub-issue #8946 on Feb 2, 2026, 2:12 PM

tobiu added sub-issue #8947 on Feb 2, 2026, 2:23 PM

tobiu Feb 3, 2026, 12:03 AM

Input from Gemini 3 Pro:

✦ ### Architectural Update: Generic Sparkline Components

The "Living Sparklines" feature (Issue #8943) triggered a significant architectural improvement that extended beyond the scope of this DevRank application.

We recognized that the "Auto-Initializing Worker" pattern developed for the sparklines was highly reusable. Consequently, we spun off Epic #8948 (Dynamic Worker Architecture) to refactor this logic into the core framework.

Impact on DevRank:

Obsolete Code: apps/devrank/view/SparklineComponent.mjs has been deleted.

Obsolete Code: apps/devrank/canvas/Sparkline.mjs has been moved to src/canvas/Sparkline.mjs.

Refactoring: DevRank.view.GridContainer now uses the generic Neo.grid.column.Sparkline with type: 'sparkline'.

This refactoring means DevRank is now "consuming" the standard framework capability it helped pioneer, rather than maintaining a custom implementation. The original tickets (#8940, #8943) remain valid as the origin story, but the code has moved.

tobiu added sub-issue #8957 on Feb 3, 2026, 11:24 AM

tobiu added sub-issue #8958 on Feb 3, 2026, 11:39 AM

tobiu added sub-issue #8959 on Feb 3, 2026, 1:32 PM

tobiu added sub-issue #8960 on Feb 3, 2026, 1:43 PM

tobiu added sub-issue #8961 on Feb 3, 2026, 2:01 PM

tobiu added sub-issue #8962 on Feb 3, 2026, 2:01 PM

tobiu added sub-issue #8963 on Feb 3, 2026, 2:01 PM

tobiu referenced in commit abe67c3 - "#8930 "neo-theme-neo-dark", "neo-theme-neo-light"" on Feb 4, 2026, 6:21 PM

tobiu added sub-issue #8997 on Feb 5, 2026, 10:31 AM

tobiu added sub-issue #9005 on Feb 5, 2026, 3:51 PM

tobiu added sub-issue #9006 on Feb 5, 2026, 6:44 PM

tobiu added sub-issue #9007 on Feb 5, 2026, 8:32 PM

tobiu added sub-issue #9022 on Feb 7, 2026, 5:18 PM

tobiu added sub-issue #9023 on Feb 7, 2026, 5:18 PM

tobiu added sub-issue #9024 on Feb 7, 2026, 5:31 PM

tobiu added sub-issue #9025 on Feb 7, 2026, 5:34 PM

tobiu added sub-issue #9026 on Feb 7, 2026, 5:49 PM

tobiu added sub-issue #9027 on Feb 7, 2026, 7:07 PM

tobiu added sub-issue #9028 on Feb 7, 2026, 7:11 PM

tobiu added sub-issue #9029 on Feb 7, 2026, 7:17 PM

tobiu added sub-issue #9030 on Feb 7, 2026, 7:20 PM

tobiu added sub-issue #9031 on Feb 7, 2026, 7:31 PM

tobiu added sub-issue #9032 on Feb 7, 2026, 7:44 PM

tobiu added sub-issue #9033 on Feb 7, 2026, 8:01 PM

tobiu added sub-issue #9034 on Feb 7, 2026, 8:26 PM

tobiu added sub-issue #9035 on Feb 7, 2026, 8:39 PM

tobiu added sub-issue #9036 on Feb 7, 2026, 8:48 PM

tobiu added sub-issue #9037 on Feb 7, 2026, 8:58 PM

tobiu added sub-issue #9038 on Feb 7, 2026, 9:08 PM