Status: global entry point for Molino app documentation, planning, and build guidance.

This is the quick access page for the ongoing documentation and delivery process. It should stay broad and practical: the root points to the current work, the feature hubs, and the larger planning layers.

In this staging clone, dev-docs/ is the rendered documentation root. The copied production PRD tree lives at dev-docs/_PRD and should be treated as the more current product reference when compared with older MLVs or milestone notes.

• Main dev docs
• Commercial pipeline + projection plan
• Staging lane
• Molino Stageup public overview
• AI-operated staging clone
• Trips human layer checklist
• Milestones roadmap
• Micro goals benchmark list
• Recursive codebase audit playbook

• Stage Molino Index clone as the first implementation and testing lane before main-project integration
• Trips-first commercial app flow
• Document-driven orchestration
• Offer / Order / LineItems snapshots
• Apps Script office server exports
• Shared pricing and projection patterns
• DRY standardization across modules

The codebase works in multiple modes:

• core boilerplate
• Trips-first product surface
• demo SaaS / showcase deployment
• reusable vertical package
• client-specific installations

The root docs should help you move between those modes without duplicating the same rules in every folder.

• Trips
• Assistant
• Document
• Apps Script
• Framework
• Experiences
• Offers
• Orders
• Products
• Concept Cards
• Session Stacks
• Study Guide
• Home
• Studio
• Users
• Projects
• Integrations
• Recap
• Milestones
• Micro goals
• Sheet index
• Magazine / social
• Project branding
• Weekly support sponsor
• Sponsor

• Put feature truth in the matching domain folder.
• Keep the root as a short global landing page.
• Archive old versions locally instead of deleting them.
• Use copied _PRD material as current product direction.
• Use MLVs, milestone notes, and archives as helpful background when they do not conflict with current docs or code.
• Keep public staging notes in the rendered dev-docs/staging/ and dev-docs/trips/ layer when they are meant for collaborators rather than internal implementation-only planning.