Profile
Self profile draft and public projection are available through existing server-authority paths.
Member hub
Review the account facts this staging build can show today: your sign-in session, editable public profile draft, submitted capability requests, and read-only presence. Profile copy helps other members understand who they are meeting; runtime, payment, settlement, and payout decisions still come from server-side facts.
Each Member Hub capability declares whether it is released, deployed, entitled, role-gated, data-backed, and interactive. Unavailable capability cards are information, not fake buttons.
Profile
Self profile draft and public projection are available through existing server-authority paths.
My Values
Private value records are readable when the server can read this account; the page is not a wallet.
Memory
Memory is a static/public-safe preview plus lifecycle scaffold. Creation and entitlement remain planned.
Verification
Capability requests can be submitted; reviewer decisions remain scoped and do not upgrade public badges yet.
Reports
Report rows are submit/self-view plus reviewer read-only queue; no handling lifecycle is exposed.
Partner
Provider/partner presentation reads supply-side scenes, but partner approval and payout setup remain owner-gated.
This envelope does not grant roles, create entitlements, call a paywall, complete reviewer work, create memories, or move money.
Add and verify a mobile number on top of your email account. This does not replace email sign-in; it is an extra trust signal, and for in-person scenes a verified phone can be required before you join.
Checking your phone-verification status.
Verification runs through Supabase Auth and the owner-configured SMS provider. The app never fabricates a verified state; verification is read from the server.
Profile draft only. Verification, runtime, payment, and payout remain blocked. Public projection is read-only in this preview.
The legacy profile mixed public identity, private contact, verification evidence, vehicle facts, and future payout binding. TribeRide separates those zones before adding more fields.
T0 · Public profile
Member-facing profile copy such as public name, locale, and visibility. This is the only self-edit profile zone live today.
T0 · Private contact
Phone, emergency contact, and contact preferences need a contact reveal policy before storage.
T1 · Verification evidence
License, insurance, plate, and capability evidence belong behind reviewer/operator access with expiry and revocation.
T2 · Payout binding
Provider account, KYC, and receiver references are owner-operated T2 facts, not profile self-service fields.
T3 · System signal
Risk, abuse, and trust assertions are internal read-only facts and must not become public profile labels.
This panel is a policy scaffold only. It does not upload documents, store private contact fields, approve verification, bind payout receivers, or expose system signals.
Profile context · tier T1
This form only files a T1 request for review. Your identity is taken from the signed-in session, not typed into the form, and the saved request remains pending_review until a reviewer acts. T0 profile edits, T2 payout binding, and T3 system signals stay on their own authority paths. Reviewer approval is recorded as request state; it does not yet upgrade the public profile badge or create a payout/trust guarantee.
Your submitted requests
No capability requests are visible yet. Sign in to view your verification requests.
Hosting · payout account
This environment cannot store a payout account binding yet, so nothing can be connected here. Nothing about your account has been changed.
TribeRide does not pay hosts yet. Participant payments are not routed to host accounts on this build, and no payout runs — connecting an account only prepares for that, and does not schedule it, promise it, or give it a date. Completing the provider’s onboarding does not change what you are owed or when.
reports · server-submitted
This form creates an open report through server authority as a row visible to you under current RLS. You get your own self-view; an allow-listed reviewer can acknowledge, resolve, or dismiss it. Once an outcome is terminal you can appeal it once below. This build applies no penalty, score, refund, SLA, or money outcome, and your identity comes from your signed-in session, not from a field in the form.
scene review details
Completion and feeling are stored inside the existing report body. They do not decide settlement, payout, or account standing.
Your submitted reports
This list is your own RLS-filtered self-view and your appeal receipt. Stored states show the report row state and any appeal status only; they are not a claim about a penalty, refund, or money outcome.
Sign in to view your reports. Reports you submit from this panel will appear here after the server accepts the row.
These cards are the public projection of profile rows currently readable by this page. Capability labels and request states are context only; they do not create booking authority, payment status, payout readiness, or trust guarantees.
Host capability review candidate · pending_review
preview · sign in to see yours
Profile projection seed · blocked_by_gate
preview · sign in to see yours
Derived, cosmetic, and non-authoritative. These numbers are calculated from participation history visible to this account. They do not create rewards, verification, runtime authority, settlement, payout, or commercial eligibility.
Internal readouts for staging review. These panels explain what the server observed; they do not approve payments, settlement, payout, or production readiness.