drink-service-pacinglisted

# Drink service pacing Build a capacity envelope, then place each service state inside it. The result is a pre-event review artifact. It never directs live service, contacts a venue, sends a guest message, changes staffing, or claims physical verification. ## 1. Confirm the job Accept requests to build or validate a timed drink-service run sheet before an event. Keep these adjacent jobs outside the procedure. - Beverage quantities and purchasing belong to event quantity planning. - Preparation dependencies belong to a drink-prep schedule. - Staffing recommendations require the venue or service provider. - Live queue decisions remain with the on-site service lead. When a request mixes jobs, retain the run-sheet portion and record the excluded work without performing it. Complete this step when the requested artifact is confirmed as a pre-event service run sheet and every excluded job is named. ## 2. Freeze the inputs Record each value with one source label chosen from `venue confirmed`, `provider confirmed`, `measured rehearsal`, `host approved`, or `unknown`. The capacity envelope requires all of the following. - Event phases have fixed start and end times. - Arrival waves include their time windows and expected service-request counts by service route. - Any conversion from guest arrivals to expected requests is supplied and approved by the host or venue. - Service points show active intervals, assigned workers, menu scope, and verified effective throughput. - Men