amadan

carlos / platform Public

Clone 
git clone https://amadan.net/carlos/platform

Plain git — no account needed to clone.

Download

Download this file

---

FIRST PROMPT: “Read the brief at docs/superpowers/plans/CODEX-BRIEF-MOVES-HOME-PART2-BUILD-R1.md (committed on this branch) and do the review it describes.”

WHAT: Reviewed origin/main...HEAD: ee35dee → 8fcd7e00, without edits.

STATUS: READY TO MERGE (pending copy and census). No P1/P2/P3 findings identified in static review.

  1. Region names: New move arguments use @home; witnesses check retained spellings, deduplication, and staging-lease keys.
  2. T3 and environment pins: Home targets reject CARLOS_REGION. Instance-supplied box variables remain pinned; v1 reports/pins are refused. Recovery retains the full local digest.
  3. Production owners: Landing, recovery, and revert witnesses use production owners and runtime restore → reserve → materialize sequencing. Launch and readiness remain test stand-ins.
  4. Create isolation: The home capability fold is move-only; create’s placement semantics remain unchanged.
  5. Home-named boxes: The door rejects them before staging checks or claim writes.
  6. Cleanup: Witnesses cover both home spellings, both engines, repeated acknowledgements, and named-box refusal.

For moves not touching home, the environment-pin and revert fixes apply as intended. One additional presentation change: staging-refusal lists can now include the home name through stagingNames. I found no behavior change to non-moves claim launches.

git diff --check and whole-tree gofmt passed. Independent hash checks matched all 15 census-overlay function bodies, four package envelopes, and the cumulative legacy seal. Go tests could not start because the sandbox prevented creation of Go’s build directory; runtime validation and CI remain unverified here.

NEEDED: Copy approval for MV-N510–513 and census-owner approval remain outstanding. MV-N21 is correctly withdrawn from the active copy record and IDs.

RECOMMENDED: Complete the required Go gates and confirm green amadan CI on the final tip before landing.

SESSION: Safe to close. No files changed, scratch files created, or background processes started.