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	14106
title	Accepted-loss residue classifier + terminal-reason taxonomy (#14084 leaf 1)
state	Closed
labels	enhancementaiarchitecture
assignees	neo-opus-grace
createdAt	Jun 26, 2026, 4:23 PM
updatedAt	Jun 26, 2026, 5:43 PM
githubUrl	https://github.com/neomjs/neo/issues/14106
author	neo-opus-grace
commentsCount	0
parentIssue	14084
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 26, 2026, 5:43 PM

Accepted-loss residue classifier + terminal-reason taxonomy (#14084 leaf 1)

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

neo-opus-grace commented on Jun 26, 2026, 4:23 PM

Context

#14084 leaf 1 (the graduated converged design — see the #14084 graduation comment). The Memory Core repair reports perpetual exit 1 even when its only residue is genuinely-unembeddable + operator-acknowledged. The heart of the fix is a pure decision: given a repair's unrecoverable residue + a durable acknowledgement, is this accepted-loss (terminal + ack-matched) or must it escalate (transient, or un-acknowledged/stale)?

The Architectural Reality

The detect-producer pure-fn pattern (dataIntegrityCoverageDiagnosis.mjs / sqliteIntegrityDiagnosis.mjs / storeBloatDiagnosis.mjs) is the shape to mirror: injected inputs → a verdict, no I/O, unit-testable in isolation.
The fingerprint inputs are fixed by @neo-gpt's strategy-fingerprint AC: residue (ids + reasonCodes) + provider/model/context-budget + the active-recovery-strategy version + the sorted terminality-policy set (terminalReasons) (added in PR #14108 review — the ack must go stale on a policy/capability change, not only a residue change). The durable ack RECORD + the operator-ack surface are leaf 2; the defragChromaDB.mjs wiring is leaf 3.

The Fix

A pure classifyRepairResidue({residue, ack, strategyVersion, provider, contextBudget, terminalReasons}):

escalate when ANY residue row's reason is NOT in the terminal whitelist (transient/unknown must always escalate).
else (all-terminal) compute a stable fingerprint over the residue + strategy/provider/context + the sorted terminality-policy set (terminalReasons); accepted-loss iff ack is present AND ack.fingerprint === currentFingerprint; else escalate (un-acknowledged or stale ack).
Returns {outcome, reasonCode, fingerprint, nonTerminalReasons}; pure + deterministic (the fingerprint is a stable hash, no Date/randomness).
A frozen TERMINAL_REASONS default (embedding-context-exceeded, document-absent); transient reasons never qualify.

Acceptance Criteria

All-terminal residue + matching ack.fingerprint → accepted-loss.
Any non-terminal (transient/unknown) reason → escalate (regardless of ack).
All-terminal but no ack, or stale ack (fingerprint mismatch) → escalate.
The fingerprint is stable/deterministic over (sorted residue ids+reasons, strategyVersion, provider, contextBudget, sorted terminalReasons policy set) — order-independent, no time/randomness. A terminality-policy-only change (residue terminal under both the old and new policy) invalidates a stale ack → escalate.
Empty residue → not escalate (no loss to escalate); a distinct no-residue outcome (the caller treats as clean).
Pure: no I/O, no mutation; unit-covered for each branch.

Contract Ledger Matrix

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`classifyRepairResidue({residue, ack, strategyVersion, provider, contextBudget, terminalReasons})`	#14084 graduated design + @neo-gpt strategy-fingerprint AC	`accepted-loss \| escalate \| no-residue` verdict + stable fingerprint over `(sorted residue ids+reasons, strategyVersion, provider, contextBudget, sorted terminalReasons policy set)`	non-terminal → escalate; missing/stale ack → escalate; terminality-policy change → escalate; empty residue → no-residue	module + fn JSDoc	unit spec per branch
`TERMINAL_REASONS` (frozen)	#14084 reason-taxonomy	`embedding-context-exceeded`, `document-absent`; shared with the diagnosis `reasonCode` vocabulary	n/a	JSDoc	spec

Out of Scope

The durable ack record + operator-ack surface (leaf 2).
The defragChromaDB.mjs outcome wiring + the terminal diagnosis (leaf 3).

#14084 (parent — the graduated design), #14026 (the detect signal the ack suppresses), #14066 (the partial-promote contract this refines), #14085 (the residue-shrinking Prevent sibling), #14039.

Live latest-open sweep: checked latest open + the #14084 leaf set at 2026-06-26T14:22Z; no accepted-loss-classifier leaf exists. A2A: #14084 graduation comment posted; design hand-off from @neo-opus-vega.

Origin Session ID: 5ab545e1-f09e-46c5-ae62-8cf5b2b96193

Handoff Retrieval Hints: query_raw_memories("accepted-loss residue classifier terminal-reason fingerprint escalate"); anchors: the data-integrity detect-producer pure-fn pattern, #14084 graduation comment.