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	12444
title	Reshape stale-yield into a capability-transfer diagnostic
state	Closed
labels	enhancementaiarchitecturemodel-experience
assignees	neo-gpt
createdAt	Jun 3, 2026, 8:46 PM
updatedAt	Jun 4, 2026, 8:23 PM
githubUrl	https://github.com/neomjs/neo/issues/12444
author	neo-opus-grace
commentsCount	1
parentIssue	12440
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 4, 2026, 8:23 PM

Reshape stale-yield into a capability-transfer diagnostic

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementaiarchitecturemodel-experience

neo-opus-grace commented on Jun 3, 2026, 8:46 PM

Sub-ticket of Epic #12440 (Liveness-first authorship substrate). Graduated from Discussion #12429 (OQ1 + the anti-reconcentration guard).

Scope

Demote the stale-yield mechanism (Discussion Option D) from a balance mechanism to a diagnostic that classifies WHY a yielded lane is blocked and routes to liveness / capability-transfer — not re-assignment.

Acceptance Criteria

Stale-yield reshaped as a diagnostic: classify the block as missing-context / missing-wake-presence / capability-debt.
Route the diagnosis to a bounded capability-transfer artifact (context capsule, narrowed first-PR slice, avoided-traps note, exact files, evidence ladder) that changes the under-author's cost curve — NOT re-recommendation or assignment.
Anti-reconcentration guard: re-shaper concentration tracked separately (else the monoculture relocates from authoring to re-shaping).
Capability-debt recorded against the OQ2 floor (#12440 capability-floor sub) when ONLY the over-author can produce the re-shaping artifact.

Rationale (from #12429)

With 1–2 awake authors the yield doesn't redistribute, it routes onto whoever's awake ("it didn't balance, it routed"). So the protocol's real job is diagnosis — is the lane blocked by missing context, missing wake-presence, or real capability debt? Demoted from primary-fix to diagnostic/recovery path.

Origin: Discussion #12429 → Epic #12440. Session e886ae3e-13c0-4a94-9713-f8316e2342d0.

tobiu referenced in commit ccc174f - "feat(agentos): define the authorship-capability floor + family-going-cold detector (#12445) (#12492) on Jun 4, 2026, 1:55 PM

tobiu referenced in commit 841d07f - "feat(agentos): define stale-yield diagnostic (#12444) (#12525) on Jun 4, 2026, 8:23 PM

tobiu closed this issue on Jun 4, 2026, 8:23 PM