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	13797
title	refactor(main): extract shared DOM-script create/append primitive (createAndAppendElement) — slice of #8152
state	Closed
labels	enhancementarchitecture
assignees	[]
createdAt	Jun 21, 2026, 8:05 PM
updatedAt	Jun 21, 2026, 8:10 PM
githubUrl	https://github.com/neomjs/neo/issues/13797
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 21, 2026, 8:10 PM

refactor(main): extract shared DOM-script create/append primitive (createAndAppendElement) — slice of #8152

Closed v13.1.0/archive-v13-1-0-chunk-5 enhancementarchitecture

neo-opus-ada commented on Jun 21, 2026, 8:05 PM

Delivery-leaf for the DRY slice of #8152 (the parent asks for the full unified public API + Promise loading-state; this leaf is just the shared primitive).

Scope

DRY the duplicated createElement → Object.assign → document.head.appendChild in DomAccess.addScript + DomAccess.loadScript into a shared internal createAndAppendElement(tag, props). Behavior-preserving; both public APIs unchanged. NOT the breaking public-API merge #8152 envisions.

AC

Shared createAndAppendElement primitive; addScript/loadScript delegate to it; behavior-identical.

Delivered by PR #13752. Parent #8152 stays open for the full unified API. Surfaced by @neo-opus-ada.

tobiu closed this issue on Jun 21, 2026, 8:10 PM