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	14175
title	#14150 gate-surface: composeServiceRecoveryEnabled cloudOnly leaf + getter + resolveCloudOnlyEnabled export (the consult-surface for the B1 cutover)
state	Closed
labels	[]
assignees	neo-opus-ada
createdAt	Jun 27, 2026, 2:08 AM
updatedAt	Jun 27, 2026, 2:17 AM
githubUrl	https://github.com/neomjs/neo/issues/14175
author	neo-opus-ada
commentsCount	0
parentIssue	null
subIssues	[]
subIssuesCompleted	0
subIssuesTotal	0
contentTrust
projected
quarantined	0
signals	[]
blockedBy	[]
blocking	[]
closedAt	Jun 27, 2026, 2:17 AM

#14150 gate-surface: composeServiceRecoveryEnabled cloudOnly leaf + getter + resolveCloudOnlyEnabled export (the consult-surface for the B1 cutover)

Closed v13.1.0/archive-v13-1-0-chunk-7 []

neo-opus-ada commented on Jun 27, 2026, 2:08 AM

Context

Substrate-first split of #14150 (symmetric to @neo-opus-grace's #14171/#14166). #14150's full resolution requires the B1 docker-socket recovery path to actually consult a mode-gate — but that consult is cutover-gated (DataIntegrityDiagnosisService is still escalate-only; the B1 apply-path isn't live until @neo-opus-grace's #14134 cutover). So Resolves #14150 from the surface PR would auto-close #14150 with AC1 unmet (the gate exists but nothing reads it).

This sub is the stable surface that lands now, zero-collision with the cutover:

cloudOnly.composeServiceRecoveryEnabled leaf (config.template.mjs) — cloud-on / local-off default, operator-overridable.
Orchestrator.composeServiceRecoveryEnabled getter (mirrors tenantRepoSyncEnabled).
resolveCloudOnlyEnabled exported for the cross-module B1-selection-point consult (ADR-0019-clean).
Orthogonal to recoveryActuator.blockedComposeServices (ADR-26).

Acceptance criteria

Leaf + getter + export present, mirroring the established cloudOnly pattern.
Mode-gate default cloud→enabled / local→disabled, operator-overridable; unit-covered.
Exported resolver consultable cross-module.

Resolved by PR #14170. Refs #14150 (stays open until the #14134 consult wires the gate live). Self-assign @neo-opus-ada. Authored by Ada (Claude Opus 4.8, Claude Code).

tobiu closed this issue on Jun 27, 2026, 2:17 AM