Using a rigid day script
Replacement: follow the objective and current room state after every update.
Objectives can change as the alpha evolves. This route follows the player-visible state instead of pretending every day has one permanent script.
Run each shift in four passes: orient, serve, observe, recover. At opening, read the objective and HUD. During service, keep one active task moving. When the cafe changes, stop adding new tasks and compare what the team can actually see. After the interruption, re-read the objective before resuming; do not assume the old task is still the right one.
Action route
Confirm the day/open state, current objective, order count, reputation, Sanity and cash.
Complete the visible service task and keep the order queue from becoming the team's only focus.
Name unexpected visual or audio changes and give one player room to inspect while others hold position.
After the interruption, check the objective and HUD again before choosing the next action.
Decision table
Recovery
Replacement: follow the objective and current room state after every update.
Replacement: freeze the queue, resolve the visible problem, then restart service.
Replacement: verify objective, orders and Sanity before moving again.
Quick answers
No. It gives a reusable shift loop because alpha objectives can change. Follow the current task shown in your game.
Use the CCTV workstation when the current task or a visible cafe change gives you a reason, then return to the shift loop.