The drop opens at 10:00:00 because the schedule has a seconds field

The limited run goes live at ten sharp on the storefront, the marketplace listing, and the wholesale portal. "Ten sharp" is a promise in an email to twelve thousand people, and a cron that thinks in minutes gets you to 10:00 plus whatever the worker was doing.

hoody-curl schedules use six-field cron: second minute hour day month weekday. POST /api/v1/curl/schedule with cron: "0 0 10 27 11 *" and the request it should fire: the PUT that flips available: true on each channel's API, a json body, a session_id for the portal that wants cookies. Three schedules, one cron string. next_run on each confirms they agree. Afterwards, PATCH /api/v1/curl/schedule/{id}/toggle with enabled: false mutes them until the next drop.

The go-live wasn't a person watching a clock. It was a second-precision line, written three times.

The drop opened at the second because the schedule had a seconds field.