Practitionist / Practitionist/elluminar_web

πŸš€ Production launch readiness (tracking)

Open
#42 3 comments 0 reactions 1 assignee View on GitHub

@teetangh is already working on this.

Since Aug 9, 2026.

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
17h 2m
Merged PRs (30d)
18

Description

Epic tracking the path from working MVP to launchable, production-grade company.

Launch shape (decided 2026-07-17): private beta first (real payments, small invited cohort), then public launch.
Priority: πŸ”΄ beta-blocker = before ANY real user Β· 🟠 launch-window = during beta, before public launch Β· 🟑 = post-launch.

πŸ”΄ Tier 0 β€” beta blockers
  • #43 β€” πŸ”΄ Schema finalization & freeze (final additive migrations β†’ hard freeze + CI guard) β€” first milestone
  • #35 β€” πŸ”΄ Security & auth hardening (+ CSP & rate limiting: confirmed missing)
  • #36 β€” πŸ”΄ Legal pages subset: /terms, /privacy, /refund-policy, /contact + cookie banner (blocks #38 β€” Razorpay live activation requires these pages)
  • #37 β€” πŸ”΄ Real content & brand
  • #38 β€” πŸ”΄ subset: live keys + refund.processed webhook (currently stubbed) + event-id dedupe fix + refund e2e
  • Full GST invoice engine (pulled forward from #24 by founder decision): CGST/SGST/IGST split, SAC code, buyer GSTIN, InvoiceSeries gapless numbering, credit notes on refunds
🟠 Tier 1 β€” during beta, before public launch
  • #38 β€” 🟠 rest: subscription lifecycle/dunning/cancellations (payouts stay manual)
  • #39 β€” 🟠 Data, infra & reliability (+ Fermion webhook reconciliation job & outage runbook)
  • #40 β€” 🟠 Product completeness & QA (+ add Playwright e2e to CI β€” currently absent)
  • #36 β€” 🟠 rest: DPDP deletion/anonymization, consent capture, retention (hard enforcement May 2027; Consent Manager Nov 2026)
  • #12 β€” 🟠 PostHog analytics (pulled forward β€” funnel must exist AT launch to measure it)
  • #8 β€” 🟠 Referral codes (pulled forward)
  • #41 β€” 🟠 subset: CI gates on prod deploys, support email, incident basics
🟑 Tier 2 β€” post-launch
  • #41 β€” 🟑 rest of growth/ops
  • All post-mvp issues (#1–#29) in existing v1/v2 order β€” schema audit confirms none require migrations

State: landing + dashboards + full restyle shipped to dev→prod (a245761). Dev-auth bypass is NODE_ENV-gated; complex mock seed lives on dev only.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up β€” it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.