Migration control plane
Persistence Control
Stage the CareerOS data transition deliberately. Browser recovery remains the safe default. Mirror writes is available only after private storage and rollback are ready. Server primary is locked until exact local/server parity is verified.
Current policy
Browser recovery
Private runtime
Standby
Checking runtime
Recovery points
—
Parity
Pending
Persistence modes
Controlled rolloutBrowser recoveryAll recovered workspaces continue using the versioned browser snapshot. No server dependency.
Mirror writesMigration target: local data stays immediately available while migrated workspaces also write to private server storage.
Server primaryFinal target: migrated workspaces read private server storage first while retaining browser recovery as an explicit rollback/cache path.
Cutover gates
LockedAuthenticated private session
PENDINGSign in from Data & Backup or Recovery Points
Private read path
PENDINGServer auth/private Blob are not both ready
Server writes enabled
PENDINGCAREEROS_SERVER_WRITES_ENABLED must be true after validation
Recovery point available
PENDINGCreate a recovery point before changing persistence mode
Exact section parity
PENDINGInspect private server and resolve every local/server fingerprint difference
Safety boundary: changing this policy does not silently migrate every workspace. Each module must be converted to the shared runtime provider and pass regression checks before it begins honoring Mirror writes or Server primary.