Launches

From the dashboard or /app/launches, Create launch inserts a row in launches with created_by = auth.uid() and an empty blueprint stub. Activity is logged as launch_created.

Name, product, audience, goal, status, and target date are editable from the launch detail page. Updates write through to Supabase, recompute readiness, and log launch_updated.

Deletion requires a typed confirmation. All launch-scoped rows (blueprint, tasks, assets, messages, contacts, timeline, feedback, debrief) cascade via the user_can_access_launch RLS path. Action logs as launch_deleted.

Duplicate copies the launch shell and blueprint structure into a new launch — names, fields, and channel scaffolding only. Tasks, assets, outreach, signals, and debrief are intentionally not copied to avoid stale records.

• Draft — early planning.
• Planned — date set, prep underway.
• In progress — launch week.
• Launched — live; signals being collected.
• Archived — debrief done, kept for reference.

Create sample launch on the empty dashboard inserts a fully populated launch tagged [SAMPLE] across all modules. Sample data is never auto-seeded and is fully deletable like any other launch.