Plan a run of show backwards from the end time

Steps

1. 1 Guest Open the public host application form 0:02 ▣

   No account needed to START pitching a night — the account is asked for at the very end, once the host knows what they are signing up for. Everything about the schedule below is asked from scratch.

2. 2 Guest Who is asking, and for what 0:03
3. 3 Guest Pick the event date from the calendar 0:04 ▣

   Saturday 17 April 2027. This is the EVENT day — which is not the same as the calendar day every part of the night falls on, and that difference is the whole point of what follows.

4. 4 Guest When does the night end? 0:06

   The only anchor the host gives. Everything else is a DURATION, and the schedule is walked backwards from here.

5. 5 Guest …Midnight 0:07 ▣
6. 6 Guest How long does the headliner play? 0:08
7. 7 Guest …2 hours 0:09
8. 8 Guest How long is clean-up? 0:11

   The only step that moves FORWARD from the end time.

9. 9 Guest …1 hour 0:12
10. 10 Guest How long do the openers play? 0:13
11. 11 Guest …1 hour 0:14
12. 12 Guest How long is setup? 0:16
13. 13 Guest …1 hour 0:17
14. 14 Guest How long before the first act do doors open? 0:19
15. 15 Guest …30 min 0:20
16. 16 Guest The run of show derives itself 0:21 ▣

    Nobody typed a timestamp. Doors 8:30 PM, first act 9 PM, headliner 10 PM, last note at midnight — which is already the 18th, so the card says so out loud.

17. 17 Guest Same night, one answer different: it runs to sunrise instead. 0:23

    Anything before the 6am rollover still counts as the same night, so 'Saturday, ends at 6 AM' means Saturday MORNING — and the run of show has to walk backwards through midnight to get there.

18. 18 Guest Change the end time 0:25

    No preset says 6 AM, so this is the free-entry branch. It is still a wall clock, not a timestamp — the host never sees UTC.

19. 19 Guest …none of the presets fit: Other… 0:26
20. 20 Guest …6:00 AM 0:27 ▣

    Typed into the free-entry box, the group commits and collapses exactly like a preset — and the SERVER sends back the canonical label.

21. 21 Guest The openers play longer 0:28
22. 22 Guest …2 hours 0:29
23. 23 Guest Setup takes longer too 0:31
24. 24 Guest …2 hours 0:32
25. 25 Guest Doors open an hour before the first act 0:33
26. 26 Guest …1 hour 0:34
27. 27 Guest Load-in lands on the PREVIOUS evening 0:36 ▣

    Setup 11 PM Friday → doors 1 AM → first act 2 AM → last note 6 AM Saturday. The clock crosses midnight in the middle of the run of show and the schedule is still in order, because every hop is arithmetic on absolute instants, never on the wall clock.

28. 28 Guest Venue-local on screen, UTC in the database 0:37 ▣

    The browser built neither string. It posts wall-clock answers to /api/intake/public/timeline/preview and renders what comes back — one implementation of DST and the midnight rollover, on the server.

29. 29 Guest Size the room and the bar minimum 0:39
30. 30 Guest Open the tier table to enter exact rows 0:40

    The shape buttons above fill this in one press; this night wants its own numbers, and precision is always one tap away.

31. 31 Guest Propose one tier 0:42
32. 32 Guest Accept the clause this end time implies 0:43

    A rider is a checkbox only because an APPROVED clause sits behind it: ticking this accepts staff overtime after 00:00 and the municipal noise ordinance. This programme runs 2 AM → 6 AM, i.e. it ends ON the rollover rather than before it, so the automatic derivation does not fire and the acceptance is genuinely the host's.

33. 33 Guest Submit the application 0:44

    No flyer attached, so the platform recommends one. It is a RECOMMENDATION, never a gate — declining is recorded on the application rather than blocking it.

34. 34 Guest Send it anyway 0:45

    Everything typed is already validated and parked server-side. The host is asked to confirm the address — an event host needs an account to sign the contract, and this is the last moment where asking for one is not in the way.

35. 35 Guest Offstage: the confirmation email goes out 0:47
36. 36 Guest Confirm the address — the run of show files itself 0:51

    The five stored instants survive the hold untouched — the parked payload is replayed through the same submit path a signed-in host uses.

37. 37 Guest Landed on the thank-you page 0:54 ▣
38. 38 Venue Manager The venue manager opens the submission 0:58 ▣
39. 39 Venue Manager The same run of show, from five stored instants 1:00 ▣

    The application stores UTC only. This projection is rebuilt from those five timestamps in the venue's own timezone, so staff and host are looking at the same night in the same words.