Staging only — non-production preview. Provider operations, payout, and production remain gated.

TribeRide staging

Find, publish, and manage real plans.

Start from a group-chat plan

No sign-up needed to start

Turn your group chat into a real plan

Paste the message where your group agreed on a ride, stay, or meal. TribeRide reads it in your browser and prefills an editable draft scene.

The parse runs entirely in your browser — nothing is created yet. Creating the scene happens after you review the draft and sign in; the manual form uses the same server authority.

Paste a group chat

Turn a group-chat plan into a scene

Paste the message where you agreed on a plan. It is read in your browser to prefill a draft — nothing is created until you check it and confirm.

Statusidle
The parser runs entirely in your browser and creates nothing. Only Confirm writes, through the same server action and sign-in the manual form uses.

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.

Route first

Every primary action opens an existing product surface.

Queue visible

Members can return to account-scoped scene status.

Commercial honest

Payments and payouts stay labeled as separate steps.

Product path

A working coordination loop, not a brochure.

Route-only
1Discover open plansBrowse live rides, stays, and meals with visible stage labels.
2Offer or askPublish a supply scene or post demand from the signed-in account.
3Track the queueReturn to private scene and value records after the server reads the session.

This home page only routes members into existing surfaces; it does not create runtime facts.

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, launch operations, and broader commercial rollout remain owner-gated.

Official example scenes

Three official example tiles show what a published scene looks like. They are fictional demonstrations — examples, not live supply.

Coach, Lens, and Desk pools are planned — no official examples yet.

What you can publish

The first three lanes are usable product entries today: rides, stays, and meals all lead into discovery with matching filters. Future lanes remain visible so the product direction is clear without pretending they are open.

Pool cards change the view, not runtime truth. Coach, Lens, and Desk stay planned until their publish path is explicitly built.

CarPoolLive

Rides and open seats

Offer or find rides with open seats, pickup context, and a clear join path.

Route
Discovery opens filtered to CarPool scenes.

Browse ride scenes

StayPoolLive

Places to stay

Publish a place to stay or find one with open spots for a trip.

Route
Discovery opens filtered to StayPool scenes.

Browse stay scenes

EatPoolLive

Meals and tables

Host a meal, join a table, and keep the participation step visible.

Route
Discovery opens filtered to EatPool scenes.

Browse meal scenes

CoachPoolPlanned

Skills and coaching

Coaching and skill sessions are planned, but not open for publishing yet.

Status
Visible as a future lane; no live publish path yet.

Planned

LensPoolPlanned

Creative sessions

Creative and photography collaborations are planned for a later publish path.

Status
Visible as a future lane; no live publish path yet.

Planned

DeskPoolPlanned

Work desks and study rooms

Desk and workspace sharing is planned for a later publish path.

Status
Visible as a future lane; no live publish path yet.

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.

Next state

The member lands on an existing scene or creates a published entry through the current publish surface.

Open discovery

Step 2

Coordinate in the room

Scene Room shows the staged join, hold, confirmation, and message path without inventing client truth.

Next state

The room carries the member into the server-derived participation and slot state.

Open room

Step 3

Return to your queue

My Scenes and My Values show the private account view after the server can read the session.

Next state

The account pages show read-only follow-up records for scenes and value facts.

Open my scenes

The home page does not bypass the runtime chain; it sends members to the existing read and request surfaces.

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.

Session-filtered views

Server authority

Join, hold, confirmation, value, and payment facts are derived by server paths, not client labels.

No client fact claims

Boundary honest

Staging keeps payout, production, and rollout limits visible instead of presenting planned work as done.

Owner-gated limits

3

Open pool lanes

0

Home runtime writes

T0

Presentation slice

What this page proves

The home surface can explain the product and route members into the current flow without becoming a source of identity, participant, value, payout, or production truth.

Start from here