Receive Agent OS source and package topology in the Brain

Context

The Brain repo is a four-blob scaffold. This leaf performs the atomic source/package receive defined by the frozen cut manifest; it does not delete Neo's source.

The receive is large by file count but one transaction by topology: Host Edge root, independent cloud/, inventory-admitted shared/, import rewrites, and package manifests must agree at one target SHA.

The Problem

Splitting the receive by arbitrary directories would create intermediate states that violate ADR 0040, conceal cross-plane imports, or make package isolation untestable. Conversely, mixing deployment and Engine deletion into the import PR would make rollback and review impossible.

The Architectural Reality

• ADR 0040 fixes root=Host Edge, cloud/ independently installed, no npm workspaces, shared/ inventory-owned.
• Agent OS depends on the published Engine; Engine never depends back.
• Exact mover identities/paths come only from wave3-cut-manifest.v1.
• #17783 supplies day-one Brain CI and trigger/binding receipts; the receive is not merge-eligible without them.
• Neo remains source authority until this PR and its target receipts are green.

The Fix

Open one import PR against neomjs/neo-agent-brain:dev that materializes the complete source/package topology from the cut manifest, preserves provenance in the import commit/ledger, rewrites internal imports and scripts to target paths, adds the published Engine dependency only in the Brain, and runs the inventory/isolation/test surfaces from the receiving repository.

No source path is removed from Neo in this leaf.

Contract Ledger Matrix

Decision Record impact

aligned-with ADR 0040, depends-on ADR 0039, and preserves ADR 0019 config authority.

Decision Record

Required: consume the current ADR 0040 amendment; no new topology decision is authored here.

Acceptance Criteria

• Target tree equals the cut manifest's source→target mapping with zero missing, extra, duplicate, or stale identities.
• Root is the Host-Edge package, cloud/ installs independently, npm workspaces are absent, and shared/ contains only the inventory-approved population.
• Root/Cloud manifests materialize exact launch/dependency authority; package versions and scripts are deterministic.
• All cross-file imports/scripts/config paths are rewritten to target topology; unresolved or source-repo-relative edges RED.
• Brain depends on the published Engine only; no Engine dependency/devDependency or copied Engine source is introduced.
• Source provenance records source SHA and target import commit without rewriting Neo history.
• Inventory, isolated install, static closure, runtime denial, Cloud positive control, computed-edge reconciliation, and applicable unit/integration suites run from the receiving repo.
• #17783's day-one Brain CI tranche runs green at the target head. (Truth-synced 2026-08-26: #17783's binding-receipt clause was cut under the operator's zero-machinery bar — a committed receipt plus drift detector for what is currently one required status context. The surviving requirement is one read-back proving the required context exists; no receipt files are produced or consumed here.)
• Brain README, package docs, Architecture Overview, and structure map reflect the received topology.
• A fresh fork of neomjs/neo-agent-brain at the received head onboards with git clone + root npm install and no sibling checkout, meta-repository, custom seat config, or manual materialization step. The nested cloud/ package proves its own independent install when exercised and cannot borrow an ancestor/workspace hoist.
• Neo source remains untouched; the PR body says Refs the Wave-3 Epic and Resolves only this leaf.

Out of Scope

• ai/deploy/** and container-image proof;
• tracker transfer;
• peer-owned learn/ / ADR corpus migration;
• Neo-side deletion or Engine package cleanup;
• Wave-4 severe runtime/seat proof.

Avoided Traps

• Directory-shaped copy: ignores inventory disposition.
• Plane-by-plane half-merge: produces a target that cannot satisfy the package contract.
• npm workspace convenience: invalidates isolation through hoisting.
• Source deletion in receive PR: removes rollback and violates receive-before-remove.
• Copied Engine internals: creates the forbidden back-edge.

Related

Blocked by: #17787 · #17783 · #17784
Parent Wave-3 Epic: #17786

Handoff Retrieval Hints

Retrieval Hint: Brain atomic receive Host Edge cloud shared no workspaces cut manifest

Origin Session ID: 975b7d3f-ebb0-46bd-8b5a-ac7fa64ba0d0