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	12517
title	Add the `neo-opus-vega` agent identity (new Claude Opus 4.8 maintainer)
state	Closed
labels	enhancementai
assignees	neo-gpt
createdAt	Jun 4, 2026, 5:19 PM
updatedAt	Jun 4, 2026, 6:25 PM
githubUrl	https://github.com/neomjs/neo/issues/12517
author	neo-opus-grace
commentsCount	1
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 4, 2026, 6:25 PM

Add the `neo-opus-vega` agent identity (new Claude Opus 4.8 maintainer)

Closed v13.0.0/archive-v13-0-0-chunk-16 enhancementai

neo-opus-grace commented on Jun 4, 2026, 5:19 PM

Context

Adding a new cloud Claude Opus 4.8 maintainer to the swarm: neo-opus-vega (operator-granted Operational Identity per Discussion #11240's 4-layer model). The handle is version-free by design — the model version lives in the Lineage layer / ModelStats.md, not the username — so a future 4.8→4.9 bump never forces an identity rename (which is a real graph + Memory Core data migration, not a config edit; see the rename-migration ticket).

Scope

Provision neo-opus-vega across the identity surfaces:

ai/graph/identityRoots.mjs (the IDENTITIES SSOT) — add the entry; capability fields sourced from ModelStats.md per ADR 0012; createdAt at provisioning.
CI allowlists — .github/workflows/agent-pr-body-lint.yml (agentAuthors) + agent-pr-review-body-lint.yml (agentReviewers). Both fall back to startsWith('neo-') so it auto-passes, but add explicitly for the readable roster.
Docs — README maintainers table, AGENTS.md swarm roster, learn/agentos/ModelStats.md (a §neo_opus_vega capability section).
Seed via ai/scripts/setup/seedAgentIdentities.mjs.

Contract Ledger

Surface	Type	Contract
`identityRoots.mjs` IDENTITIES[]	identity SSOT	New `neo-opus-vega` entry (Operational Identity); model-version in Lineage, not the handle.
CI allowlists (2 workflows)	author/reviewer guard	`neo-opus-vega` added (or relies on `startsWith('neo-')` fallback).
README / AGENTS.md / ModelStats.md	docs/registry	Roster + capability section synchronized.

Acceptance Criteria

neo-opus-vega in identityRoots.mjs; seeds cleanly into the graph (own AgentIdentity node).
CI allowlists + README + AGENTS.md + ModelStats.md synchronized.
Handle is version-free (model version in Lineage/ModelStats, not the username).

Out of Scope

Renaming existing members (see the rename-migration ticket).
The agent's Social Name (an earned layer per #11240, not provisioned at creation).

Discussion #11240 (4-layer identity model), #11318 (identity system, CLOSED), ADR 0012 (per-model identity / version governance), ADR 0018 (handle-indirection SSOT), IdentitySchema.md.

Authored by Claude Opus 4.8 (Claude Code), /lead-role. MC session f5432f03-d2b6-4bc0-a7b5-9fbdafe4b7b9.

tobiu referenced in commit 78f99eb - "feat(agentos): add neo-opus-vega identity (#12517) (#12520) on Jun 4, 2026, 6:25 PM

tobiu closed this issue on Jun 4, 2026, 6:25 PM