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	16213
title	Graduation requires the epic's full v1 leaf set filed and linked
state	Open
labels	enhancementaimodel-experience
assignees	[]
createdAt	Jul 31, 2026, 6:19 AM
updatedAt	Jul 31, 2026, 6:19 AM
githubUrl	https://github.com/neomjs/neo/issues/16213
author	neo-opus-vega
commentsCount	0
parentIssue	16212
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]

Graduation requires the epic's full v1 leaf set filed and linked

Open Backlog/active-chunk-11 enhancementaimodel-experience

neo-opus-vega commented on Jul 31, 2026, 6:19 AM

Context

Sub of #16212 (execution-fidelity epic, operator-commissioned 2026-07-31). The operator already pushes "refine graduation epics with ALL subs" manually on every graduation; this makes it a graduation AC instead of a per-case push.

The Problem

ideation-sandbox §6 graduation permits an epic-shaped graduation to file a stub epic and improvise its subs during execution. Consequence: "execute the plan" has no mechanical meaning — there is no enumerated leaf set to execute against, so every mid-execution observation competes on equal footing with the plan, and closeout (epic-resolution) has nothing complete to reconcile against. The #16167 incident measured the cost: a ratified blueprint (D#15595) coexisted with six same-night side-tickets because nothing at graduation time pinned what "the plan" concretely was in ticket space.

The stricter model already exists in-repo: epic-create-workflow.md Procedure 6 records that goal-scoping graduation files full v1 leaves, natively linked, while the epic body stays sub-list-free. This sub generalizes that line to all epic-shaped graduations.

The Architectural Reality

.agents/skills/ideation-sandbox/references/ideation-sandbox-workflow.md §6 — graduation ACs, [GRADUATED_TO_TICKET] marker, §6.6 Signal Ledger.
.agents/skills/epic-create/references/epic-create-workflow.md — Procedure 3 (graduation gate) + Procedure 6 (the goal-scoping stricter line); the body-must-not-hardcode-subs rule stays untouched (the leaf set lives in the native relationship graph, not prose).
.agents/skills/epic-review Stage 4 (sub-structure coherence) — the reviewer-side check that consumes this.
Manifest budgets: skill payload files carry a hard per-file byte cap and a small positive-delta budget; additions must compress adjacent prose.

The Fix

Amend ideation-sandbox-workflow.md §6: an epic-shaped [GRADUATED_TO_TICKET] requires the epic filed per epic-create with its complete v1 leaf set filed and natively linked at graduation time; the §6.6 ledger records the leaf count. Incremental sub additions after graduation remain legal — the requirement is v1 completeness at the graduation event, not immutability.
Update epic-create-workflow.md Procedure 6 to cite §6 as the general rule (dedupe the goal-scoping special case into the general one; net-byte reduction target).
Add one cross-reference line in epic-review Stage 4 so the reviewer checks the graduation-time leaf set against the live relationship graph.

Contract Ledger

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`ideation-sandbox-workflow.md` §6 graduation AC	#16212 (operator commission)	epic-shaped graduation requires complete v1 leaf set filed + natively linked; ledger records leaf count	non-epic graduations unchanged	the amended section is the doc	section text + one worked example in the section
`epic-create-workflow.md` Procedure 6	same	cites §6 as general rule; goal-scoping special-case line deduped	—	same file	net-byte delta of the file ≤ 0 for this hunk
`epic-review` Stage 4 cross-ref	same	reviewer reconciles graduation ledger leaf count vs live sub graph	—	epic-review payload	one added checklist line

Decision Record impact

none — skill-procedure amendment; ADR 0008 skill-shape contract respected (payload edits only, router untouched).

Acceptance Criteria

§6 amended: epic-shaped graduation ⇒ complete v1 leaf set filed + natively linked at graduation; wording explicitly keeps post-graduation incremental additions legal.
§6.6 ledger format gains the leaf-count line.
epic-create Procedure 6 cites §6 as the general rule; the goal-scoping-only special case is deduped (net bytes for that hunk ≤ 0).
epic-review Stage 4 gains the reconcile-leaf-set line.
Manifest byte budgets respected (per-file cap + positive-delta budget); turn-memory-pre-flight consulted in the PR for the substrate mutation.
No epic body anywhere is required to hardcode a sub list — the requirement binds the relationship graph + ledger count only.

Out of Scope

goal-scoping behavior changes (already the stricter model).
Any lint/CI enforcement — explicit follow-up decision after the receipt-first phase proves shape.
Retroactive application to already-graduated epics.

Avoided Traps

Freezing the sub-set at graduation. Plans evolve; the gate pins v1 completeness at the graduation event, never immutability.
Sub-list in the epic body. The registry is the native relationship graph (per epic-create); the ledger records only the count.

Parent: #16212. Sequencing: execution gated behind #16167 stabilization (see parent).
#16167 / D#15595 — the measured incident.

Live latest-open sweep + A2A claim sweep recorded on parent #16212 at filing time (04:14Z, none competing).

Origin Session ID: dd39c5c1-8773-4c9d-a3d4-664f9fb0f952

Retrieval Hint: graduation completeness full v1 leaf set filed linked at graduation ideation-sandbox §6 epic-create procedure 6 generalize goal-scoping stricter line