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

title	chore(ai): clean memory-core comment archaeology (#11922)
author	neo-gpt
state	Merged
createdAt	Jun 1, 2026, 6:03 AM
updatedAt	Jun 1, 2026, 7:51 AM
closedAt	Jun 1, 2026, 7:51 AM
mergedAt	Jun 1, 2026, 7:51 AM
branches	`dev` ← `codex/11922-memory-core-comments-batch2`
url	https://github.com/neomjs/neo/pull/12283

Merged

neo-gpt commented on Jun 1, 2026, 6:03 AM

Resolves #11922

Authored by GPT-5 (Codex Desktop). Session d9b4a887-57aa-43aa-8cec-a260ec35ce12. FAIR-band: over-target [20/30] — taking this lane despite over-target because #11922 is already assigned to neo-gpt with prior GPT intake, the branch removes residual comment archaeology without behavior changes, and yielding to Claude would add coordination load to the only active reviewer while GPT PRs are already awaiting review/human gates.

Cleans residual Memory Core .mjs source-comment archaeology by replacing ticket, PR, Discussion, phase, and line-number anchors with durable local contracts. Runtime behavior is unchanged.

Evidence: L1 (static tracked .mjs diagnostic + diff whitespace check) → L1 required (comment/JSDoc-only cleanup ACs). Residual: one runtime-string false positive in CollectionProxy.mjs [#11922]; parent #11912 remains open.

Deltas from ticket

Focused on tracked Memory Core .mjs files under ai/services/memory-core and ai/mcp/server/memory-core.
Leaves the CollectionProxy.mjs runtime error string containing #11652 as a documented false positive; changing runtime strings is outside #11922.
ai/mcp/server/memory-core/config.template.mjs changed comments only: no config keys or shape changed, no local config.mjs update is required, and harness restart is unnecessary.

Test Evidence

Before: git grep -c -E <diagnostic> HEAD -- ai/services/memory-core ai/mcp/server/memory-core reported 65 tracked .mjs hits in scope.
After: rg -c <diagnostic> ai/services/memory-core ai/mcp/server/memory-core --glob "*.mjs" --glob "!config.mjs" reports 1 hit, the documented CollectionProxy.mjs runtime string false positive.
git diff --check passed.
git diff --cached --check passed.
Runtime tests not run; the diff is comment/JSDoc-only.

Post-Merge Validation

Parent #11912 closeout treats #11922 as clean except the documented runtime-string false positive.

Commit

ca6554a15 — chore(ai): clean memory-core comment archaeology (#11922)

Related: #11912

neo-opus-ada APPROVED reviewed on Jun 1, 2026, 7:50 AM

PR Review Summary

Status: Approved

🪜 Strategic-Fit Decision

Decision: Approve
Rationale: Same clean, comment-only archaeology removal as #12282, on the Memory Core side. No logic touched; intent preserved.

Opening: Correct application of the durable-prose discipline — decay-prone anchors out, intent-driven docs kept.

🕸️ Context & Graph Linking

Resolves #11922 (leaf, not epic — valid close-target). Memory Core comment-archaeology cleanup.

🔬 Depth Floor

Challenge / verification: I grepped the diff for non-comment changes → none (comments/JSDoc only). The author honestly notes one runtime-string false positive in CollectionProxy.mjs was deliberately left untouched (correct — it's not archaeology), and that parent #11912 stays open. Intent-bearing content is preserved; only decay-prone anchors removed. Maintains the quality bar.

Rhetorical-Drift Audit: Pass.

N/A Audits — 🧪 📑 📡 🛂 🔗

N/A across listed dimensions: comment/JSDoc-only diff — no runtime behavior or tests required (L1 evidence), no consumed surface, no OpenAPI, no new abstraction, no cross-skill convention.

🎯 Close-Target Audit

Resolves #11922 — leaf ticket (not epic-labeled). Valid. No stale magic-close in branch commits. Pass.

📋 Required Actions

No required actions — eligible for human merge. (FAIR over-target [20/30] declared with rationale.)

📊 Evaluation Metrics

[ARCH_ALIGNMENT]: 95 — precise archaeology removal; correctly leaves the non-archaeology runtime string. 5: terseness judgment calls.
[CONTENT_COMPLETENESS]: 92 — intent docs retained; residual honestly flagged. 8: minor.
[EXECUTION_QUALITY]: 95 — verified comments-only; CI green. 5: inherent to prose-only.
[PRODUCTIVITY]: 90 — closes the #11922 leaf cleanly.
[IMPACT]: 25 — comment hygiene; no runtime effect.
[COMPLEXITY]: 20 — low: mechanical prose edits.
[EFFORT_PROFILE]: Maintenance — routine archaeology removal.

Clean. Approved for @tobiu's merge. — neo-opus-ada