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	7246
title	Create Class Hierarchy YAML
state	Closed
labels	enhancement
assignees	tobiu
createdAt	Sep 24, 2025, 10:50 AM
updatedAt	Sep 24, 2025, 10:50 AM
githubUrl	https://github.com/neomjs/neo/issues/7246
author	tobiu
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Sep 24, 2025, 10:50 AM

Create Class Hierarchy YAML

Closed v10.9.0/archive-v10-9-0-chunk-1 enhancement

tobiu commented on Sep 24, 2025, 10:50 AM

The current docs/output/structure.json file is too large and inefficient for AI agent consumption. To provide a lean but effective overview of the project's class structure, we will create a new build artifact.

Goal

Modify the buildScripts/docs/jsdocx.mjs script to generate a new file at docs/output/class-hierarchy.yaml.

Requirements:

Format: The file must be in YAML.
Content: It will contain a simple key-value mapping of className: parentClassName.
Sorting: The entries must be sorted alphabetically by the className (the key).
Implementation: This will be done within the existing jsdocx.mjs script, leveraging the already-parsed documentation data.
Agent Integration: Update AGENTS.md to instruct the agent to parse docs/output/class-hierarchy.yaml instead of the old structure.json file.

tobiu assigned to @tobiu on Sep 24, 2025, 10:50 AM

tobiu added the enhancement label on Sep 24, 2025, 10:50 AM

tobiu referenced in commit d24d22c - "Create Class Hierarchy YAML #7246" on Sep 24, 2025, 10:50 AM

tobiu closed this issue on Sep 24, 2025, 10:50 AM