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.

Neo.mjs - Self-Evolving Software Organism

Frontmatter

title	refactor(ai): read AiConfig graph leaf directly (#12464)
author	neo-gpt
state	Closed
createdAt	Jun 4, 2026, 3:36 AM
updatedAt	Jun 4, 2026, 3:46 AM
closedAt	Jun 4, 2026, 3:46 AM
mergedAt
branches	`dev` ← `codex/12464-aiconfig-analyze-nl-telemetry`
url	https://github.com/neomjs/neo/pull/12468

Closed

neo-gpt commented on Jun 4, 2026, 3:36 AM

Resolves #12464 Related: #12456 Related: #12438

Authored by GPT-5 (Codex Desktop). Session 032b788b-aac0-40ae-9a48-f595ffb3e4e8. FAIR-band: over-target [20/30] — taking this lane despite over-target because the operator restored GPT capacity, both Claude lanes were active or winding down, and #12464 is a narrow unassigned micro-split that avoids collision with #12435/#12451/#12461/#12462.

Drops the redundant process.env.NEO_MEMORY_DB_PATH || fallback in ai/scripts/diagnostics/analyzeNlTelemetry.mjs. The script already imports the Memory Core AiConfig provider, and storagePaths.graph already binds NEO_MEMORY_DB_PATH through the leaf declaration, so the direct leaf read keeps behavior equivalent while aligning with ADR 0019.

Evidence: L1 (static source/syntax check) → L1 required (behavior-equivalent direct AiConfig leaf read; no runtime-only ACs). No residuals.

Deltas from ticket

None — implements the ticket prescription exactly.

Decision Record impact

aligned-with ADR 0019.

Test Evidence

node --check ai/scripts/diagnostics/analyzeNlTelemetry.mjs
git diff --check
rg -n "process\.env\.NEO_MEMORY_DB_PATH \|\| aiConfig\.storagePaths\.graph|const DB_PATH = aiConfig\.storagePaths\.graph" ai/scripts/diagnostics/analyzeNlTelemetry.mjs returned only the direct leaf read.
Commit hook ran check-whitespace, check-shorthand, and check-ticket-archaeology successfully.

Post-Merge Validation

None required; the close-target ACs are satisfied by the static source change plus syntax validation.

neo-gpt commented on Jun 4, 2026, 3:45 AM

Input from GPT-5 (Codex Desktop):

● [REJECTED_WITH_RATIONALE]

Withdrawing this PR. The operator rejected the lane, and the rejection is valid: this was a V-B-A failure by the author. I accepted #12464 as a micro-ticket and opened a 1-line PR that spent the full CI matrix, instead of rejecting the ticket as flawed/under-scoped after accounting for the graph history, related Discussions, and adjacent open tickets.

Do not review or merge #12468. Closing the PR and routing #12464 to not-planned/needs-re-triage.