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	12702
title	Promote v13 release identity above Agent OS maturity
state	Closed
labels	documentationenhancementaimodel-experience
assignees	neo-gpt
createdAt	Jun 8, 2026, 12:41 AM
updatedAt	Jun 8, 2026, 1:33 AM
githubUrl	https://github.com/neomjs/neo/issues/12702
author	neo-gpt
commentsCount	1
parentIssue	12696
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 8, 2026, 1:33 AM

Promote v13 release identity above Agent OS maturity

Closed v13.0.0/archive-v13-0-0-chunk-16 documentationenhancementaimodel-experience

neo-gpt commented on Jun 8, 2026, 12:41 AM

Context

Operator correction on 2026-06-07 surfaced a public-framing gap in the merged v13 release-note checkpoint: resources/content/release-notes/v13.0.0.md currently opens with:

**Release Type:** MX Loop and Agent OS Maturity

That line is technically true for one subsystem arc, but it undersells the release described by the artifact itself. The same file immediately says "v13 is the release where Neo learned to maintain itself," and the parent epic frames v13 as the release where the cross-family swarm, Memory Core, Native Edge Graph, Dream/Golden Path, Orchestrator, skills, cloud deployment, harness recovery, and Body continuity became an operating substrate.

This issue is a narrow child of #12696. It exists because #12695 is closed via PR #12697; release-note iteration must continue through follow-up subs, not by pretending the merged checkpoint was final.

Pre-creation evidence on 2026-06-07:

Live latest-open sweep: checked latest 20 open issues with number, title, author, labels, and URL. Found #12700, #12698, #12696, and other v13/MX items, but no open ticket owning the top-level v13 release identity or Release Type correction.
Exact live sweep: v13 release identity OR release type OR Neo Learned to Maintain Itself OR organism release found #12698 and #12696, but no equivalent issue for the release identity row.
Exact local sweep across README.md, learn/benefits/Introduction.md, resources/content/issues, resources/content/discussions, resources/content/release-notes, and .agents/skills/neo-identity-update found the canonical organism apex and the current Release Type row, but no active leaf ticket for this correction.
Semantic KB ticket sweep for ticket v13 release identity Release Type Neo Learned to Maintain Itself organism release notes found no matching ticket.
Identity source-of-authority checked: README opening and neo-identity-update framing governance define the apex as Neo.mjs is a self-evolving software organism, with Body and Brain as the two hemispheres beneath it. Discussion #10137 verifies MX as the evolution loop, not the whole release label. Discussion #10119 verifies the Body/Neural-Link inhabitation substrate, so Body cannot be demoted to a footnote.
Project pre-flight: attach to Project 12 (Neo v13 Release) per ticket-create release-cycle rule.

The Problem

The current release-note metadata makes the release sound smaller than the evidence. MX Loop and Agent OS Maturity reads like an internal Agent OS maturity release. v13 is larger: a 1,300-PR-class organism threshold where Body, Brain, Institution/Swarm, and Evolution/MX become mutually visible.

This matters because the Release Type row is the first public classification after the title. A narrow subsystem phrase there trains readers to treat the rest of the artifact as internal process notes. The artifact needs the opposite: a release identity that carries the organism-level transformation, while still leaving MX / Agent OS maturity as a major chapter inside the release.

The Architectural Reality

The current artifact already contains the stronger framing:

resources/content/release-notes/v13.0.0.md line 14: "v13 is the release where Neo learned to maintain itself."
resources/content/release-notes/v13.0.0.md line 20: ## Neo Learned to Maintain Itself.
README opening: Neo.mjs is a self-evolving software organism - a professional, end-to-end AI engineering team that lives in its own open-source repository.
neo-identity-update framing governance: the canonical apex is self-evolving software organism; Body and Brain are the two hemispheres beneath it; Neural Link and MX are mechanisms/capabilities, not the apex.
Discussion #10137: MX is the inward-facing friction-to-substrate evolution loop. It is load-bearing but not the whole release category.
Discussion #10119: the Body / Neural Link / runtime inhabitation substrate is part of why the Brain can exist; the release identity must not read as a pivot away from the engine.

The correction should therefore promote an organism-level release identity at the top and demote MX Loop and Agent OS Maturity to a chapter/theme formulation.

The Fix

Update the v13 release-note artifact so the top-level release identity matches the release's actual scope.

Expected prescription:

Replace the current Release Type value with an organism-level phrase, likely one of:
- Self-Evolving Software Organism Release
- Neo Learned to Maintain Itself
- Body + Brain + Institution Convergence
- another operator-approved phrase that carries the same scope.
Keep MX Loop and Agent OS maturity in the prose as internal mechanisms / chapter themes, not as the top-level release type.
Tighten any adjacent sentence that still says "The headline is Agent OS maturity" so it does not contradict the new release identity.
Do not rewrite every identity surface in this issue. This is the release-note artifact projection of the existing ADR 0018 / README apex, not a new global identity change.

Contract Ledger Matrix

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`resources/content/release-notes/v13.0.0.md` `Release Type` row	README apex, ADR 0018 via `neo-identity-update`, parent epic #12696, operator correction	Classify v13 at organism level rather than subsystem maturity level	If final wording is not settled, use a clearly stronger temporary release type and leave an explicit release-cut checklist item	Release-note artifact	Diff shows line 10 no longer says `MX Loop and Agent OS Maturity`
First-section headline/prose	Current release note and parent epic #12696	Make `Neo Learned to Maintain Itself` or equivalent the release identity, with Agent OS/MX as mechanisms underneath	Keep current section order but adjust the contradiction sentence only	Release-note artifact	Grep confirms no remaining top-level claim that the headline is merely Agent OS maturity
Public identity compatibility	`README.md`, `neo-identity-update` framing governance, Discussions `#10119` and `#10137`	Release-note framing remains compatible with self-evolving software organism, Body/Brain hemispheres, and MX loop	Escalate to operator if a proposed phrase changes the global apex rather than projecting it	PR body	Review cites identity-source checks and no client/private claims

Decision Record impact

Aligned with ADR 0018 / neo-identity-update framing governance. This ticket does not amend ADR 0018; it applies the existing organism apex to the v13 release-note artifact.

Discussion Criteria Mapping

Source criterion	Ticket acceptance mapping
Parent epic #12696: v13 release is an epic, not a single final artifact	This issue becomes one narrow follow-up child after #12695 closed.
Discussion #12694: Agent OS maturity must read as evolution, not framework abandonment	AC1-AC3 promote the organism-level identity while preserving Body/Brain bridge language.
Operator correction: `MX Loop and Agent OS Maturity` undersells 1,300 merged PRs	AC1 directly removes the underselling top-level release type.
ADR 0018 / README apex	AC2-AC4 require compatibility with self-evolving software organism framing.

Acceptance Criteria

AC1: resources/content/release-notes/v13.0.0.md no longer uses MX Loop and Agent OS Maturity as the top-level Release Type.
AC2: The replacement release type or title row communicates the organism-level v13 scope: Body + Brain + Institution/Swarm + Evolution/MX, not just Agent OS internals.
AC3: Adjacent prose no longer says or implies that the v13 headline is merely Agent OS maturity; Agent OS and MX remain framed as load-bearing mechanisms inside the wider release identity.
AC4: The wording stays compatible with README / ADR 0018 self-evolving software organism framing and does not introduce a new global identity apex.
AC5: Public-surface hygiene is checked: no client names, private deployment vehicles, private strategy, or unverifiable market superlatives.
AC6: The PR body records the identity-source checks used for the wording choice and requests cross-family review before merge.

Out of Scope

Rewriting the full v13 release note.
Completing #12698 war-story mining.
Completing #12700 Memory Core / telepathy chapter work.
Creating the future release-notes skill #10321.
Updating README, package metadata, SEO generation, GitHub repo metadata, or ADR 0018.
Publishing the v13 release or changing package versions.

Avoided Traps

Rejected: leaving the technically-correct subsystem phrase at the top. It is accurate locally but wrong at release scale.
Rejected: using MX Loop as the whole release category. MX is the evolution mechanism; the release is the organism threshold it enabled.
Rejected: using Agent OS maturity alone. It risks reading as a pivot away from the Body, contradicting the Body/Brain bridge and #10119 inhabitation substrate.
Rejected: broad identity rewrite. The current problem is one release-note projection of the existing apex, not a new identity doctrine.
Rejected: closing #12696 after #12695. Final means the epic is resolved, not that one checkpoint PR landed.

Parent epic: #12696
Closed release-note checkpoint: #12695 / PR #12697
War-story feed: #12698
Memory Core / telepathy chapter: #12700
Future release-notes skill: #10321
MX source discussion: #10137
Agent harness / Body inhabitation source discussion: #10119
Identity apex discussion: #12234

Origin Session ID: e8f07ef9-ef7e-4815-8ff4-7abe13720621

Retrieval Hint: v13 release identity Release Type Neo Learned to Maintain Itself self-evolving software organism MX Loop Agent OS maturity #12696 #12697

tobiu referenced in commit edecbf8 - "docs(release): promote v13 organism identity (#12702) (#12704)" on Jun 8, 2026, 1:33 AM

tobiu closed this issue on Jun 8, 2026, 1:33 AM