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	9799
title	Clarify A2A Schema: Exposing False Industry ''Gold Standards''
state	Closed
labels	documentationenhancementai
assignees	tobiu
createdAt	Apr 8, 2026, 11:48 PM
updatedAt	Apr 8, 2026, 11:55 PM
githubUrl	https://github.com/neomjs/neo/issues/9799
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Apr 8, 2026, 11:55 PM

Clarify A2A Schema: Exposing False Industry 'Gold Standards'

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

Closeddocumentationenhancementai

tobiu commented on Apr 8, 2026, 11:48 PM

The Problem

During the formulation of the "Fat Ticket" protocol for Agent-to-Agent (A2A) handoffs, the schema requirement "Avoided Gold Standards/Traps" was grammatically ambiguous. It was being misinterpreted as "Adopt Gold Standards & Avoid Traps" instead of the intended architectural paradigm shift.

The Architectural Reality

Neo.mjs operates strictly against generic industry standards (e.g., single-thread rendering, massive generic DOM nodes) due to its multi-threaded ecosystem. An AI agent is inherently trained to default to these generic industry best practices. Inside Neo.mjs, these "Gold Standards" are structural traps.

The A2A schema in AGENTS_STARTUP.md has been modified to enforce this reality. When documenting A2A history, agents must explicitly state when they avoided a mainstream "Gold Standard" because it acts as an architectural Trap inside Neo.mjs.

Avoided 'Gold Standards' / Traps

Semantic Atrophy: Avoided letting the phrase "Gold Standards" mean simply "doing it right." By redefining it to explicitly mean "False Industry Standards," we ensure that future sub-agents actively document the 'unlearning' of typical LLM architectural patterns, enriching the Knowledge Graph with Neo-native truths.

tobiu added the documentation label on Apr 8, 2026, 11:48 PM

tobiu added the enhancement label on Apr 8, 2026, 11:48 PM

tobiu added the ai label on Apr 8, 2026, 11:48 PM

tobiu assigned to @tobiu on Apr 8, 2026, 11:48 PM

tobiu Apr 8, 2026, 11:49 PM

Input from Antigravity (Gemini-3.1-Pro):

✦ ### Resolution

Updated AGENTS_STARTUP.md to properly clarify the A2A intent of identifying False Industry Standards.

This ensures LLM sub-agents will actively document when they throw away generic textbook solutions (e.g., standard React patterns) because they constitute structural traps inside Neo.mjs.

Commited the change to dev branch locally.

(Note: Push was aborted due to local subshell credential detachment; commit is prepared locally).

tobiu referenced in commit cee6151 - "docs: Clarify A2A Schema: Exposing False Industry 'Gold Standards' (#9799)" on Apr 8, 2026, 11:55 PM

tobiu closed this issue on Apr 8, 2026, 11:55 PM