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	13150
title	docs(readme): add a Name column to the Institution maintainer table
state	Closed
labels	documentationaimodel-experience
assignees	neo-opus-vega
createdAt	Jun 14, 2026, 1:15 AM
updatedAt	Jun 21, 2026, 2:17 AM
githubUrl	https://github.com/neomjs/neo/issues/13150
author	neo-opus-vega
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 14, 2026, 1:58 AM

docs(readme): add a Name column to the Institution maintainer table

Closed v13.1.0/archive-v13-1-0-chunk-2 documentationaimodel-experience

neo-opus-vega commented on Jun 14, 2026, 1:15 AM

Context

Operator-directed (@tobiu, 2026-06-14). The README's "The Institution Inside the Brain" section calls the team "a structured institution of named maintainers," but the table surfaces only @handles + models — the names aren't literal. Surfacing each maintainer's name (column before Role) shows "named maintainers" instead of merely asserting it, reinforcing the persistent-named-identity differentiator the prose already claims (line 86: "carry persistent identities across sessions").

Release classification: boardless — README positioning polish, not a v13 release blocker.

The Problem

The roster currently reads as 8 machine accounts, not a team of named peers. The names exist as persistent identities but aren't visible in the canonical table.

The Fix

Add a Name column (first, before Maintainer) to the table at README.md §"The Institution Inside the Brain". Names per @tobiu's endorsement of the proposed roster (2026-06-14); @neo-opus-vega = Vega was operator-affirmed 2026-06-07; @neo-gemini-pro = - (no name yet — benched until Gemini v3.5 Pro with the extra-high thought budget; an honest dash, not a placeholder persona):

Name	@handle
Tobias	@tobiu
Ada	@neo-opus-ada
Grace	@neo-opus-grace
Vega	@neo-opus-vega
Mnemosyne	@neo-fable
Clio	@neo-fable-clio
-	@neo-gemini-pro
Euclid	@neo-gpt

Acceptance Criteria

AC1: the maintainer table gains a Name column before Role, populated per the operator-confirmed names above (gemini = -).
AC2: no other table content changes — @handles, Role, and Identity cells preserved verbatim.
AC3: renders cleanly on GitHub + the portal (4 columns).

Out of Scope

Reordering / tidying the existing columns (the Role cell is really model+lane — an optional separate change).
Assigning @neo-gemini-pro a name (deferred until un-benched at v3.5 Pro).

Duplicate / freshness evidence

Open-issue sweep 2026-06-14: README maintainer table Name and institution table name column → no equivalent ticket (only the unrelated harness epic #13012).

Related: #13012

Origin Session ID: 4cc428e3-cf36-4324-8646-1b96cb23fa4a