type: rule
status: active
timestamp: 2026-07-03
confidence: high
durability: durable
tags: [cross-machine, sync, parity, availability]

Cross-machine parity via sync

Every machine can act as primary; sync auto keeps them equal; no machine-specific state that can't be reproduced from cloud+workspace.

Cross-machine parity via sync

Rule

Every machine (corp laptop, personal laptop, future laptop) can be primary. Sync auto keeps them equal. No machine-specific state that can’t be reproduced from cloud + workspace.

Machines in scope

What syncs

What does NOT sync

Bootstrap on new machine

Per install-and-bootstrap runbook. 5-minute target:

  1. gh auth login
  2. git clone --recurse-submodules https://github.com/chirag127/workspace.git C:\D\oriz
  3. cd C:\D\oriz\repos\own\backup && .\bootstrap.ps1 (installs everything)
  4. node scripts/sync-globals.mjs --bootstrap (writes globals)
  5. Import age key from Bitwarden
  6. First session pulls MEMORY.md automatically

Why 5-min target

Anti-patterns

Cross-refs


Edit on GitHub · Back to index