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	11836
title	Sub 4: Sibling daemon propagation of masterclass-reference pattern (5-6 daemon files)
state	Closed
labels	enhancementairefactoringarchitecture
assignees	neo-gpt
createdAt	May 23, 2026, 1:22 PM
updatedAt	Jun 7, 2026, 7:14 PM
githubUrl	https://github.com/neomjs/neo/issues/11836
author	neo-opus-ada
commentsCount	2
parentIssue	11831
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 6, 2026, 11:51 PM

Sub 4: Sibling daemon propagation of masterclass-reference pattern (5-6 daemon files)

Closed v13.0.0/archive-v13-0-0-chunk-13 enhancementairefactoringarchitecture

neo-opus-ada commented on May 23, 2026, 1:22 PM

Parent Epic

#11831 — Sub 4 of 6 (parallel after Sub 1 sets the masterclass-reference).

Scope

Propagate the 4-way Service-DI classification + 2-value chain + Neo.util.Env consumption pattern to sibling daemon files. May decompose into per-daemon sub-tickets if review burden warrants.

Acceptance Criteria

For each daemon file:

Drop cargo-cult _-suffix configs (no hooks → no _).
Lazy getters for operator policy values: Env.parseNumber(process.env.X, 'X') ?? AiConfig.namespace.X.
Class-system-managed collaborators with ClassSystemUtil.beforeSetInstance(value, DefaultClass, defaults) where applicable.
Parent-configured child collaborators with beforeSet* + parent afterSet* propagation hooks where applicable.
Per-file test refactor parallels Sub 2's test-fixture pattern.

Target daemon files

ai/daemons/services/SwarmHeartbeatService.mjs
ai/daemons/services/KbAlertingService.mjs (recently normalized in PR #11813; verify shape matches)
ai/daemons/services/KbReconciliationService.mjs
ai/daemons/services/KbGarbageCollectionService.mjs
ai/daemons/services/GapInferenceEngine.mjs
(Per-file audit may surface additional candidates)

Decomposition decision

If review burden for all 5-6 daemons in one PR exceeds the §7.5 unit-test-budget envelope: decompose into Sub 4a/4b/etc per-daemon. Default: try one consolidated PR; split if cycle-burden surfaces.

Authored by: [Claude Opus 4.7] (Claude Code)

tobiu referenced in commit 7e7adb2 - "refactor(agentos): delete obsolete CadenceEngine.parseInterval + PrimaryRepoSyncService.parseEnabledFlag (#11835) (#11843) on May 23, 2026, 3:28 PM

tobiu referenced in commit aef235c - "refactor(agentos): drop hookless daemon config suffixes (#11836) (#12657)" on Jun 6, 2026, 11:51 PM

tobiu closed this issue on Jun 6, 2026, 11:51 PM