A shared machine turns bot handoffs into a design problem. "Instead of a machine per task, you get a machine per person." Every bot keeps its own role, memory, and thread while sharing one persistent computer, browser state, files, and connections. Name it the Routine Readiness Gate. A task becomes a routine only after the bot can repeat the work reliably on the shared machine. 1) Run one real task before saving any skill. 2) Correct the bot until its method produces dependable work. 3) Save durable files in the shared workspace. 4) Prefer a connector, then use the browser when no connector exists. 5) Use takeover only for the blocked authentication step. 6) Schedule the routine only when another bot can share the computer without breaking the run. A bot can own up to 50 routines, so the scarce resource is not routine capacity. It is confidence that shared state, browser changes, and handoffs will not corrupt repeated work. On Monday, keep a task manual unless it passes all six checks.