Epics
⚠️
Scaffold — not synced to a real tracker. This page is a template for recording delivery epics. It intentionally contains no invented ticket IDs, dates, or assignees. Fill it from your actual issue tracker (Jira, Linear, GitHub Projects) or delete it if delivery tracking lives elsewhere. Delete this callout once populated.
How to use this page
An epic is a large body of work that delivers a meaningful outcome and groups many stories. Keep this list aligned with the Roadmap — each roadmap phase is usually one or more epics. Link every epic to its tracker item so this page stays a readable index, not a second source of truth.
Epic template
Copy per epic:
### <EPIC-ID> — <Epic title>
- **Tracker link:**
- **Roadmap phase:** (P0–P5 from /business/roadmap)
- **Goal / outcome:** what "done" delivers for a school or the business
- **Status:** proposed / in progress / done
- **Stories:** link to /jira/stories entries or tracker
- **Owner:** Suggested epics to record (derived from the roadmap — verify against your tracker)
These map to real roadmap themes; create/link the actual tracker epics rather than treating these as authoritative:
| Suggested epic | Roadmap phase |
|---|---|
| Security hardening (DB exposure, IAM, SSH→SSM) | P0 |
| Coordinated ship to production | P1 |
| Reliability (SES prod email, monitoring, N+1s, pagination) | P2 |
| Demo polish (remove “coming soon”, PDF download, dark mode) | P3 |
| Online fee collection (Razorpay) | P4 |
| Mobile parity (transport/hostel and beyond) | P5 |