Run every MX Trek edition from one disciplined control surface.

Built for an independent nonprofit initiative connecting Mexico with scientists, entrepreneurs, investors, and public leaders currently pursuing graduate study at Harvard, Stanford, and MIT. The app keeps organizer operations rigorous while publishing only approved guidance to participants.

Brand mark

Organizer console and participant portal share one relational foundation, but visibility is controlled by role and sensitivity from day one.

Shared relational core

Treks, events, contacts, logistics, and finance live in one model instead of across disconnected sheets.

Sensitivity-first access

Participant-safe publishing is separated from internal notes, restricted contacts, and finance data.

Multi-year memory

People, venues, providers, and playbooks can carry forward from one edition to the next.

Mobile-first operations

The structure is designed to work on phones during live execution, not just on large desktop tables.

Product framing

Three operating modes

Planning mode

Build the edition: agenda, guests, logistics, bookings, costs, DRIs, and checklists.

Execution mode

Run the trip day by day with transport details, meeting points, on-point owners, and open issues.

Publishing mode

Release only approved schedule and logistics information into the participant portal.

Current build status

Preview-first, auth-next

One sign-in will eventually route organizers and participants by membership and role.

The current preview keeps `/portal` open so you can inspect the participant surface while auth is still a stub.

The next milestone replaces placeholder cards with the SQL schema, RLS, and live Supabase-backed reads.

Immediate backend milestone

Supabase project structure, schema migrations, permissions, and row-level security for the first real organizer modules.