Skip to content
Product · Blueprint

Make a page real

How a page WeDance listed on its own — synced from wedance.vip or imported from Instagram — becomes run by its real owner, and how dancers can tell. The owner is rarely told the page exists, and dancers can’t see the difference.

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 (4): A person carries the link or the news between lanes.
  • Silent (4): 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 (/business/claim, Admin → Claims and Users, the organiser’s /confirm links, a page’s Duplicates tab, Who’s coming and /dance-card); not yet run end to end with a test owner. See also the event setup blueprint. This is job J7, trust it’s real.

Friction by phase

Page appears
⏳0 ✋0 🔇1 · 2/4 not live
Owner finds it
⏳0 ✋1 🔇1 · 1/3 not live
Claim or join
⏳1 ✋0 🔇0 · 0/3 not live
Review
⏳1 ✋2 🔇1 · 3/4 not live
Owner runs it
⏳0 ✋0 🔇0 · 1/3 not live
Duplicates merged
⏳1 ✋1 🔇0 · 1/3 not live
Real faces
⏳0 ✋0 🔇0 · 1/3 not live
Dancers trust it
⏳0 ✋0 🔇1 · 2/2 not live

Lanes × phases

WhoPage appearsOwner finds itClaim or joinReviewOwner runs itDuplicates mergedReal facesDancers trust it
Page owner
Organiser, venue, artist · /business
WeDance
Sync, import, admins (Admin → Claims, Users)
Dancers
/@handle, event pages, /meet

Where it breaks

Each gap is a cluster of markers. Click one to light its steps on the blueprint.