Parent
Outcome
Operate ts-cloud across more than one box or region: onboard and validate remote servers, expose real driver-backed lifecycle operations, assign workloads to capacity pools, use remote builders, complete multi-region replication/failover, and provide safe upgrades and disaster-recovery drills.
Architectural direction
The control plane should schedule operations; provider drivers should declare capabilities and execute idempotent primitives. AWS, Hetzner, and local boxes may differ, but status, events, auth, audit, retry, and UX contracts should remain consistent.
Children
Exit criteria
An operator can understand fleet capacity and health, move or rebuild workloads deliberately, validate failover and recovery, and upgrade the platform without treating SSH sessions as the primary management plane.