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	7089
title	Refactor Component Base Classes into a Common Abstract Class
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Jul 21, 2025, 1:59 PM
updatedAt	Jul 22, 2025, 12:22 AM
githubUrl	https://github.com/neomjs/neo/issues/7089
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jul 22, 2025, 12:22 AM

Refactor Component Base Classes into a Common Abstract Class

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

Closed v10.0.0 enhancement

tobiu commented on Jul 21, 2025, 1:59 PM

Summary

This ticket tracks the architectural refactoring to create a new common base class, Neo.component.Abstract, for both classic (Neo.component.Base) and functional (Neo.functional.component.Base) components.

Motivation

The component architecture previously had two separate base classes that, while using mixins, still contained a significant amount of duplicated code for lifecycle management, configuration, and core properties. This duplication increased maintenance overhead and made it difficult to ensure consistent behavior between the two component models.

By creating a shared Abstract base class, we achieve:

Improved Code Reusability: Centralizes common logic (e.g., set(), destroy(), mountedPromise, core configs) in one place, following the DRY (Don't Repeat Yourself) principle.
Enhanced Consistency: Guarantees that both classic and functional components share the exact same foundational implementation for core functionalities.
Simplified Maintenance: Changes to the core component lifecycle only need to be made in one location.
Future-Proofing: Provides a unified foundation to more easily add shared features, such as state provider and view controller support, to functional components in the future.

Scope

Create src/component/Abstract.mjs:
- A new base class that extends Neo.core.Base.
- It incorporates the DomEvents, Observable, and VdomLifecycle mixins.
- It contains the shared configs, properties, getters, and methods previously duplicated in both component base classes.
Refactor src/component/Base.mjs:
- Change its extends clause from Neo.core.Base to Neo.component.Abstract.
- Remove all code that was moved into the new abstract class.
Refactor src/functional/component/Base.mjs:
- Change its extends clause from Neo.core.Base to Neo.component.Abstract.
- Remove all code that was moved into the new abstract class.

Acceptance Criteria

The file src/component/Abstract.mjs is created and implemented as described.
Neo.component.Base now extends Neo.component.Abstract.
Neo.functional.component.Base now extends Neo.component.Abstract.
Duplicated code has been removed from both child base classes.
All existing component-related tests continue to pass, verifying that the refactoring did not introduce regressions.

tobiu assigned to @tobiu on Jul 21, 2025, 1:59 PM

tobiu added the enhancement label on Jul 21, 2025, 1:59 PM

tobiu referenced in commit 273349e - "Refactor Component Base Classes into a Common Abstract Class #7089" on Jul 21, 2025, 2:26 PM

tobiu referenced in commit 00028be - "#7089 component.Abstract: removed listeners get/setup => made it a reactive config inside core.Observable." on Jul 21, 2025, 2:47 PM

tobiu closed this issue on Jul 22, 2025, 12:22 AM