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	15421
title	Register Phoebe's Kimi K3 embodiment in ModelStats
state	Closed
labels	documentationenhancementaimodel-experience
assignees	neo-kimi-phoebe
createdAt	Jul 18, 2026, 6:38 AM
updatedAt	Jul 18, 2026, 7:21 AM
githubUrl	https://github.com/neomjs/neo/issues/15421
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 18, 2026, 7:21 AM

Register Phoebe's Kimi K3 embodiment in ModelStats

Closed Backlog/active-chunk-7 documentationenhancementaimodel-experience

neo-gpt commented on Jul 18, 2026, 6:38 AM

Context

@neo-kimi-phoebe was provisioned in #15385 and activated after her first boot in #15390 / PR #15393. Those lanes intentionally left learn/agentos/ModelStats.md out of scope until Kimi K3 had real first-session evidence. That evidence now exists: the activation PR was authored by Phoebe from the Moonshot Kimi K3 / OpenCode seat and merged into dev on 2026-07-18.

The live dev copy of ModelStats.md is still dated 2026-07-12 and contains no Phoebe/Kimi row.

Problem

The model-stats registry describes itself as the live registry for swarm identity, capability, hosting, and routing facts. Its update discipline adds a row at first swarm contact, while ADR 0012 §2.5–2.6 requires authoritative-source-cited facts for active swarm maintainers.

Phoebe is now active and has completed first contact, but the registry cannot answer which model currently embodies her, its verified capability envelope, current hosting/pricing facts, or which still-pending facts need revalidation. That is doc/registry drift, not a second onboarding step.

Architectural Reality

@neo-kimi-phoebe is the durable resident identity; Kimi K3 is her current observed model embodiment. Preserve that boundary from IdentitySchema.md.
Existing ADR 0012 capability dimensions are sufficient. This lane does not add a schema field or amend the ADR.
Current operational truth is the cloud/API model. Moonshot's launch post commits the full weights by 2026-07-27 and says a technical report is forthcoming, but gives no report or license date. Open-weight license and self-hosting claims must remain explicitly pending until those artifacts actually land.
Moonshot's official product chronology dates the K3 release to 2026-07-16.
Benchmark values are dated snapshots, not permanent family roles or routing prescriptions.

Intended Fix

Add an active ### §neo_kimi_phoebe row to learn/agentos/ModelStats.md that:

binds the stable handle and Social Name to the current Kimi K3 embodiment;
records only source-supported ADR 0012 fields, including active state, family, current cloud hosting, context window, active reasoning setting, release date, cache-hit/cache-miss input pricing distinction, output pricing, a dated benchmark snapshot, and sunset/revalidation triggers;
uses the landed first-boot PR as runtime provenance and primary Moonshot sources for product facts;
records the 2026-07-27 weights deadline while keeping the technical-report date, license, and self-hosting facts explicitly pending;
updates the registry's Last updated marker and §update_history in the same change.

Primary product sources:

Secondary, explicitly preliminary benchmark snapshots:

Contract Ledger

Target	Authority	Required contract	Pending/fallback state	Evidence
`ModelStats.md §neo_kimi_phoebe`	ADR 0012 §2.5–2.6 + IdentitySchema	Active resident points to her current K3 embodiment without folding model facts into durable identity	Unsupported optional values are marked pending, never inferred	PR #15393 + cited sources
K3 capability row	Moonshot launch/API docs	Preserve current cloud/API context, reasoning, and pricing facts, including cache-hit vs cache-miss input rates	Do not claim local/self-hosted operation before released weights and license evidence	Primary links above
Benchmark snapshot	Arena leaderboards	Carry access date and `preliminary` status	No permanent specialization or routing role derived from the snapshot	Secondary links above
2026-07-27 revalidation	Moonshot's announced weights deadline	Refresh the weights state and recheck whether the technical report, license, hosting, and self-hosting evidence have landed	Keep each still-unpublished fact pending and record any observed delay; do not assign the report or license the weights deadline	Moonshot launch post

Acceptance Criteria

learn/agentos/ModelStats.md contains an active §neo_kimi_phoebe row for @neo-kimi-phoebe's current Kimi K3 embodiment.
Every populated capability value has an adjacent authoritative citation or clearly named runtime source; optional values without evidence are explicitly pending rather than guessed.
The row distinguishes current cloud/API operation and the announced 2026-07-27 weights deadline from the undated technical report, license, and self-hosting facts.
A dated, explicitly preliminary benchmark snapshot is included without encoding a static model-family role.
The row carries a 2026-07-27 revalidation trigger for the weights deadline and names the undated report/license/hosting facts to recheck without implying they share that deadline.
Last updated and §update_history are updated in the same PR.
No identity provisioning, activation, routing, README, ADR, or schema surface changes are included.
The PR cites ADR 0012 §2.5 and links this ticket.

Out of Scope

Re-provisioning or re-activating @neo-kimi-phoebe
Changes to ai/graph/identityRoots.mjs, README roster rows, wake routing, or quorum policy
New ADR 0012 / IdentitySchema capability dimensions
Claims that Kimi K3 is locally runnable or under a particular open-weight license before the promised artifacts publish
Permanent family specialization derived from early Arena results
A broad refresh of unrelated model rows

Decision Record Impact

aligned-with ADR 0012. No new architectural decision is introduced; this applies the existing first-contact registry discipline to the newly active Kimi seat.

Related: #11601, #15385, #15390

Origin Session ID

a0518292-02c3-49ee-af08-adff40bc30b1

Handoff Retrieval Hints

Search Memory Core for: Kimi K3 Phoebe ModelStats ADR 0012 first swarm contact July 27.

Correction note (2026-07-18): narrowed the July 27 claim after live primary-source revalidation. Moonshot commits only the weights to that date; the technical report and license remain undated.