D0024 — The laptop move: eleven calls before the weekend, starting with copy or rebuild

[obotclaw[bot]]

Full argument, options and evidence: https://jwildfire.github.io/obot.roadmap/reports/decisions/2026-08-20-laptop-migration/

You move to the new laptop this weekend, and a step-by-step rebuild guide was written for it today. Eleven of its questions cannot wait for the day itself — each one either changes what the steps say, has to happen while the old machine is still whole, or gets set in the first ten minutes of the new one. All eleven arrive with a recommendation, so this is you agreeing or disagreeing rather than deciding cold.

Two things underneath every question, and neither is hypothetical. Nothing on the old machine is backed up anywhere: no backup destination is configured and no cloud folder holds a copy, so roughly eleven megabytes that no repository can rebuild — the decision record, the ledgers, the program's memory — exist on exactly one drive. And the key that lets agent writes go out as the bot rather than as you exists in one system keychain, with no exported copy and no way to get the original back from GitHub.

The one that decides the rest:

• Option A, recommended — rebuild clean. Every setting is chosen rather than inherited. Costs about three hours of attention across a day, plus a new signing key and a round of updating the repositories that hold it. Forecloses nothing, because the old machine is still sitting there.
• Option B — copy the account across with Apple's migration tool. Fastest by hours, and it keeps the GitHub login and the signing key intact. It also carries all three of the configuration problems the rebuild exists to remove, none of which announces itself, plus a settings block describing a different project that has been quietly judging this one's commands.
• Option C — copy, then undo the three problems deliberately, treating the read-back checks at the end of the guide as the actual deliverable. The honest fallback if the weekend turns out shorter than planned.

One thing the guide does not say and the page does: the strongest argument for copying the account is that the signing key survives, and you can have that under a clean rebuild for free. Generate the replacement key and update the repositories that hold it this week, while both machines are alive. Then the new machine never has a window of broken builds, and the key stops being a reason to take the faster route.

The other ten, with the recommendation each carries:

• L2 (D0024.2) — where does the pre-move copy actually go, and is it in hand by Friday? Recommends an external disk plus a real backup destination set up on the new machine. Added on the page: do not erase the old machine for at least a week afterwards.
• L3 (D0024.3) — is there a copy of the signing key anywhere off this machine? Recommends assuming there is not, and confirming that before the move rather than during it.
• L4 (D0024.4) — does the change that keeps agent GitHub writes off your own name land before the move or after? Recommends before, with the safeguard added to the installer in the same change so a fresh machine's self-check can see whether it is there.
• L5 (D0024.5) — same account name, and the working folder in the same place? Recommends keeping both exactly. The program's memory lives in a directory derived from that path, and a one-character change makes it invisible rather than missing.
• L6 (D0024.6) — disk encryption on, automatic login off? Recommends yes to both, and adds the half the guide leaves out: together they silently stop the scheduled sweep after any reboot, so something has to tell you it is not running.
• L7 (D0024.7) — a new access key for GitHub, or the old one? Recommends a new one, so retiring the old laptop is a revocation rather than an act of faith.
• L8 (D0024.8) — which repository owns the top-level instruction file, and is it a link or a checked copy? Recommends the harness repository, installed as a checked copy, with the check running on a schedule rather than by hand.
• L9 (D0024.9) — does the morning summary get turned on? Recommends yes. It has been one command away for weeks, and a clean rebuild is exactly where that gets lost.
• L10 (D0024.10) — which version of R? Recommends pinning to the old machine's version for the weekend, and records a disagreement: that is right for the move and wrong permanently, since the end state should reproduce the automated builds rather than the old laptop.
• L11 (D0024.11) — lid open by convention, or a desk that runs with the lid shut? Recommends the desk, if the parts are there by Friday. Convention has already failed once, and it failed silently.

Three of the guide's fourteen questions are not on the page, and it says so rather than dropping them. Two went to the local configuration list, because publishing them would describe private family information or what a live credential is currently permitted to do; they are on your dashboard as items with the exact action and the exact check. The third, whether the program's memory store belongs in a private repository, is deferred by the guide itself as not needed before the move.

The rebuild guide stays local. It names where credentials live and never what they are, and nothing on the published page reproduces it beyond what each choice requires.

---

Drafted by 👯🤖 W0091 using Claude Opus 5. NOT reviewed by @jwildfire.