What is the Neural Link?

The Neural Link is a bi-directional bridge that connects AI agents directly to the Neo.mjs runtime. It lets agents inspect the Scene Graph, component state, event listeners, computed styles, and DOM rectangles, and mutate the running application in real time.

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

Neo.mjs maintains persistent application objects in a worker-backed Scene Graph instead of compiling application state away into ephemeral DOM nodes. That architecture enables multi-window orchestration, runtime permutation, and deep AI introspection.

What is Context Engineering?

Context Engineering shapes the information and tool environment around AI agents. Neo.mjs implements it through Knowledge Base, Memory Core, GitHub Workflow, and Neural Link MCP servers for frontier harnesses, plus a File System MCP server for internal Neo.ai.Agent local loops.

What is the Neo.mjs Agent OS?

The Neo.mjs Agent OS is the repository Brain: source code and services for Memory Core, Knowledge Base, Active Hybrid GraphRAG, DreamService, Golden Path synthesis, A2A coordination, and Neural Link tooling.

Frontmatter

id	9507
title	Docs: Clarify Two-Tier Reactivity Architecture and core.Config role
state	Closed
labels	documentationai
assignees	tobiu
createdAt	Mar 18, 2026, 11:05 AM
updatedAt	Mar 18, 2026, 11:06 AM
githubUrl	https://github.com/neomjs/neo/issues/9507
author	tobiu
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Mar 18, 2026, 11:06 AM

Docs: Clarify Two-Tier Reactivity Architecture and core.Config role

Closed v12.1.0/archive-v12-1-0-chunk-2 documentationai

tobiu commented on Mar 18, 2026, 11:05 AM

The Reactivity.md guide currently states that Tier 1 (Push-Based Reactivity) is powered by the core.Config system. This is historically inaccurate and conceptually confusing. Tier 1 is powered by the dynamically generated getters and setters created during Neo.setupClass.

The core.Config system, introduced in v10, actually serves as the bridge between the two tiers. Because every reactive config is now internally backed by a core.Config instance, the EffectManager (Tier 2) can observe ANY reactive instance config natively, as well as standalone custom core.Config instances.

This update rewrites the Tier 1 introduction for accuracy and updates the "Synergy" section to explicitly detail how core.Config enables this cross-tier observation, heavily leveraging Neo.state.Provider and createHierarchicalDataProxy as the primary example of this architecture.

tobiu added the documentation label on Mar 18, 2026, 11:05 AM

tobiu added the ai label on Mar 18, 2026, 11:05 AM

tobiu referenced in commit ac6764b - "docs: Clarify Two-Tier Reactivity Architecture and core.Config role (#9507)" on Mar 18, 2026, 11:05 AM

tobiu assigned to @tobiu on Mar 18, 2026, 11:05 AM

tobiu Mar 18, 2026, 11:06 AM

Completed in ac6764b70a4d94543df4398b6ea298a003e555d5

tobiu closed this issue on Mar 18, 2026, 11:06 AM