Epic Priority and Action Plan

Reference document only. Authoritative work items live in Azure DevOps Boards (dev.azure.com/hybridcloudsolutions, project "Heritage Community Hub"). Use this file to orient sprint planning conversations; create and track actual items in ADO.

This file describes the current epic priority order and near-term planning actions derived from the canonical platform strategy (pmo/platform-strategy.md). Phase 0 (Decide) is complete — ADRs 0001-0024 are all Accepted.

---

Delivery sequence (revised 2026-06-17)

The platform follows a strict phase-gate model — no phase begins until the previous phase's definition of done is met — but the order is the revised, priority-driven sequence: the platform is first, the iOS app second, then the content/engagement features, then Android, then the rest. Each phase is owned by an ADO Epic; build work lives there as Features → User Stories → Tasks.

#	Phase	ADO Epic	Priority
0	Decide ✅ COMPLETE (2026-06-18)	Author detailed ADRs — AB#3154 (Closed)	done
1	Platform (foundation + identity, RBAC, member features, signups, family portal)	Build Platform — AB#3074	2
2	Apple (iOS) app	Deliver iOS (Apple) App — AB#3077	2
3	Sermons & Music Hub	Deliver Sermons and Music Hub — AB#3137	3
4	Community Calendar & Announcements	Deliver Community Calendar and Announcements — AB#3075	3
5	Messaging & Notifications	Deliver Messaging and Notifications — AB#3138	4
6	Google (Android) app	Deliver Android (Google) App — AB#3139	4
7	Additional features (Small Groups, Homeschool, Marketplace, member-posted media)	Deliver Additional Features — AB#3076	4
7	Signature features (Pony Express, Ride Share, Sister Community)	Deliver Signature Features — AB#3078	4

Phases 1–7 are build phases executed from the ADO board, not from this document — this file is the human-readable index that maps each phase to its ADO Epic.

---

Epic priority order

Phase 0 — Decide ✅ COMPLETE (2026-06-18)

ADO Epic: Author detailed ADRs (platform and per-feature) — AB#3154 — CLOSED

ADRs 0001-0024 all Accepted. All open decisions resolved (including MVP scope = the platform, delivered fully, first). See docs/internal/adr/ for the full index. No ADR remains Proposed.

Phase 1 — Build Platform · AB#3074

Priority: 2 (current phase; Phase-1 Features decomposed into User Stories + Tasks across 2026-Q3-S1..S4)

The platform is the most important deliverable — it owns everything every surface and feature depends on. Scope:

• Bicep IaC for free-tier Azure resources in infrastructure/; dev / test / prod environments.
• CI/CD pipeline (GitHub Actions — ADR 0004).
• Key Vault integration; all secrets via KV, none in repo.
• Observability baseline (Application Insights — ADR 0005).
• Compute on Azure Container Apps; PostgreSQL database (ADR 0024).
• Clerk auth (Apple/Google); member signups + minister approval; server-side RBAC (six roles).
• Account model, Family Groups, family portal, member profiles, parent-managed child sub-accounts.
• Core shared services: API framework, api-client, shared-types, ui design system, notifications transport, audit logging, media storage primitives.
• Scaffold apps/api, apps/web, apps/mobile, and all packages/* workspaces. (apps/landing is a retired placeholder — not deployed.)
• Web app as installable PWA: web app manifest, service worker, icons (including maskable); hosted on Azure SWA Free at heritageva.app (custom domain wired in Cloudflare at deploy time). The web app is the first usable client and testbed before iOS ships.
• Three-client model: web (apps/web), iOS (AB#3077, later), Android (AB#3139, later) — all clients of the same platform API via api-client SDK.

Phase 2 — Apple (iOS) app · AB#3077

Priority: 2. React Native + Expo iOS app consuming api-client; push notifications (APNs); offline cache/sync; App Store publishing via EAS Build.

Phase 3 — Sermons & Music Hub · AB#3137

Priority: 3. Sermons/video/music; inexpensive storage; web + mobile streaming; mobile offline download; member-only via RBAC. Distinct from member-posted media (back burner).

Phase 4 — Community Calendar & Announcements · AB#3075

Priority: 3. Calendar (events, RSVP, attendance, multi-view, recurring, role/group visibility, ICS feed) — the primary engagement driver — plus one-way Announcements (approver-authored; no replies).

Phase 5 — Messaging & Notifications · AB#3138

Priority: 4. Leadership one-way broadcasts + notifications service: multi-channel fan-out across SMS (Twilio) + push + email (SendGrid). No user-to-user chat.

Phase 6 — Google (Android) app · AB#3139

Priority: 4. Android app from the same React Native + Expo codebase; push (FCM); Google Play via EAS Build.

Phase 7 — Additional features · AB#3076

Priority: 4. Small Groups & Ministries; Homeschool Education Portal (two tiers — Resource Library + High School Program; COPPA-compliant, parent-managed accounts); Community Marketplace (member-only listings, no transactions); member-posted media (back burner).

Phase 7 — Signature features · AB#3078

Priority: 4 (long-term). Pony Express Delivery Network; Community Ride Share & Travel; Sister Community Integration. Community Learning Platform and Community Wellness & Support are candidate additions, not yet committed.

---

Cross-cutting Epics (also in ADO)

• Establish planning, docs, and repository foundation — AB#3150.
• Author detailed ADRs (platform and per-feature) — AB#3154 (Closed).
• Deliver interim public landing site — AB#3157 (superseded — no public site; web entry = apps/web at heritageva.app; retire/rescope in ADO).
• Author build-ready foundation documentation — AB#3177.
• Documentation accuracy and maintenance — AB#3197.

---

Near-term actions (planning)

Phase 0 is complete and the ADO delivery backlog already exists (Epics AB#3074-3078, AB#3137-3139, plus the cross-cutting Epics above; Features, User Stories, and Tasks decomposed per the work-items standard). The current planning effort keeps the board and these reference docs reconciled — no code, infrastructure, or pipelines are produced here.

1. Keep this file and pmo/project_roadmap.md in sync with the ADO Epic set and the canonical pmo/platform-strategy.md whenever priorities or AB# ids change.
2. For each phase as it is scheduled, confirm its Features/Stories/Tasks are decomposed in ADO with AC, priority, tags, area path, and a sprint iteration before activating the sprint.
3. Assign Phase-1 Features/Stories to the early 2026-Q3 sprints; later phases stay at the project-root backlog until scheduled.

---

Decisions locked (do not reopen)

• Monorepo, layered via workspaces (pnpm + Turborepo).
• React Native + Expo for mobile.
• ADO Boards as single source of truth for work items.
• Code and PRs on GitHub (Heritage-Virginia org); ADO Boards for work items linked via AB#.
• End-user auth: Clerk (Apple + Google social login); no Entra for end users.
• Compute: Azure Container Apps. Database: PostgreSQL (portable). (ADR 0024, supersedes ADR 0004.)
• Two-plane RBAC; six canonical roles; application authorization enforced server-side.
• Messaging = one-way broadcast announcements; no user-to-user replies.
• Marketplace = member-only listings only; no transactions.
• SMS: Twilio (provider-neutral adapter); email: SendGrid.

Open decisions

None block planning. All Phase-0 technology decisions are locked (ADRs 0001-0024 all Accepted), including MVP scope (the platform, delivered fully, first). Remaining choices — e.g. the roadmap/changelog-from-ADO sync mechanism — are build-time implementation details tracked in ADO.

---

"By wisdom a house is built, and through understanding it is established." — Proverbs 24:3