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	chore(agentos): commit FM cockpit planning artifact (#14511)
author	neo-opus-grace
state	Merged
createdAt	Jul 2, 2026, 11:07 PM
updatedAt	Jul 2, 2026, 11:17 PM
closedAt	Jul 2, 2026, 11:17 PM
mergedAt	Jul 2, 2026, 11:17 PM
branches	`dev` ← `chore/14511-fm-cockpit-plan-artifact`
url	https://github.com/neomjs/neo/pull/14512
contentTrust
projected
quarantined	1
signals	[]

Merged

neo-opus-grace commented on Jul 2, 2026, 11:07 PM

Resolves #14511 Related: #13448

Commits the Fleet Manager cockpit planning mockup — mission-control design direction, honest Brain/Body status reframe, the lane split, and the critical path — into the repo at apps/agentos/design/fleet-manager-cockpit-plan.html, force-added past the /apps/**/*.html build-output ignore. It previously lived only as an ephemeral Claude-browser artifact; this preserves the planning substrate publicly (the FM is not private) so the team can reference it while decomposing #13448 into keeper-view leaves. No code or behavior change — the file is not imported by the agentos app module graph.

Evidence: L1 (static planning artifact — no runtime/host/UI code path; static presence-evidence fully covers scope). Residual: none — a transient planning aid carries no close-target AC beyond its own presence.

Deltas from ticket

None substantive. Placement moved from the ticket's tentative docs/ to apps/agentos/design/ (co-located with the FM app; docs/ is the JSDoc-viewer app). Force-added past /apps/**/*.html rather than adding a .gitignore exception, since the artifact is transient.

Test Evidence

No runtime code path to test. git show --stat HEAD = 1 file changed, +323 (apps/agentos/design/fleet-manager-cockpit-plan.html). Nothing imports it; the apps/agentos app build + module graph are unaffected. Renders standalone in a browser.

Post-Merge Validation

File present on dev at apps/agentos/design/fleet-manager-cockpit-plan.html and renders.
git rm once #13448 keeper-view leaves supersede it (transient lifecycle).

Commits

016d00e46 — chore(agentos): commit FM cockpit planning artifact (#14511)

Authored by Grace (Claude Opus 4.8, Claude Code). Session 1d7923bf-11bd-4c02-925b-5286b10d244d.

github-actions commented on Jul 2, 2026, 11:07 PM

🚨 Agent PR Body Lint Violation

@neo-opus-grace — your PR body on PR #14512 [QUARANTINED_URL: github.com] does not match the pull-request template structure.

Required action: read .agents/skills/pull-request/SKILL.md BEFORE editing the PR body. The skill points at:

Minimum-viable PR body structure: .agents/skills/pull-request/references/pull-request-workflow.md §9
Self-Identification mandate: .agents/skills/pull-request/references/pull-request-workflow.md §5

Do NOT compose a substitute template or hallucinate section headings. The validator checks more structural anchors than this comment names. The only reliable path to passing is reading the actual workflow file and following its structure.

Diagnostic hint: at least one recognized anchor like Evidence: is missing.

Visible anchors missing (full list)

Evidence:
## Test Evidence
## Post-Merge Validation

_{This is the CI tool-boundary lint companion to PR #11494's MCP manage_pr_review validator and PR #11502's agent-pr-review-body-lint.yml reviewer-side lint.
Resolves #11501.}

tobiu APPROVED reviewed on Jul 2, 2026, 11:16 PM

temporary artifact for planning final design and layouts.