CodeBook: supervising an overnight work order 1. Agree on what done means. In a chat connected to CodeBook, try: In Payments, plan a cloud work order to migrate the invoice exporter. Preserve the amounts and rounding for our existing invoice fixtures. Show the milestones, who will validate them and what needs my approval. Include a dedicated manager and tell me its token ceiling before starting. Limit the entire work order to $15 at the configured rates and finish by 8 a.m. tomorrow in my time zone. Show me the exact deadline. In Claude Code with the CodeBook plugin, the shortcut is: /factory overnight Payments "Migrate the invoice exporter" 2. Review the plan before saying proceed. Check the repositories, tests, approval stations and available runner. Cloud means you can close the client. Your factory's policy still decides which stories can start. If it only suggests work, a person must release the next group. The dedicated manager's token ceiling covers its own work. The work order's optional dollar limit is shared by its workers, manager and supported proof runs. Unpriced operations are held. A request already sent to a provider can still incur charges. The report shows spent, reserved and available amounts. Your separately operated CI and deployment services bill under their own plans. For a shared limit, set Spend limit and Deadline under Work orders when you create the order. In chat, ask for a new cloud work order with a dollar ceiling and a specific stop time with its time zone. The planner, manager, workers and hosted proof runs reserve from that amount at configured rates. The order shows recorded spending, outstanding reservations and why an operation was held. A failed call can leave its reservation in place if the provider's usage is unknown. Hosted proofs need a prepared Modal environment and a sandbox hourly rate. External CI bills are separate. 3. Return to the same order. Keep the work order reference and link. In a new chat ask, for example: Show me WO-7 in Payments. Which tests passed on which commit, what failed, what did it cost, and what do you need from me? Or read the recorded results directly in Claude Code: /factory report Payments WO-7 The report does not start an agent. A missing test result is not a pass. A partial cost leaves out usage CodeBook cannot price. Follow the order's link to inspect the full evidence or decide a check that needs a person. In the work order, choose Watch production alerts if a matching production incident should pause follow-up work. Review the deployment before resuming. For a bug your team already fixed, use Factory settings → Proof runs → Incident checks to make CI catch it if it returns. See /guides/incident-checks.txt. When a production alert pauses the order, open Review alerts. The watch owner or work order creator selects Rolled back or Kept deployment for each affected deployment. They can add a note, then choose Record and resume. The order keeps the decision and who resumed it. Record a rollback after carrying it out in the deployment system. Past resumes without a decision show Decision not recorded.