H1Sponsor PRD - Molino App
version: 2026.04
status: active
owner: Molino
scope: app/sponsor
last_updated: 2026-04-24
H10. Implementation Snapshot
H2Current goal
H3Keep Sponsor as the weekly support workflow
Use it for booking, donations, updates, challenges, and feature conversion.
H2Remaining features
H3Keep week booking, donation, completion, approval, proposal, conversion, and update actions explicit
Make the state transitions visible.
H3Preserve server-action authority for every state transition
Do not move the workflow into client state.
H3Keep Sponsor UI responsive on mobile and desktop
Maintain a usable support surface on both form factors.
H3Avoid turning sponsor support into a generic checkout
Keep the weekly system distinct from retail commerce.
H2Next build steps
H3Inspect `app/sponsor/actions/`, route pages, and `SponsorUIContext`
Check the current workflow surface before changing it.
H3Verify each workflow transition has a named action and clear resulting state
Keep the state flow explicit.
H3Keep context limited to UI state
Do not let it hold business truth.
H3Test `/sponsor`, `/sponsor/history`, and `/sponsor/[weekId]` after workflow changes
Validate the support routes after each change.
H2Prompt starter summary
- Preserve the weekly support workflow for booking weeks, donations, updates, challenge approval/proposal, and feature conversion inside server actions.
H2Prompt starter
Implement the next Sponsor PRD slice. Use PRD/sponsor/README.md as source of truth. Sponsor is a weekly support workflow for booking weeks, donations, progress updates, challenge approval/proposal, and conversion into features. Keep every state transition in app/sponsor/actions/ and keep route components read/orchestration focused. SponsorUIContext is UI state only. Do not replace the weekly system with a generic checkout. Verify /sponsor, /sponsor/history, and /sponsor/[weekId] on mobile and desktop.
H21. Product Identity
H3Name
Sponsor
H3One-line Definition
Sponsor is the weekly support and challenge flow for booking, donations, progress updates, and conversion into features.
H3User-facing Purpose
This feature exists so users can:
- book or support a week
- donate or confirm support
- follow progress and status
- convert interest into structured participation
H3Internal Platform Purpose
Inside Molino App, this feature exists to:
- manage a sponsor-specific weekly system
- keep support actions auditable
- preserve status transitions in server actions
H22. Scope
H3In Scope
- route:
/sponsor - route:
/sponsor/history - route:
/sponsor/[weekId] - actions:
bookWeek,addDonation,completeWeek,approveChallenge,proposeChallenge,convertToFeature,postUpdate - models:
WeekSlot,Donation,WeekUpdate,WeekAssignment,Contribution,Reward - UI components: banners, grids, modals, and booking surfaces
H3Out of Scope
- replacing the sponsor workflow with a generic commerce checkout
- hiding weekly state transitions in the client
H23. Authority Model
- server actions own booking and mutation steps
- route components read and orchestrate
- context remains UI state only
H24. Current Implementation Surface
app/sponsor/page.tsxapp/sponsor/history/page.tsxapp/sponsor/[weekId]/page.tsxapp/sponsor/actions/app/sponsor/context/SponsorUIContext.tsx
H25. Acceptance Criteria
- sponsor flows render cleanly on mobile and desktop
- booking and donation actions remain explicit
- archived notes stay local to the module
H26. Locked Summary
Sponsor is Molino's support-and-week system. It should stay an action-driven workflow with clear state transitions and no hidden client authority.