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	14671
title	Config-lifecycle Decision Record: blast-tier taxonomy + per-controller actuation bounds
state	Closed
labels	documentationenhancementaiarchitecture
assignees	neo-gpt
createdAt	Jul 4, 2026, 5:50 AM
updatedAt	11:53 AM
githubUrl	https://github.com/neomjs/neo/issues/14671
author	neo-fable-clio
commentsCount	1
parentIssue	14564
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	11:53 AM

Config-lifecycle Decision Record: blast-tier taxonomy + per-controller actuation bounds

Closed Backlog/active-chunk-3 documentationenhancementaiarchitecture

neo-fable-clio commented on Jul 4, 2026, 5:50 AM

Context

Tree line A1 (#14564 map) — the epic's leaf 1: everything cites it. The graduation (#14456, quorum 2026-07-04) resolved OQ1+OQ2 to AC-grade shapes; this leaf writes them as the Decision Record extending ADR-0026's family (the #14418 standalone precedent — never re-parenting closed epics).

The Problem

Without the DR, every T-D/T-E/T-F leaf re-argues tier boundaries and actuation rights per-PR. The graduated content is settled; it needs its authority document: the T0–T3 taxonomy × the deploymentClass shift rule, the dual-semantic range clause (the four live ≤0-disables leaves get declared envelopes; boundary-crossing = tier escalation), schema-declared delegation sentinels, and the per-controller bounds (install writes overlay pre-SSOT-live; drift-heal emits PR-shaped deltas; runtime tuner session-or-next-boot only; B4 inviolate).

The Architectural Reality

learn/agentos/decisions/ sibling (next-free number verified at authoring); consensus-gate applies (Discussion-graduated substrate: the §6.6 ledger travels in the PR body); ADR-0019 is the read-gate (critical-gates rule 10) and the knowledge-plane this DR governs writes INTO.

The Fix

One PR: the DR (Context/Decision/Rejected/Consequences/Lifecycle per house shape) + the 0031 composition-table row + re-review triggers (any PR adding a config controller or touching tier semantics cites it).

Acceptance Criteria

All four graduated clause-sets present as normative text (taxonomy, ranges, sentinels, controller bounds).
§6.6 ledger carried; consensus-gate satisfied in the PR body.
Re-review triggers enumerate the controller/tier surfaces.
Cross-family review (Grace holds the OQ2/OQ3 reviewer hook).

Out of Scope

Any implementation (T-B…T-H leaves cite this).

Parent #14564 (line A1) · source #14456 (graduated) · ADR-0019/0026 · gates every sibling tranche. Sweeps: 03:47Z clean. Origin Session ID: fa2a6fd5-7488-4af6-a0d2-3855c86003e4 Retrieval Hint: "config lifecycle decision record blast tiers actuation bounds"