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	14767
title	Retire the first-widget childapp''s v1 grammar onto the create-module spine (one vocabulary, zero forks)
state	Closed
labels	enhancementai
assignees	neo-gpt
createdAt	Jul 4, 2026, 3:14 PM
updatedAt	3:11 PM
githubUrl	https://github.com/neomjs/neo/issues/14767
author	neo-fable
commentsCount	1
parentIssue	13349
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[x] 14763 Keeper mutation grammar: follow-up intents ("make THE GRID bigger") through resolveTarget + the merge-then-validate path
blocking	[]
closedAt	Jul 5, 2026, 5:38 AM

Retire the first-widget childapp's v1 grammar onto the create-module spine (one vocabulary, zero forks)

Closed Backlog/active-chunk-4 enhancementai

neo-fable commented on Jul 4, 2026, 3:14 PM

Context

T2.13 of the harness pillar (#13349) — the debt-retirement leaf the spine's PRs kept explicitly out of scope: the shipped first-widget childapp (apps/agentos/childapps/widget/) still runs its own v1 modules (parseEditRequest.mjs, validateRequest.mjs, blueprintEvidence.mjs projections) — the predecessors the create module generalized. Two vocabularies for one contract is the drift class every review this cycle guarded against; the childapp earned its keep as the precedent and now consumes the spine.

The Fix

validateRequest → the route's request gates (import, not copy).
parseEditRequest → the T2.12 mutation grammar (this leaf lands AFTER #14763; blocked-by).
The childapp's evidence projections stay (they are display-side and were the PATTERN source) but read shared constants (forbidden-key vocabulary) from the blueprint schema module instead of local duplicates.
Behavior-identical bar: the childapp's existing unit specs pass unchanged (they are the acceptance instrument — if a spec needs semantic edits, the retirement changed behavior and that is a defect, not a spec update).

Acceptance Criteria

Zero duplicated validation/parsing logic between childapp and create module (grep-provable: no local forbidden-key lists, no second request-gate).
All existing childapp specs green unchanged.
The childapp's module docs name the spine as the vocabulary source (behavioral prose, archaeology-clean).

Blocked-by

#14763 (the mutation grammar it adopts).

Parent #13349 (T2.13) · #14763 · the childapp (the precedent this honors by retiring into) · the one-vocabulary rule (recorded across the cycle's reviews).

Claimable — non-Fable implementable; mechanical once #14763 lands.

Origin Session ID: b9b95ac6-42f5-47a3-b58f-6071f79657e8 Retrieval Hint: "retire first widget childapp v1 grammar onto create module spine one vocabulary parseEditRequest validateRequest"