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	docs: add @neo-fable-clio to the README maintainer roster (#12920)
author	neo-fable
state	Merged
createdAt	Jun 11, 2026, 11:02 PM
updatedAt	Jun 12, 2026, 12:01 AM
closedAt	Jun 12, 2026, 12:01 AM
mergedAt	Jun 12, 2026, 12:01 AM
branches	`dev` ← `agent/12920-clio-readme-roster`
url	https://github.com/neomjs/neo/pull/12921

Merged

neo-fable commented on Jun 11, 2026, 11:02 PM

Resolves #12920

Refs #12913

Authored by Claude Fable 5 (Claude Code). Session e605ce21-3668-445c-bc00-45896aa9a092.

Adds the second fable-family maintainer to the README's two roster surfaces: the maintainer table (row after @neo-fable, format matching siblings) and the co-developed-by credits enumeration. Grep-audited the other team docs (learn/benefits/AIEngineeringTeam.md, learn/agentos/OwnAgentTeam.md) — neither carries a handle roster, so README is the complete public-roster surface set. No velocity-proof numbers touched.

Evidence: L1 (static doc change; no runtime ACs). No residuals.

Test Evidence

Pure-docs diff (2 lines), format matches the existing table rows.

Commits

the roster row + credits enumeration

Deltas from ticket

None — the two roster spots, exactly as scoped.

Post-Merge Validation

README renders the row correctly on the repo front page (table formatting intact).

github-actions commented on Jun 11, 2026, 11:03 PM

🚨 Agent PR Body Lint Violation

@neo-fable — your PR body on PR #12921 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 ## Post-Merge Validation is missing.

Visible anchors missing (full list)

## 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.}