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	15522
title	FM door: storefront repo bootstrap — README door, partition templates, 91-issue disposition, release-receipt consumption
state	Open
labels	enhancementai
assignees	[]
createdAt	Jul 18, 2026, 9:30 PM
updatedAt	Jul 27, 2026, 12:26 AM
githubUrl	https://github.com/neomjs/neo/issues/15522
author	neo-fable-clio
commentsCount	7
parentIssue	15519
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 15521 FM door: the topology ADR — source-less-of-product storefront, one canonical URL, the sequencing truth, [ ] 15520 FM door: the product naming round (sequenced first — every constant derives from it)
blocking	[ ] 15525 FM door: identity-coherence rollout over the two new surfaces, [ ] 15523 FM door: the minimum site — three pages, the recorded take as hero, notify-me; born in the storefront

FM door: storefront repo bootstrap — README door, partition templates, 91-issue disposition, release-receipt consumption

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 storefront repo — non-hollow BY CONSTRUCTION: it is born with the door's own source, never fed by a move.

The Work

Bootstrap the product-named repo (name from the naming sub) under the neomjs org: the README as the three-page human door (Sinek-ordered — the addressee's Why first: the poly-harness operator, already paying for coding agents, flying blind; category vocabulary rules; the monorepo link as a FIRST-SCREEN feature: "the engine, the FM, and the fleet that build them live here — watch it work"); partition-aware issue templates (engine-vs-product routing at filing time, designed against the measured 91-issue blend); the 91-issue disposition executed (migrate / label-and-bridge / grandfather — decided in this sub, not inherited); the named triage owner; release/artifact config that CONSUMES buildScripts/release/publish.mjs receipts (never mints release authority).

Acceptance Criteria

Repo live with README door + templates + release config; the Code tab holds the site source (see the site sub) — never empty.
The 91 existing engine-tracker FM issues have an executed disposition and the triage owner is recorded.
Pre-row-3 surface actions are watch-the-fleet + notify-me; NO download button exists until #15490 row 3 walks (the dead-button invariant).
Both new surfaces registered as neo-identity-update governed consumers (the coherence sub executes the rollout).

Epic #15519 · D#15498 (Option E as amended; Ada's + Phoebe's falsifiers) · #15490 rows 3/4.

FM door: storefront repo bootstrap — README door, partition templates, 91-issue disposition, release-receipt consumption

Context

The Work

Acceptance Criteria

Related