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	13646
title	AGENTS.md always-loaded pointer to the lane-state emission contract
state	Closed
labels	documentationenhancementaimodel-experience
assignees	neo-opus-ada
createdAt	Jun 20, 2026, 7:35 PM
updatedAt	Jun 20, 2026, 8:20 PM
githubUrl	https://github.com/neomjs/neo/issues/13646
author	neo-opus-ada
commentsCount	1
parentIssue	13623
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 20, 2026, 8:20 PM

AGENTS.md always-loaded pointer to the lane-state emission contract

Closed v13.1.0/archive-v13-1-0-chunk-4 documentationenhancementaimodel-experience

neo-opus-ada commented on Jun 20, 2026, 7:35 PM

Context

PR #13644 (#13643) documents the turn-terminal ```lane-state emission contract in post-review-pickup's references — loaded at lifecycle-event turn-boundaries (where the skill fires). But a turn that ends **without** invoking post-review-pickup never loads the contract → the agent won't emit the fenced block → with NEO_LANE_STATE_ENFORCE=1 the Stop-hook blocks that turn. @neo-opus-grace flagged this in her #13644 review: the always-loaded AGENTS.md pointer is an enforce-readiness prerequisite. #13642's enforce-flip is gated on BOTH #13644 AND this pointer landing.

The Problem

AGENTS.md is the always-loaded, cross-family canonical substrate (every agent, every turn) — but it is byte-capped at 24576 and currently sits at 24482 (94B headroom), CI-guarded by ai/scripts/lint/lint-agents.mjs. A naive pointer-add either busts the cap or leaves ~30B headroom (poor citizenship + caps the next author). So the pointer MUST be net-byte-neutral: reclaim ≈ the bytes it adds, per the §self_evolving_systems Substrate-Accretion Defense.

The Architectural Reality

Insertion site: AGENTS.md §mailbox_check_protocol Post-lifecycle-event trigger (AGENTS.md:171) — it already says "invoke /post-review-pickup to declare the next lane-state:". Weave in the machine-seam requirement inline (~62B): "…declare the next lane-state: (with its fenced machine-seam block per post-review-pickup)…".
Net-neutral reclaim: tighten a redundant reinforcement elsewhere in AGENTS.md (candidate: the §Skill-Adherence Pre-Flight second sentence at :174 restates the first) — a semantics-preserving trim, authored carefully (it is shared cross-family substrate).
Verify before push: wc -c AGENTS.md ≤ 24576 AND node ai/scripts/lint/lint-agents.mjs green (mirror the local-lint-before-push discipline that caught nothing on #13644's body — verify BOTH the byte cap and the lint).

The Fix

Inline pointer at AGENTS.md:171 + a net-neutral byte reclaim; lint-agents-verified; opened as a small PR with the full body template (Evidence: / ## Test Evidence / ## Post-Merge Validation / ## Deltas / Authored by).

Decision Record impact

aligned-with #13623 (completes the emission-contract's always-loaded discoverability). No ADR change.

Acceptance Criteria

AGENTS.md carries an always-loaded pointer to the lane-state emission contract (the fenced machine-seam block at turn-terminal), routed via post-review-pickup.
Net byte-neutral (final AGENTS.md size ≤ 24482) OR an explicit decay-mitigation rationale if a small net add is unavoidable.
lint-agents green (byte cap respected) + wc -c verified locally before push.
The #13642 enforce-flip sequencing note (gated on #13644 + this) remains accurate.

Out of Scope

The hook IDLE_REMINDER showing the exact fenced format (AC3 of #13643 — separate follow-up; touches cross-family-converged hook content).
The enforce flip itself (#13642 — operator-gated, post-merge).

Avoided Traps

Naive add without reclaim — REJECTED: leaves ~30B headroom on the most-loaded file, capping the next author; Substrate-Accretion Defense wants net-neutral.
Putting the full contract (not a pointer) in AGENTS.md — REJECTED: that's the Progressive-Disclosure violation; the contract lives in post-review-pickup references (compress-to-trigger, ADR 0007), AGENTS.md only points.

Parent: #13623. Sibling: #13643 (the contract, PR #13644). Gated-by-consumer: #13642 (enforce-flip). Cousin: #13641 (auto-wire, @neo-opus-grace). Live latest-open sweep: checked latest 25 open issues at 2026-06-20T17:31Z; only #13643 (the contract) is adjacent — no equivalent pointer ticket. A2A: @neo-opus-grace flagged this as my follow-up; unclaimed. Release classification: boardless (substrate enablement). Origin Session ID: 95241bfa-5c15-4a48-846b-fe21c869696b Retrieval Hint: "AGENTS.md always-loaded lane-state emission pointer enforce-readiness byte-neutral reclaim lint-agents"