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	12109
title	Remove KB health table from Sandman handoff
state	Closed
labels	bugairegression
assignees	neo-gpt
createdAt	May 27, 2026, 10:31 PM
updatedAt	May 27, 2026, 11:09 PM
githubUrl	https://github.com/neomjs/neo/issues/12109
author	neo-gpt
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	May 27, 2026, 11:09 PM

Remove KB health table from Sandman handoff

Closed v13.0.0/archive-v13-0-0-chunk-14 bugairegression

neo-gpt commented on May 27, 2026, 10:31 PM

Context

The operator verified that resources/content/sandman_handoff.md must keep the Dream Pipeline / Golden Path handoff format focused on capability-gap categories and the strategic interpretation. The ## KB Multi-Tenant Health Markdown table added by #11639 / PR #11708 does not belong in that operator-facing handoff surface.

The Problem

The table interrupts the Sandman handoff with low-level KB telemetry and hides the expected shape operators and agents look for: Guide Disconnects, Example Disconnects, Orphaned Concepts, Concept Reverification Queue, Active PR Cycle State when applicable, Golden Path recommendations, and Strategic Interpretation.

The Architectural Reality

GoldenPathSynthesizer.synthesizeGoldenPath() is the single writer for resources/content/sandman_handoff.md. It currently imports and appends renderKbMultiTenantHealthSection() from KbTenantHealthHelper.mjs, which creates the table. The KB helper can remain available for KB observability tests or a future correct surface; the Sandman handoff should stop composing it.

The Fix

Remove the KB Multi-Tenant Health composition block from ai/services/graph/GoldenPathSynthesizer.mjs. Adjust tests so the Sandman handoff generation path asserts the KB table is absent.

Acceptance Criteria

GoldenPathSynthesizer.synthesizeGoldenPath() no longer imports or appends renderKbMultiTenantHealthSection().
Generated sandman_handoff.md output no longer contains ## KB Multi-Tenant Health.
Existing capability-gap sections and Golden Path output remain unchanged.
Targeted unit coverage passes.

Out of Scope

Runtime config overlay migration.
Strategic Interpretation provider repair.
Latest Priority Backlog recursion.
Removing the KB telemetry recorder itself.

Supersedes the Sandman-handoff surface portion of #11639 / PR #11708.

Origin Session ID: 6ca1b510-51c3-4fac-aa39-a0fd6941318c

Handoff Retrieval Hint: sandman_handoff KB Multi-Tenant Health table GoldenPathSynthesizer #11708 removal

tobiu closed this issue on May 27, 2026, 11:09 PM

tobiu referenced in commit faf3d1f - "fix(ai): remove KB health table from Sandman handoff (#12109) (#12110) on May 27, 2026, 11:09 PM