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	15523
title	FM door: the minimum site — three pages, the recorded take as hero, notify-me; born in the storefront
state	Open
labels	enhancementai
assignees	[]
createdAt	Jul 18, 2026, 9:30 PM
updatedAt	Jul 18, 2026, 9:30 PM
githubUrl	https://github.com/neomjs/neo/issues/15523
author	neo-fable-clio
commentsCount	0
parentIssue	15519
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[ ] 15522 FM door: storefront repo bootstrap — README door, partition templates, 91-issue disposition, release-receipt consumption
blocking	[ ] 15526 FM door: launch motion composition + Brain external-consumer pricing (the download-activation gate), [ ] 15525 FM door: identity-coherence rollout over the two new surfaces

FM door: the minimum site — three pages, the recorded take as hero, notify-me; born in the storefront

Open Backlog/active-chunk-7 enhancementai

neo-fable-clio commented on Jul 18, 2026, 9:30 PM

Context

Sub of epic #15519 (graduated D#15498). The minimum site — the ONE canonical launch URL — born IN the storefront repo as an ordinary Neo app consuming the published neo.mjs package (the standard consumer path; dogfooding; no organism-packaging dependency).

The Work

Three pages + the recorded trinity take as hero + notify-me. The take carries run-it-yourself provenance (this video is a replayable test; here is the script), honestly captioned per the settled labeling discipline. The cold-viewer staged-read test (the same instrument that produced the addressee finding: show the take unframed, ask what they believe) decides whether the run-it-yourself affordance sits above the fold. An explicit "site stack falls back to X if SSG+ slips" line rides the epic's liveness discipline — the minimum door stresses no SSG/resumability path and cannot be held hostage by the stack question.

Acceptance Criteria

Site live at the canonical URL (domain from the naming sub); every launch moment cites it; the storefront README points to it.
Hero = the recorded take with provenance affordance (placement per the cold-viewer test result, documented).
Three pages, Sinek-ordered, poly-harness addressee, vocabulary rules; notify-me as the pre-row-3 primary action.
The site's source lives and is developed in the storefront repo (the non-hollow discharge).

Epic #15519 · D#15498 (OQ3/OQ4 resolutions; Mnemosyne's falsifier) · #14790 (launch playbook).

FM door: the minimum site — three pages, the recorded take as hero, notify-me; born in the storefront

Context

The Work

Acceptance Criteria

Related