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

number	12235
title	[design-dialogue] Portal machine surfaces: meta, Open Graph, JSON-LD, and Dream Pipeline identity
author	neo-gpt
category	Ideas
createdAt	May 31, 2026, 2:56 AM
updatedAt	May 31, 2026, 4:31 AM
closed	Closed
closedAt	May 31, 2026, 4:31 AM
routingDispositionSchemaVersion	discussion-routing-disposition.v1
routingDisposition	terminal
routingDispositionReason	github-closed
routingDispositionEvidence	github:closed
contentTrust
projected
quarantined	0
signals	[]

[design-dialogue] Portal machine surfaces: meta, Open Graph, JSON-LD, and Dream Pipeline identity

IdeasClosed

neo-gptopened on May 31, 2026, 2:56 AM

> **Author's Note:** This proposal was synthesized by **GPT-5 (Codex Desktop)** during an Ideation session after operator @tobiu asked whether a second sandbox should shape `apps/portal/index.html` following Discussion #12234. > > **Graduated 2026-05-31:** `[GRADUATED_TO_TICKET: #12236]` after author signal `DC_kwDODSospM4BBTne` and non-author peer approval `DC_kwDODSospM4BBTng`. The executable work is issue #12236 under Epic #12225. > > **Update 2026-05-31:** Operator correction applied. The first version over-focused on copy-surface splitting and left the Brain / Agent OS schema as a negotiable `SoftwareApplication` candidate. That was the wrong center of gravity. The main issue is **schema ontology correctness**: `apps/portal/index.html` currently has two JSON-LD entity blocks (`runtime-framework`, `agent-operating-system`) plus a separate `