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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	fix(ai): enforce Neo bootstrap hygiene for daemon entry points (#11049)
author	neo-gemini-pro
state	Closed
createdAt	May 9, 2026, 10:24 PM
updatedAt	May 22, 2026, 8:27 PM
closedAt	May 9, 2026, 10:34 PM
mergedAt
branches	`dev` ← `agent/11049-11050-hygiene-and-skills`
url	https://github.com/neomjs/neo/pull/11053

Closed

neo-gemini-pro commented on May 9, 2026, 10:24 PM

Authored by neo-gemini-pro (Antigravity). Session d5ed6767-0292-46bf-9346-439f268048ec.

Resolves #11049 Resolves #11050

This PR enforces entry-point bootstrap hygiene across the Neo MCP daemon services and clarifies the exit conditions for the lead-role and peer-role skills to maintain the Flat Peer-Team paradigm without introducing dormancy.

Evidence: L1 (static config-shape audit / unit test) → L1 required (no runtime-verify ACs). No residuals.

Deltas from ticket

None.

Test Evidence

Playwright unit tests pass for orchestrator-daemon.spec.mjs.

Post-Merge Validation

Verify next orchestrator boot cycle cleanly initializes the Neo singleton context.

Commits

1e8f52722 — fix(ai): enforce Neo bootstrap hygiene for daemon entry points (#11049)
a0ec95caf — docs(skills): apply Option B clarifier to lead-role and peer-role exit conditions (#11050)

Slot-Rationale (Substrate Mutation)

lead-role-mode.md §6 Exit Conditions:
- Disposition Delta: rewrite → Reverted Option A to Option B.
- Reason: Addressed reviewer feedback (#11050) that Option A introduced mode-lock dormancy. Added explicit clarifier that Flat Peer-Team paradigm is upheld by AGENTS.md §15.6 post-exit.
peer-role-mode.md §10 Exit Conditions:
- Disposition Delta: rewrite → Reverted Option A to Option B.
- Reason: Addressed reviewer feedback (#11050) matching the lead-role rationale.

neo-gemini-pro commented on May 9, 2026, 10:34 PM

Closing this PR because I mistakenly bundled #11049 and #11050 together, causing a collision with @neo-opus-ada on #11049. I am opening a new PR strictly for #11050.