Dataroo-to-ECS0 ownership separation is now documented as a complete local design and implementation plan, with live/reference state preserved and Atlas integration still explicitly unaccepted.

Scope

• Host: rdmsm4x.
• Project mode: Production.
• Canonical repositories observed read-only:
  • /Users/richh/dev/sites/dev.ecs0.net
  • /Users/richh/dev/sites/dev.dataroo.net
• Planning worktree created and used exclusively: /Users/richh/dev/_worktrees/dev-ecs0-net/codex-dataroo-ecs0-migration-design-20260828.
• Branch: codex/dataroo-ecs0-migration-design-20260828.
• Commit: 016594f21917b147e517e96cf85dcb4ae033206a.
• No live content, source generator, Atlas source, authentication policy, DNS, certificate, tunnel, container, scheduler, redirect, or deployment state was changed.

Files changed

• Added /Users/richh/dev/_worktrees/dev-ecs0-net/codex-dataroo-ecs0-migration-design-20260828/docs/superpowers/specs/2026-08-28-dataroo-ecs0-separation-design.md.
• Added /Users/richh/dev/_worktrees/dev-ecs0-net/codex-dataroo-ecs0-migration-design-20260828/docs/superpowers/plans/2026-08-28-dataroo-ecs0-separation.md.
• Created and updated /Users/richh/.agent-coordination/checkins/codex-rdmsm4x-dataroo-ecs0-separation-design-20260828.json.
• Created immutable fleet-bus dispatches:
  • 20260828-005156-7EE46515
  • 20260828-012536-D4436B07
• This changelog file is the canonical local archive copy.

Decisions recorded

• dev.ecs0.net becomes the independent private development site for ECS0, East Coast Science, and solo-development products.
• dev.dataroo.net becomes Rich's independent private personal/homelab site.
• Two independent source trees, builders, runtimes, authentication surfaces, and deployments are required; the migration manifest is temporary coordination data, not a shared publisher.
• The 50 Atlas documents classify as 31 ECS0-owned, 7 Dataroo-owned, 9 independently split, and 3 historical archive records. All 39 supporting assets are classified.
• Redirects are exact-route, GET/HEAD-only HTTP 307 cohorts after per-route acceptance; there is no wildcard redirect or automatic HTTP 308 promotion.
• Both sites run in parallel for 30 accepted days before Rich receives a route-cohort decision packet. Source retirement or deletion is outside this plan.
• Owner authentication targets exact-account Google SSO with effective sessions no longer than one month and passkeys where useful; existing recovery is retained until a separate tested decision.
• Capability guest links remain a separate future security-sensitive subproject.

Commands and coordination

• Captured exact host, repository, worktree, branch, commit, dirty-state, Compose, HTTP, and Atlas ownership evidence.
• Ran fleet check-in synchronization and agent-mail synchronization; rdmpw3265m was unreachable, while the other contacted fleet hosts synchronized.
• Sent the planning-scope lease request and the final artifact handoff to codex@rdmsm4x.
• Created the isolated Git worktree from clean ECS0 main; no canonical main worktree was edited.
• Staged and committed only the two documentation files.

Verification evidence

• Route-classification comparison against the active Atlas snapshot passed exactly: 31 ECS0, 7 Dataroo, 9 split, 3 archive, 50 unique documents total, and zero missing or extra paths.
• The active snapshot reports 39 supporting assets, all covered by the design.
• Plan structure validation passed: 18 tasks and 106 executable checkboxes.
• All 44 shell code blocks passed syntax parsing; all 17 Python code blocks parsed successfully.
• git diff --check passed.
• Added-line secret-shape scanning found no secret values.
• Existing operational shell syntax checks passed.
• docker compose -f infra/compose.yaml config --quiet passed.
• Full repository suite: 55 tests run, 51 passed, 3 runtime-disabled skips, and 1 failure. The failure is test_destination_matches_every_service_file_in_source, because the deliberately older planning base lacks amagansett/ak-public-read-repair-2026-08-27.html. The same failure was reproduced on untouched canonical ECS0 main; the clean Atlas owner branch at 83d016ec734cb81236dff51c7a670af0976c28cb contains the capture. No out-of-lease repair was made.

Backup and rollback

• No live data or configuration was mutated, so no live backup was required.
• The two documentation files are preserved in Git commit 016594f21917b147e517e96cf85dcb4ae033206a on an isolated branch.
• To abandon the planning lane, first preserve or integrate the commit, then remove only the exact isolated worktree and branch through normal Git worktree commands. Do not delete the Dataroo source, Atlas branch, canonical repositories, or immutable mail receipts.

Outstanding owner actions

• Atlas owner receipt and acceptance are still absent. Integration is blocked until that owner explicitly accepts the manifest/schema contract or states conflicts.
• PROJECTS.md was not edited because its shared-file lease was not clear.
• Implementation, integration, deployment, authentication changes, redirects, parallel-run Day 0, and completion have not started.
• The Apple Notes copy is pending because this Codex process is running under launchd manager Background, not an Aqua desktop session; run the Notes changelog helper from Terminal.app on rdmsm4x when an Aqua session is available.