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	14514
title	Boot-identity fact AC-1: discriminator + gatherer + live REM-watchdog classification
state	Closed
labels	ai
assignees	neo-opus-ada
createdAt	Jul 2, 2026, 11:30 PM
updatedAt	Jul 3, 2026, 12:38 AM
githubUrl	https://github.com/neomjs/neo/issues/14514
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jul 3, 2026, 12:38 AM

Boot-identity fact AC-1: discriminator + gatherer + live REM-watchdog classification

Closed v13.1.0/archive-v13-1-0-chunk-8 ai

neo-opus-ada commented on Jul 2, 2026, 11:30 PM

AC-1 of #14490 (the boot-identity health fact, Leaf 1 of #14477) — split out so PR #14492 truthfully resolves the slice it actually delivers without auto-closing #14490 while AC-2 is still residual.

Scope (delivered by PR #14492)

The pure classifyBootFreshness(facts, config) discriminator + BOOT_FRESHNESS_CLASS / SCHEDULER_RESUME_STATE codebooks (Neo-free, hermetically unit-testable, advisory-only — never a certainty-class stale).
The BootIdentityHealthService advisory scaffold + the live fact-gatherer factory.
The REM-consolidation liveness watchdog integration: a stall carries its boot-freshness disposition (restart-explains / designed-deferral / unknown), reading a recognized, recency-bounded dream maintenance-deferral (a generic skip can never mask a genuine stall) without ever suppressing the alarm.
HealthService#getTaskOutcome read-surface (defensive deep clone).

Out of scope (remains on #14490)

AC-2: expose the fact on the authenticated control-plane surface (R3-safe — the client Bridge RPC receives the read-only fact, never a restart-affecting command). Gated on the #14501 control-plane substrate decision.

Parent: #14490 · Epic: #14477. Delivered by PR #14492.

Authored by Ada (Claude Opus 4.8, Claude Code).

tobiu closed this issue on Jul 3, 2026, 12:38 AM

tobiu referenced in commit d64e25c - "feat(ai): boot-identity fact AC-1 discriminator + live watchdog classification (#14514) (#14492) on Jul 3, 2026, 12:38 AM