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	11925
title	Clean daemon script and config source comments
state	Closed
labels	documentationenhancementairefactoringarchitecturemodel-experience
assignees	neo-gpt
createdAt	May 24, 2026, 10:49 PM
updatedAt	Jun 7, 2026, 7:15 PM
githubUrl	https://github.com/neomjs/neo/issues/11925
author	neo-gpt
commentsCount	1
parentIssue	11912
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 2, 2026, 10:16 AM

Clean daemon script and config source comments

Closed v13.0.0/archive-v13-0-0-chunk-13 documentationenhancementairefactoringarchitecturemodel-experience

neo-gpt commented on May 24, 2026, 10:49 PM

Parent epic: #11912

Context

#11912 is being reshaped into an epic with grouped cleanup subissues. This subissue owns daemon, lifecycle-script, maintenance-script, config-template, and residual ai/ source-comment surfaces not covered by the service-group subissues.

Current grouped baseline on origin/dev:

ai/scripts/**/*.mjs: 96 diagnostic matches.
ai/daemons/**/*.mjs: 50 diagnostic matches.
ai/config*.mjs, MCP config templates outside the service-owned groups, and residual ai/**/*.mjs surfaces: remaining high-noise matches after the Memory Core, KB/Graph, and GitHub/shared groups are accounted for.

The Problem

Daemon and script comments often preserve incident history, PR lanes, or AC references directly in executable source. Config templates also accumulate release-era rationale that should be expressed as stable operator-facing contracts.

The Architectural Reality

This group covers long-running process entry points, bridge/wake/KB daemons, migration and maintenance scripts, lint/diagnostic utilities, and residual config templates. These surfaces are operationally sensitive: comments should tell agents and operators what the script/daemon/config owns now, not which historical lane produced it.

The Fix

Clean daemon, script, config-template, and residual ai/ source comments in grouped batches:

Rewrite incident/PR/AC/lane references into stable operational contracts.
Keep exact command names, env vars, config keys, log-message payloads, and public paths when those are current API.
Document false positives and residual runtime strings.
If a residual file belongs more naturally to another subissue during cleanup, move it by comment on #11912 rather than creating a per-file ticket.

Contract Ledger Matrix

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`ai/daemons/*/.mjs` comments/JSDoc	#11912 source-comment cleanup epic	Comments explain daemon ownership, lifecycle, and failure modes in stable terms	Preserve operator-visible runtime strings	PR bodies	Before/after focused diagnostics
`ai/scripts/*/.mjs` comments/JSDoc	#11912 source-comment cleanup epic	Comments explain script contracts, inputs, and safety gates without lane archaeology	File separate bug ticket for executable issues found during cleanup	PR bodies	Before/after focused diagnostics
Config/residual `.mjs` comments/JSDoc	#11912 source-comment cleanup epic	Comments explain stable config/operator contracts	Reassign to a sibling subissue if a residual file belongs there	PR bodies	Before/after focused diagnostics

Decision Record Impact

Aligned with ADR 0005 and ADR 0008. No ADR amendment expected.

Acceptance Criteria

Clean daemon .mjs comments/JSDoc to durable operational intent.
Clean script .mjs comments/JSDoc to durable operational intent.
Clean config-template and residual .mjs comments/JSDoc not covered by other subissues.
Preserve runtime behavior, command names, env vars, config keys, and public paths.
PR evidence includes before/after focused counts and git diff --check.
Parent #11912 remains open until all grouped subissues are complete.

Out of Scope

Service groups covered by the Memory Core, KB/Graph, and GitHub/shared subissues.
Runtime behavior changes.
Generated mirrors and historical docs outside source .mjs comments.

Parent epic: #11912

Origin Session ID: 019e5bac-15f3-7830-a59c-72772c757f9a

Handoff Retrieval Hint: query_raw_memories("11912 daemons scripts config source-comment archaeology")