Product · Blueprint
Get booked as an artist
How a teacher, DJ, band or performer goes from having a page to being booked again, drawn lane by lane. There are three ways in (a booking request, a line-up invite, a gig), and none of them leads to the others.
How to read it
Status (as on the UX map)
- Live, real data
- Partial or mock data
- Promised, not built
- Gap: nothing planned
Friction markers
- Waits (3): Someone is blocked on someone else, and nothing chases it.
- By hand (8): A person carries the link or the news between lanes.
- Silent (8): An answer or change doesn’t reach the side that needs it.
Gaps are where markers cluster. Click a step for its code, or a gap below to light up its steps. Built from the code on 2026-11-16 (/artists, an artist’s /@handle/book, the line-up invite, /gigs and the MCP tools); not yet run end to end with a test artist and organiser. The line-up steps overlap the event setup blueprint, seen from the artist’s side. This is job J5, get discovered and booked as an artist.
Friction by phase
Be listed
⏳1 ✋1 🔇1 · 1/3 not live
Be found
⏳0 ✋1 🔇0 · 2/4 not live
Asked or invited
⏳0 ✋3 🔇2 · 2/5 not live
Answer
⏳2 ✋1 🔇1 · 2/6 not live
On the line-up
⏳0 ✋1 🔇3 · 4/6 not live
The night
⏳0 ✋1 🔇0 · 2/2 not live
After
⏳0 ✋0 🔇1 · 2/3 not live
Lanes × phases
| Who | Be listed | Be found | Asked or invited | Answer | On the line-up | The night | After |
|---|---|---|---|---|---|---|---|
Artist Their /@handle, Bookings, /confirm/<token> | |||||||
WeDance Sync, emails, line-ups | |||||||
Organiser /artists, /@handle/book, the event editor |
Where it breaks
Each gap is a cluster of markers. Click one to light its steps on the blueprint.