TribeRide staging
Find, publish, and manage real plans.
Open seats, visible stages, real plans
TribeRide turns everyday coordination into scenes with open spots, a visible join path, and account-scoped follow-up. Start with rides, stays, and meals; coach and creative pools stay visible as planned lanes.
Use the first row as a working path: find open scenes, publish supply or demand, then return to My Scenes to track the queue state tied to your account.
Account-scoped
Private scenes and values stay filtered to the signed-in member.
Server-gated
Participant, slot, payment, and payout facts remain server-side.
Pilot honest
Staging labels stay explicit about planned and owner-gated areas.
Staging preview only. Publishing and joining run through the existing staged flow. Payout execution, production cutover, and broader commercial rollout remain owner-gated.
What you can publish
Rides and open seats
Offer or find rides with open seats, pickup context, and a clear join path.
Browse ride scenes →
Places to stay
Publish a place to stay or find one with open spots for a trip.
Browse stay scenes →
Meals and tables
Host a meal, join a table, and keep the participation step visible.
Browse meal scenes →
Skills and coaching
Coaching and skill sessions are planned, but not open for publishing yet.
Planned
Creative sessions
Creative and photography collaborations are planned for a later publish path.
Planned
How the staged flow works
The current product path is intentionally narrow: discover a scene, request access in the room, then manage the account-scoped record from My Scenes. Commercial execution stays behind owner gates.
Step 1
Find or publish
Discovery and publish routes keep the first decision clear: join an open scene or offer one.
Step 2
Coordinate in the room
Scene Room shows the staged join, hold, confirmation, and message path without inventing client truth.
Step 3
Return to your queue
My Scenes and My Values show the private account view after the server can read the session.
How trust stays explicit
Trust model
Real coordination, visible boundaries.
TribeRide keeps the useful product path close to the member: account-scoped plans, server-derived runtime state, and plain labels when a commercial or production step is still gated.
Member scoped
Private plans, values, and room context stay tied to the signed-in member instead of public browsing.
Server authority
Join, hold, confirmation, value, and payment facts are derived by server paths, not client labels.
Boundary honest
Staging keeps payout, production, and rollout limits visible instead of presenting planned work as done.
Start from here
Discovery
Find
Find joinable rides, stays, and meals. This is the main entry for new members.
Browse open scenes
Publish a scene
Publish
Offer a ride, stay, or meal with open spots under your signed-in account.
Offer open spots
Post a need
Publish
Ask for a ride, stay, meal, or other plan you want someone to host.
Ask for help
My scenes
Manage
Return to scenes you own or joined and check the current participation state.
Review your queue
My values
Manage
Review value records for your activity. Payout execution stays owner-gated.
Check value records
Member hub
Account
Update your profile and capability presentation for member-scoped surfaces.
Update profile
Sign in
Account
Start the browser session needed for publishing and account-scoped pages.
Open auth