The 24 enhancement issues: proposed stages
Status: proposal. Nothing here has been applied. Approve, or say which rows to move. Parent: the milestone sort plan
The test used on every row, from the launch plan: if December were cancelled tomorrow, would we still do this? Yes means Prototype. No means Alpha. Beta is for work that only makes sense once Alpha has run.
Prototype: we would do these regardless of December
| Issue | Why |
|---|---|
| #125 Discord search and preset categories | Internal issue-triage tooling. No user sees it |
| #134 Auto-shutoff and wave rules | Core lantern mechanics, not launch-shaped |
| #224 OSM import server-side for fraud handling | Infrastructure hardening we want either way |
| #275 Audit Cloud Run proxy coverage | Platform hygiene |
| #280 Image processing service | Infrastructure |
| #287 Explore Firebase Data Connect | Exploration, no launch dependency |
| #324 Decompose Dashboard, introduce Zustand | Refactor. Improves everything downstream |
| #350 Extract OfferCards and AdSlot to shared | Refactor |
| #241 Non-GitHub users submit issues | Contributor intake |
| #853 Skill for keeping timeline docs current | Agent tooling |
Alpha: December needs these
| Issue | Why |
|---|---|
| #231 Merchant-user association in the admin portal | Alpha has merchants, and someone has to manage them |
| #237 Admin portal configuration management | Running a pilot means changing settings without a deploy |
| #238 Resend integration, system health and billing | Transactional email is part of a live launch |
| #799 LLM moderation before the keyword check | Real users post real content, and moderation is a safety surface |
| #850 Reissue an admin's app invite link | Invite-gated signup makes reissuing an operational need |
| #851 Show what access each admin actually has | Access review matters once real user data is in there |
| #823 Event tracking icon by source | Small, and it is admin legibility during a live pilot |
| #824 Merchant venue detail page | Merchants edit venues during a pilot; inline controls do not scale |
| #323 Hero card venue photo and lantern count | First impression at a venue, which is the Alpha moment |
| #362 Escalating backup nudge | Losing a passphrase is unrecoverable, and Alpha is when real accounts start existing |
Beta: only makes sense after Alpha has run
| Issue | Why |
|---|---|
| #162 Bonfire, the event feature | Group meeting, beyond the two-person loop Alpha exists to prove |
| #167 Merchant community portal and tools | Alpha merchants are hand-provisioned and few |
| #171 Merchant claim-venue UI flow | Self-serve claiming needs merchants we have not recruited yet |
| #239 AI assistant in the admin portal and Discord bot | Useful, not load-bearing for a pilot |
The rows I am least sure of
#134 auto-shutoff and wave rules. Filed as Prototype because it reads as core mechanics, but "wave rules" could be exactly the behaviour an Alpha event depends on. If these change how a wave behaves during a scheduled evening, it is Alpha.
#362 backup nudge. Filed as Alpha on the reasoning that unrecoverable accounts start existing at Alpha. Arguable as Prototype, since the risk exists the moment anyone has an account.
#239 AI assistant. Filed as Beta, but if it is what makes the admin portal usable during a live pilot, it moves.