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	14197
title	Remove duplicate dead synthesizeGoldenPath() in DreamService (shadowed by a later def + broken ./services/ import)
state	Closed
labels	airefactor(ai)
assignees	neo-opus-ada
createdAt	Jun 27, 2026, 5:36 AM
updatedAt	Jun 27, 2026, 9:21 AM
githubUrl	https://github.com/neomjs/neo/issues/14197
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 27, 2026, 9:21 AM

Remove duplicate dead synthesizeGoldenPath() in DreamService (shadowed by a later def + broken ./services/ import)

Closed v13.1.0/archive-v13-1-0-chunk-7 airefactor(ai)

neo-opus-ada commented on Jun 27, 2026, 5:36 AM

Surfaced by a tech-debt-radar Vector-C sweep (2026-06-27).

The debt

ai/daemons/orchestrator/services/DreamService.mjs defines async synthesizeGoldenPath() twice:

Line 1034 — @deprecated passthrough that dynamically imports './services/GoldenPathSynthesizer.mjs'. But DreamService is already in ai/daemons/orchestrator/services/, so that path resolves to .../services/services/GoldenPathSynthesizer.mjs — a double-services/ that doesn't exist (confirmed: no such dir). So this method is BROKEN (would throw ERR_MODULE_NOT_FOUND if reached).
Line 1140 — a second @deprecated passthrough using the module-level GoldenPathSynthesizer import; "kept for backward compatibility and test stability."

In JS, the second method shadows the first — so line 1034 is unreachable dead code (and broken). The active method is 1140; the DreamService tests (DreamService.spec.mjs:2335/2357, DreamServiceGoldenPath.spec.mjs:82) call DreamService.synthesizeGoldenPath() → JS resolves to 1140. The real production callers use GoldenPathSynthesizer.synthesizeGoldenPath() directly (pipeline.mjs:560, MemoryService.mjs:2082).

The fix

Delete the dead duplicate at lines 1030–1038 (the JSDoc + the shadowed, broken-import synthesizeGoldenPath()). Keep 1140 (the active, test-covered one). Zero behavior change — 1034 is unreachable; tests + production callers are unaffected.

Acceptance Criteria

The duplicate synthesizeGoldenPath() at ~1034 (+ its JSDoc + broken ./services/ import) is removed; one definition remains.
DreamService + DreamServiceGoldenPath specs stay green (they exercise the surviving 1140).

Bounded dead-code removal — no data, no governance, no gate.

🤖 Authored by Ada (@neo-opus-ada · Claude Opus 4.8, Claude Code) via tech-debt-radar Vector-C.

tobiu referenced in commit 52fef9d - "refactor(ai): remove duplicate dead synthesizeGoldenPath() in DreamService (#14197) (#14200) on Jun 27, 2026, 9:21 AM

tobiu closed this issue on Jun 27, 2026, 9:21 AM