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	14055
title	#14030 AC1 producer-core: supervised-task failure/overdue diagnosis helpers
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-vega
createdAt	Jun 26, 2026, 6:03 AM
updatedAt	Jun 26, 2026, 9:31 AM
githubUrl	https://github.com/neomjs/neo/issues/14055
author	neo-opus-vega
commentsCount	0
parentIssue	14030
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[ ] 14064 Consume supervised-task diagnosis helper in backup escalation
closedAt	Jun 26, 2026, 9:31 AM

#14030 AC1 producer-core: supervised-task failure/overdue diagnosis helpers

Closed v13.1.0/archive-v13-1-0-chunk-6 enhancementaiarchitecture

neo-opus-vega commented on Jun 26, 2026, 6:03 AM

Context

#14030 AC1 (alert on backup failure/overdue) converged with @neo-gpt (https://github.com/neomjs/neo/issues/14030#issuecomment-4806173915): a sibling task-diagnostics producer (NOT bolted into ContainerHealthDiagnosisService, NOT a pageable recovery-actuator target) that emits a recovery-diagnosis event with targetIdentity:{kind:'supervised-task', id} + details.actionClass:'escalate', routed through a narrow diagnosis-escalation sink.

The Fix (this slice — the producer-core)

Pure functions in ai/daemons/orchestrator/services/taskOutcomeDiagnosis.mjs:

detectTaskOverdue({lastRunAt, intervalMs, graceMs, now}) → {overdue, overdueByMs} (interval<=0 disables).
buildSupervisedTaskDiagnosis({taskName, outcome, observedAt, details}) → a recovery-diagnosis event (via the existing createRecoveryDiagnosisEvent contract): failed→crash, overdue→ambiguous recovery class; supervised-task targetIdentity; actionClass:'escalate'. Never restarts/retries — detection only.

Acceptance Criteria

detectTaskOverdue returns the overdue verdict (past lastRunAt+intervalMs+graceMs); <=0 interval never overdue.
buildSupervisedTaskDiagnosis emits a contract-valid recovery-diagnosis event (supervised-task identity, escalate actionClass, crash/ambiguous class) and rejects invalid outcomes/missing taskName.
Unit coverage for both.

Out of Scope (the next AC1 slice — live wiring)

The ProcessSupervisorService.recordTaskOutcome('<task>','failed', …) hook (line 412 etc.) calling the producer for the alert-on-failure task set.
The scheduling-loop overdue check (scheduling/backup.mjs lastRunAt+interval) calling detectTaskOverdue.
The narrow escalateDiagnosis(diagnosisEvent) sink in RecoveryActuatorService (NOT apply('backup','page') — page is deploy-target-only).

Contract Ledger Matrix

Consumed surface	Field	Type / values	Change	Consumer impact	Fallback / semantics
`detectTaskOverdue()` return (exported from `taskOutcomeDiagnosis.mjs`)	verdict	`overdue: Boolean` · `overdueByMs: Number` (≥0)	New exported function (additive)	Intended consumer: the scheduling-loop overdue check (next slice) → feeds `buildSupervisedTaskDiagnosis`.	Pure; `intervalMs <= 0` ⇒ `{overdue:false, overdueByMs:0}` (periodic disabled); absent `lastRunAt` treated as 0.
`buildSupervisedTaskDiagnosis()` return	`recovery-diagnosis` event	conforms to `createRecoveryDiagnosisEvent`: `type:'recovery-diagnosis'` · `recoveryClass: 'crash'` (failed) / `'ambiguous'` (overdue) · `targetIdentity:{kind:'supervised-task', id}` · `confidence:1` · `details.actionClass:'escalate'` + `details.outcome`	New exported function (additive); reuses the existing `recovery-diagnosis` wire contract	Intended consumer: the `escalateDiagnosis` sink (next slice). Producer-only — emits the event; never restarts/retries.	Throws `TypeError` on invalid `outcome` (not `failed`/`overdue`) or missing `taskName`.

Docs: both functions' JSDoc documents the verdict/event shapes + the detection-only (no restart/retry) guarantee.
Evidence: L2 unit — detectTaskOverdue verdicts + the failed→crash / overdue→ambiguous event shapes + invalid-input rejection.

#14030 — parent (AC1); #14039 — v13.1 epic. AC2 (#14053) / AC3 stay separate.

Authored-by: @neo-opus-vega (Vega, Claude Opus 4.8)

tobiu referenced in commit 0c6ca39 - "feat(ai): supervised-task failure/overdue diagnosis producer-core (#14055) (#14056) on Jun 26, 2026, 9:31 AM

tobiu closed this issue on Jun 26, 2026, 9:31 AM