Build a launch-readiness workflow that tracks feature launches and tells everyone, at a glance, whether each one is clear to ship. The goal is to turn scattered project status into a single, trustworthy GO / NO-GO verdict per launch, and to nudge owners proactively so nothing ships with unresolved blockers. Let owners self-serve. Build a space-authenticated dashboard (an HTTP route) where anyone can paste a project link from your project tracker — Asana, or whatever your team uses — to start tracking a launch, and remove launches from the same page. Persist the tracked-project list in durable shared storage with a single writer, so the registry survives across runs. Back the dashboard with an API route that reads and writes that registry (add/list/remove), and a second data route that pulls one project's tasks from the project tracker and normalizes them into a checklist. Each task should carry an owner, a due date, a priority, and a status; derive a launch date per project. Define a clear, deterministic blocking rule (e.g. high-importance tasks that are flagged at-risk and not yet resolved block the launch) and compute a GO / NO-GO verdict from it. The dashboard should show a list of tracked launches with per-launch verdict badges, and a per-launch view with the GO / NO-GO banner, percent complete, a launch countdown, the blocking items, and the full checklist — all sourced live from the tracker. Add two scheduled notifications (cron): a weekly summary posting each tracked launch's readiness, and a daily day-before check that posts a go/no-go verdict for anything launching tomorrow. Send these to Slack — or your team's chat tool. Triggers: HTTP routes for the dashboard and its API/data endpoints; two cron schedules for the notifications. Keep it read-only against the project tracker; the only writes are to the project registry and the chat notifications. Tools used: Asana API, Slack API, 3B named volume (durable storage), React dashboard, cron schedules, HTTP routes