Prompt starter summary:

• Add a short prose version of the Prompt starter here so the module intent is visible at a glance before the code block.

Prompt starter:

Implement the next <Feature> PRD slice. Use PRD/<module>/README.md as source of truth. The current goal is <goal>. Preserve these boundaries: page.tsx reads and orchestrates only, actions/ owns mutations, components render typed UI and user intent, api/route.ts is for external systems only, Prisma remains canonical data truth, and projection outputs are derived artifacts. Inspect <files/folders> before editing. Implement <specific slice>, keep <critical acceptance criteria>, and verify <route/action/output>.

<Feature / module name>

<One clear sentence defining what this feature does.>

This feature exists so users can:

• <primary user goal>
• <secondary user goal>
• <conversion or commercial goal>
• <support or operational goal>

Inside Molino App, this feature exists to:

• preserve canonical data authority
• expose a controlled UI surface
• connect to external projection or booking systems
• avoid duplicated client-side business logic
• keep Offer -> Order -> Projection paths stable

<Current problem, business need, or next milestone.>

This reduces or replaces:

• <manual workflow>
• <temporary page>
• <duplicated component>
• <external-only process>
• <spreadsheet/manual step>

This does not replace:

• Prisma as source of truth
• server actions as mutation authority
• Google Workspace projection layer
• external booking providers where applicable
• manual human support where business logic still requires it

This PRD covers:

• route: <route>
• module folder: app/(pages)/<entity>/
• components: <components>
• server actions: <actions>
• types: <types>
• external integrations: <systems>
• database models: <models>
• projection/export behavior: <outputs>
• admin workflow: <workflow>
• public UI behavior: <behavior>

This PRD does not cover:

• <future feature>
• <external system redesign>
• <unrelated module>
• <full automation not yet needed>
• <payment provider replacement>
• <native API integration if current milestone only uses widgets/buttons>

Possible later extensions:

• <API replacement>
• <dashboard>
• <analytics>
• <automation>
• <multi-language support>
• <admin sync interface>

Primary public users:

• travellers
• trip planners
• guests joining shared departures
• customers browsing city experiences
• partner referrals

Primary internal users:

• admin/operator
• guide/coordinator
• sales/support
• content editor
• trip planner

page.tsx       = read-only server orchestrator
actions/       = sole mutation authority
components/    = dumb UI / client intent only
api/route.ts   = external integration surface only
context/       = ephemeral client UI state only
types/         = shared domain truth
Prisma         = database truth
Apps Script    = external Google execution only

• No Prisma outside actions/.
• No mutations inside page.tsx.
• No internal app workflow should call its own API route.
• API routes are for outsiders, webhooks, CRON, callbacks, and external systems.
• Client components call server actions only.
• Derived views rebuild from canonical truth.
• LineItems are economic truth once generated.
• Projections must not recompute commercial totals independently.

app/
  (pages)/
    <entity>/
      page.tsx
      actions/
      components/
      context/
      types/
      api/
        route.ts

This feature touches or depends on:

<module>

User lands on route -> reads section or card -> selects product/session/trip -> clicks CTA -> booking or projection action starts -> external or internal reference is stored -> follow-up path begins.

Admin creates or updates canonical entity -> pricing or line items are generated or reviewed -> public projection renders -> external bridge is attached if needed -> offer, order, or projection can be generated.

User attempts action -> missing config, invalid data, or external failure -> UI shows controlled fallback -> system logs issue -> canonical state remains safe.

The feature must display:

• <field>
• <field>
• <computed value>
• <status>
• <CTA>

The feature must allow:

• <create action>
• <update action>
• <archive or delete action>
• <sync action>
• <projection action>

All mutations must happen through:

app/(pages)/<entity>/actions/

<ModelName>

Yes | No

Store external IDs when needed:

model ExternalRef {
  id          String   @id @default(cuid())
  entityType  String
  entityId    String
  provider    String
  externalId  String
  externalUrl String?
  metadata    Json?
  createdAt   DateTime @default(now())
  updatedAt   DateTime @updatedAt
}

app/(pages)/<entity>/types/<entity>.types.ts

export type ModuleStatus = "draft" | "active" | "archived" | "published";

get<Entity>.ts create<Entity>.ts update<Entity>.ts archive<Entity>.ts sync<Entity>.ts project<Entity>.ts

• validate input
• access Prisma only inside the action
• avoid UI assumptions
• return a typed result
• revalidate relevant path or tag after mutation
• avoid calling internal API routes