H1Molino Stageup
version: 2026.04
status: staging public interface
owner: Molino
last_updated: 2026-04-28
Molino Stageup is the shareable staging surface for Molino's public product story. It is meant to be clear enough for non-developers while staying close to the real product architecture behind the scenes.
This version can be used with co-founders, colleagues, collaborators, potential sponsors, and supporters when the production app is too technical, sensitive, or unstable to share directly.
Live staging app: https://molino-staging.vercel.app/
H2What This Staging App Is For
- presenting Molino's travel, practice, and cultural work in a familiar public web format
- previewing commercial surfaces before they are fully locked in production
- turning internal product plans into readable public-facing documentation
- helping supporters understand where Molino is going
- keeping the staging link useful as a friendly mockup and conversation surface
H2Current Public Priorities
| Area | Public Meaning | Current Stage |
|---|---|---|
| Trips | The visible travel and booking hub for Molino experiences | active staging narrative |
| Studio | The broader practice and project entry point | staging bridge |
| Travel | A first revenue-capable booking path connected to Trips | planned or staged bridge |
| Collaborations | A pathway for partners, sponsors, and supporters | public-facing concept |
| Documentation | Rendered PRD pages that can be shared without developer context | active |
H2Public Positioning
Molino is building a travel and cultural practice platform around guided experiences, flexible trips, local knowledge, collaborations, and public documentation.
The staging app should make that understandable without exposing raw implementation detail. Public staging pages should read like useful public interfaces, not internal engineering notebooks.
H2Documentation Rules
- Write for non-dev readers first.
- Keep technical implementation details brief and clearly separated.
- Mark staged, planned, and production-ready behavior honestly.
- Avoid private operational notes in rendered public documents.
- Use stable filenames because they may appear in routes, document lists, or public links.
- Keep the root index practical and current.
H2Key Documents
H2Working Pattern
Work through the staging app one tab at a time. Trips is the current focus. Each tab should get a public-facing page plus a practical human checklist when there is a Google Doc or review sequence behind it.
Code changes should be tested in the staging clone first, deployed through the Vercel staging site, and only later integrated into the main project after review.
H2Session Notes
H32026-04-28 - Live Vercel staging URL added
Recorded https://molino-staging.vercel.app/ as the public staging surface and linked the AI-operated staging clone note. The staging app is the review lane for public mockups, sponsor-friendly documentation, and AI-assisted development experiments before main-project integration.
H32026-04-28 - Local stageup notes contextualized
Imported the relevant local Stageup notes from New project 3.zip into the rendered dev-docs structure without replacing the existing internal _PRD tree. The public staging overview now lives under dev-docs/staging/, while the active Trips review sequence lives under dev-docs/trips/.
H32026-04-28 - VS Code Codex instructions added
Added root AGENTS.md instructions and a Trips human layer checklist so the assistant can follow the current staged workflow: one tab at a time, public-readable docs first, implementation truth preserved underneath.
H32026-04-28 - Public staging documentation started
Adapted the production Trips PRD material into a staging-oriented documentation structure. The goal is to make staging docs work as a public interface for non-developers while still preserving enough implementation truth for future Codex sessions.