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	feat(agentos): bump swarmHeartbeatMs default 5m → 15m (#11840)
author	neo-opus-ada
state	Merged
createdAt	May 23, 2026, 2:19 PM
updatedAt	May 23, 2026, 2:39 PM
closedAt	May 23, 2026, 2:39 PM
mergedAt	May 23, 2026, 2:39 PM
branches	`dev` ← `tobiu/11840-swarm-heartbeat-15m`
url	https://github.com/neomjs/neo/pull/11841

Merged

neo-opus-ada commented on May 23, 2026, 2:19 PM

Authored by Claude Opus 4.7 (Claude Code). Session 5572d9a5-558d-4bea-b416-e31496c289c4.

FAIR-band: in-band [verify @ merge-gate]

Resolves #11840

Summary

1-line data-only tuning: ai/config.template.mjs:87 orchestrator.intervals.swarmHeartbeatMs from 5 * 60 * 1000 (5m) to 15 * 60 * 1000 (15m).

Per @tobiu: current wake-substrate pulse is too frequent; 15m reduces wakeup noise without losing operationally-useful cadence.

Substrate context

swarmHeartbeatMs is the folded-in wake-substrate pulse (per #11766) — the canonical heartbeat driving SwarmHeartbeatService.pulse() + downstream idleOutNudge. Not the same as summarySweepMs (summarization cycle) or primaryDevSyncMs (git sync cycle); those concerns stay at their current defaults.

Deltas from ticket

Ticket scope was "1-line config bump" but actually requires 2-line change (config + paired Tier 1 Config Immutability assertion) since the suite locks default values intentionally. Discovered on first CI run when the toMatchObject assertion broke. Commit 9e72b749c syncs the test.

Evidence: L1 (config value + immutability-suite assertion) — required L1 covered; no runtime behavior surface beyond cadence delta.

Test Evidence

npm run test-unit -- test/playwright/unit/ai/config.template.spec.mjs → 3/3 pass (506ms) including the Tier 1 Config Immutability toMatchObject assertion locked at the new swarmHeartbeatMs: 15 * 60 * 1000 default
Tier 1 Config Immutability suite is the substrate-discipline guard that catches silent default drift (worked exactly as designed — caught the initial unsynced assertion on first CI run; commit 9e72b749c re-locks at the new canonical)
git diff origin/dev -- ai/config.template.mjs → 1 line changed (swarmHeartbeatMs : 5 * 60 * 1000 → 15 * 60 * 1000), no other interval values touched
Existing NEO_ORCHESTRATOR_SWARM_HEARTBEAT_MS env-var override mechanism unchanged (no env-handling code touched)

Post-Merge Validation

Operator observes reduced wake-message frequency on the @neo-opus-ada / @neo-gpt mailbox (15m cadence instead of 5m)
No regression in idle-out detection (15m is still well below typical agent idle-out windows)

github-actions commented on May 23, 2026, 2:19 PM

🚨 Agent PR Body Lint Violation

@neo-opus-ada — your PR body on PR #11841 does not match the pull-request template structure.

Required action: read .agents/skills/pull-request/SKILL.md BEFORE editing the PR body. The skill points at:

Minimum-viable PR body structure: .agents/skills/pull-request/references/pull-request-workflow.md §9
Self-Identification mandate: .agents/skills/pull-request/references/pull-request-workflow.md §5

Do NOT compose a substitute template or hallucinate section headings. The validator checks more structural anchors than this comment names. The only reliable path to passing is reading the actual workflow file and following its structure.

Diagnostic hint: at least one recognized anchor like ## Test Evidence is missing.

Visible anchors missing (full list)

## Test Evidence

_{This is the CI tool-boundary lint companion to PR #11494's MCP manage_pr_review validator and PR #11502's agent-pr-review-body-lint.yml reviewer-side lint.
Resolves #11501.}

tobiu APPROVED reviewed on May 23, 2026, 2:39 PM

No review body provided.