Create an event, approve it, and host it

Steps

1. 1 Guest Open the public host application form 0:02 ▣
2. 2 Guest Name the act and how to reach them 0:03

   This is the name that will have to SIGN the agreement, so it is captured as a full legal name — initials are refused at the signing gate.

3. 3 Guest Describe the night 0:04 ▣
4. 4 Guest Pick the date from the calendar 0:06
5. 5 Guest When does the night end? 0:06

   Midnight on Saturday the 17th means 00:00 on the 18th — the platform applies the day-rollover rule so the whole schedule does not land a day early.

6. 6 Guest …Midnight 0:07 ▣
7. 7 Guest How long does the headliner play? 0:09
8. 8 Guest …2 hours 0:10
9. 9 Guest How long do the openers play? 0:11
10. 10 Guest …1 hour 0:13
11. 11 Guest How long is clean-up? 0:14
12. 12 Guest …1 hour 0:15
13. 13 Guest How long is setup? 0:16
14. 14 Guest …1 hour 0:17
15. 15 Guest How long before the first act do doors open? 0:19
16. 16 Guest …30 min 0:20
17. 17 Guest The platform derives the whole run of show, backwards 0:21 ▣

    Nobody typed a timestamp. Venue-local (America/Los_Angeles) on screen, ISO-8601 UTC in the database; setup ≤ doors ≤ main start < main end ≤ teardown is still validated server-side.

18. 18 Guest Accept the clauses this night needs 0:24 ▣

    Every box here is backed by contract language the venue has already approved — the rider library is the source of truth, so ticking one is accepting a clause. These three auto-inject the Sound/Stage and Liquor Liability riders two acts from now.

19. 19 Guest Size the room and the bar minimum 0:25

    Headcount × projected ticket price is what the platform's viability band is computed from.

20. 20 Guest Name the act — the payee (plan 81) 0:26 ▣

    An artist is a payee: payouts go to a user id with bank details, and the event cannot be scheduled without one. The email matches their existing account, and they will be asked to confirm — a booking is an agreement.

21. 21 Guest Open the tier table to enter exact rows 0:27

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

22. 22 Guest Propose the ticket tiers 0:28 ▣
23. 23 Guest Attach the flyer for the social campaign 0:29 ▣

    Filed as a flyer / poster / artist image, it becomes the event's public artwork URL the moment the application is submitted.

24. 24 Guest Submit the application 0:30 ▣

    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.

25. 25 Guest Offstage: the confirmation email goes out — a recording cannot open a mailbox, so we take the same link support would resend 0:32
26. 26 Guest Confirm the address — the application files itself 0:34

    One click creates the account, verifies the address, files the parked application and signs the host in. Nothing is retyped, and the host now has somewhere to sign their contract.

27. 27 Guest Land on the thank-you page 0:37 ▣
28. 28 Venue Manager Open the intake pipeline board 0:40 ▣
29. 29 Venue Manager Open the new submission 0:41 ▣
30. 30 Venue Manager Claim it for review (new_submission → under_review) 0:42
31. 31 Venue Manager Read the viability band the platform computed 0:43

    Viability is derived from headcount × projected ticket price against the venue's floor — the manager sees the number, not a vibe.

32. 32 Venue Manager Approve the application 0:44 ▣
33. 33 Venue Manager Approving drafted a contract automatically and notified the host. 0:46
34. 34 Venue Manager Convert the application into a draft event 0:47 ▣

    Convert mints the host's user account, grants them the event-scoped `host` role, and creates the event in `draft` — one transaction, three effects.

35. 35 Venue Manager Offstage: the act confirms the booking — nobody sells a show nobody agreed to play 0:49
36. 36 Administrator Open the auto-drafted contract 0:53 ▣

    Nobody wrote this. Approval fired contracts.on_application_approved inside the same transaction that approved the application.

37. 37 Administrator The blue snapshots are the application's own numbers 0:54

    {headcount}, {ticket_price} and {event_date} were snapshotted at draft time, so later edits to the application cannot silently change a live agreement.

38. 38 Administrator Lock the agreement — SHA-256 canonical hash 0:55 ▣

    Locking freezes the text, hashes it, and emails the host a single-use signing link.

39. 39 Administrator Offstage: the host receives their signing link by email 0:56
40. 40 Guest The host opens their signing link 1:01 ▣

    Opened signed-out on purpose: the single-use token in the URL is what authorises this page, not a session. The host can sign from the email on their phone without logging in — and the typed signature is still checked against the legal name captured at intake.

41. 41 Guest Choose to type the signature instead of drawing it 1:02
42. 42 Guest The host types their full legal name 1:03 ▣
43. 43 Guest …and agrees to sign electronically 1:04

    The Sign button stays disabled until there is both a signature and consent.

44. 44 Guest Sign the agreement 1:05 ▣
45. 45 Administrator The administrator opens the contract to counter-sign 1:09 ▣
46. 46 Administrator Switch the counter-signature to typed 1:10
47. 47 Administrator The counter-signer types their name 1:11
48. 48 Administrator …and agrees to sign electronically 1:12
49. 49 Administrator Execute the agreement 1:13 ▣
50. 50 Administrator Counter-signing sealed the document AND flipped the event draft → announced. 1:17
51. 51 Administrator Open the event the application became 1:18 ▣
52. 52 Administrator Move the event draft → announced 1:19
53. 53 Guest It is now live on the public catalog 1:23 ▣
54. 54 Member Open the event as member 1:25 ▣
55. 55 Member Buy one General Admission ticket 1:26

    Reserving takes the seat out of inventory and starts a 5-minute hold; the countdown on the next page is that hold.

56. 56 Member The hold timer is running on the checkout page 1:28 ▣

    If the hold expires the seat goes straight back into inventory — the scheduler sweeps it, nobody has to click anything.

57. 57 Member Pay for the order 1:29 ▣

    Charged through the mock payments adapter with token tok_success.

58. 58 Member Land back on My Club, purchase confirmed 1:33 ▣

    The hub is where a member already lives — tickets, credit, listings and comps — so the purchase confirms in context rather than on a receipt page they have to navigate away from.

59. 59 Member Open the site menu 1:34

    The collapsed bar is one row at every role; the full role-gated navigation lives in this panel and closes as soon as you leave.

60. 60 Member The ticket is in the wallet 1:35 ▣
61. 61 Member Time travel: it is now the night of the event (2027-04-18T03:30:00Z) 1:36

    The platform clock moved to 2027-04-18T03:30:00Z and the scheduler ticked.

62. 62 Member Back on the night, signed in again 1:47 ▣

    Sessions expire on the platform clock, so a jump this big logs everyone out — the recording shows the re-login rather than hiding it.

63. 63 Member At the door the reader wants a credential, not a receipt: this member's credential is their rotating membership card. 1:48
64. 64 Member Open the rotating QR pass 1:50 ▣
65. 65 Member Read the live payload off the pass card 1:54

    CLB1:<serial>:<6-digit TOTP>, recomputed in the member's browser every 15 s. Only the server can say whether it is valid.

66. 66 Door Staff Door staff opens the scanner 1:57 ▣
67. 67 Door Staff Scan the pass 1:58 ▣
68. 68 Door Staff The chain is closed: applied → approved → signed → sold → scanned 2:00 ▣

    Every hop in this video was a real HTTP request against the image that is about to be deployed.