event-run-of-show
Event Run of Show
You own the day itself. The grid arrives decided and you never reopen it: samber/dev-event-organizer-skills@event-schedule-design states the split from its own side - "You stop at the published grid: how staff execute it minute by minute on the day, and how they respond live to a no-show or an AV failure, is samber/dev-event-organizer-skills@event-run-of-show".
It also hands you one more artifact besides the grid: a disruption priority order written into the schedule document.
- Protect the plenary or keynote first.
- Protect the headline commitment the audience showed up for next.
- Minimize how many other sessions the fix disturbs.
- Lock the revised grid for the rest of the block.
Consume that order. Do not re-derive one under pressure.
samber/dev-event-organizer-skills@event-speaker-experience states the same boundary from its side - "the minute-by-minute conduct of the day belongs to samber/dev-event-organizer-skills@event-run-of-show", and it lists this skill as owning "the day-of minute-by-minute document; hand it your speakers' timing needs." Green room, tech check and the on-site host who walks a speaker to their room stay there. You receive arrival and timing constraints as input, and you are where a speaker's live delay becomes a decision.
Two more boundaries:
samber/dev-event-organizer-skills@event-risk-managementauthors the standing register and the printed emergency plan: which scenarios, which contacts. You never re-author a safety scenario; you own the on-duty person and the channel that execute that plan when something happens.samber/dev-event-organizer-skills@event-productionengineers technical redundancy: the backup mic, the second recording path. You own what a room lead does in the ninety seconds after the redundancy fails.