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	12445
title	Define the authorship-capability floor + family-going-cold detector
state	Closed
labels	enhancementaimodel-experience
assignees	neo-opus-ada
createdAt	Jun 3, 2026, 8:46 PM
updatedAt	Jun 4, 2026, 1:54 PM
githubUrl	https://github.com/neomjs/neo/issues/12445
author	neo-opus-grace
commentsCount	0
parentIssue	12440
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
blockedBy	[]
blocking	[]
closedAt	Jun 4, 2026, 1:54 PM

Define the authorship-capability floor + family-going-cold detector

Closed v13.0.0/archive-v13-0-0-chunk-15 enhancementaimodel-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 (OQ2 — the objective).

Scope

Define the authorship-capability floor (the liveness-first substrate's primary objective) + a detector for a maintainer family going cold in critical state-mutating substrate.

Acceptance Criteria

Authorship-capability floor defined: no active maintainer family may remain structurally unable or cold to author in a critical (state-mutating) substrate area for too long.
"Family-going-cold-in-critical-substrate" detector defined (anti-monoculture in state-mutating work).
Risk framing encoded: primary = bus-factor + skill-atrophy in state-mutating work; secondary = perspective-monoculture; explicit NON-risk = contribution-imbalance by itself.

Rationale (from #12429)

OQ2 reframed the objective away from raw authorship-count (satisfiable by padding) to a capability floor + anti-monoculture in state-mutating work. This is the standing objective the detector (sub #1) and the diagnostic (sub #2) serve.

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

Contract Ledger

Agent-consumed governance surface (.agents/skills/post-review-pickup/**):

Target Surface	Source of Authority	Proposed Behavior	Fallback	Docs	Evidence
`authorship-capability-floor.md` (new)	#12445 (design #12429 OQ2)	define the capability floor + family-going-cold-in-critical-substrate detector + risk framing (primary / secondary / explicit non-risk)	telemetry never a gate; routes to capability-transfer (#12444)	yes	lint-skill-manifest OK; sibling < 25 KB
`author-concentration-detector.md` (pointer)	#12445	concrete pointer to the floor file (replacing a forward ticket-ref)	—	yes	lint OK

tobiu closed this issue on Jun 4, 2026, 1:55 PM

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