Heritage Docs

Appearance

Future Epics — Heritage Community Hub ​

Reference document. These are the later-phase epics in the revised delivery order (see pmo/platform-strategy.md §Delivery roadmap and pmo/project_roadmap.md). They are scheduled after the platform (AB#3074) and iOS app (AB#3077). All have ADO Epics already created; Features/Stories/Tasks are decomposed when each phase is scheduled. See pmo/platform-strategy.md for the canonical feature inventory and phase definitions.

Delivery order reminder: Platform (AB#3074) → iOS (AB#3077) → Sermons & Music Hub (AB#3137) → Calendar & Announcements (AB#3075) → Messaging & Notifications (AB#3138) → Android (AB#3139) → Additional features (AB#3076) → Signature features (AB#3078).

Sermons & Music Hub · ADO Epic AB#3137 ​

Delivery position: 3 (after the platform and iOS app) ADO priority: 3

Overview: Post weekly sermons (video), videos, and music (audio). Inexpensive S3-compatible/Blob storage; web streaming; mobile streaming and offline download; member-only via RBAC; all original community content, no DRM. Distinct from member-posted media (event/wedding photos), which is a separate back-burner feature under Additional Features.

Key features:

  • Weekly sermon video posting and streaming.
  • Music (audio) and video library.
  • Inexpensive storage via a signed-URL StorageProvider abstraction (Cloudflare R2 / B2 / Stream vs Azure Blob — ADR 0010).
  • Web streaming + mobile streaming and offline download.
  • Member-only gating enforced server-side via the API.

Additional features · ADO Epic AB#3076 ​

Scheduled after Android. Groups several capabilities under one Epic.

Homeschool Education Portal — two tiers ​

ADO priority (when scheduled): 3

Overview: Heritage's homeschool program, integrated with the main community hub via the shared Account/Family-Group model. Parent-managed student accounts with COPPA-compliant access controls — students do not self-register. Two tiers per ADR 0015:

Tier 1 — Resource & Support Library (all families, all ages; ships earlier, lightweight):

  • Recommended-resource links and unit studies.
  • The community's homeschool convictions/philosophy.
  • Downloadable community-specific end-of-year evaluations and required forms.
  • Browse/download only — not assignments or grades.

Tier 2 — High School Program (dedicated; LMS-like; deferred for deeper design):

  • High school classes the community offers — homework assignments, class events, class times/calendar.
  • Teacher back-end: collaboration, gradebook, notes.
  • Needs deeper design as its phase approaches (teacher role, gradebook, enrollment).

Both tiers: parent-managed student accounts (no student self-registration; no student email required); COPPA-compliant access controls and parental-consent flow; communication uses the one-way broadcast model consistent with platform messaging rules. Authorization uses the platform's six canonical roles (the teacher back-end is scoped within ministry_leader/admin capabilities, not a separate identity system).

Community Marketplace ​

ADO priority (when scheduled): 3

Overview: Member-only classifieds and vendor/business listings. Browse and reviews only. No payment processing or transactions of any kind — this is a listings board, not a commerce platform.

Key features:

  • Item listings and categorization (classifieds).
  • Vendor/business directory listings.
  • Browse and member reviews.
  • Community member verification (closed community — membership approval already gates access).
  • Service offerings directory (childcare, tutoring, trades, etc.).

Out of scope for this epic: payment processing, delivery coordination (that is Pony Express, a Signature feature), barter/trade transaction facilitation. See ADR 0016.

Small Groups and Ministries Management ​

ADO priority (when scheduled): 3

Overview: Tools for managing small group membership, ministry teams, meeting coordination, and group-scoped communications. See ADR 0017.

Key features:

  • Small group and ministry team directory.
  • Group membership management by group leaders.
  • Meeting scheduling integrated with the Community Calendar.
  • Group-scoped announcements (one-way broadcast, same model as platform-wide announcements).
  • Resource sharing within groups.
  • Member-posted media (back burner) — event/wedding/engagement photos, separate from the Sermons & Music Hub.

Mobile apps (two separate Epics, two delivery positions) ​

Both apps ship from one React Native + Expo codebase, reusing api-client, shared-types, and shared-utils — no logic duplication. They are delivered as two separate Epics at two different positions in the revised order, not one combined mobile phase.

Apple (iOS) app · ADO Epic AB#3077 — delivery position 2 ​

ADO priority: 2 (immediately after the platform). See ADR 0009.

  • iOS app at parity with the web platform; push notifications (APNs).
  • Offline cache and sync for core features.
  • App Store publishing via EAS Build.

Google (Android) app · ADO Epic AB#3139 — delivery position 6 ​

ADO priority: 4 (after Messaging & Notifications). See ADR 0014.

  • Android app from the same codebase; push notifications (FCM).
  • Offline cache and sync; mobile-optimized calendar and RSVP flows.
  • Google Play publishing via EAS Build.

Signature features · ADO Epic AB#3078 ​

Long-term, delivered last.

Pony Express Delivery Network ​

ADO priority (when scheduled): 4

Overview: Coordination network for community members who travel and can carry items between households or communities.

Key features:

  • Route registration for traveling members.
  • Item transport request and offer matching.
  • Multi-community delivery network.
  • Rider identity verification (closed vetted membership already provides a baseline).
  • Delivery tracking and status updates.

Security note: Physical-safety ADR (S2 from security audit) must be addressed before this epic is built. Identity verification, report/block, and liability/waiver design are required.

Community Ride Share and Travel Coordination ​

ADO priority (when scheduled): 4

Overview: Coordinate community ride sharing for events, errands, and travel.

Key features:

  • Ride request and offer system.
  • Route matching for community events.
  • Regular commute and errand matching.
  • Driver screening (vetted membership is a baseline; additional verification TBD).
  • Cost-sharing coordination (no payment processing on-platform).

Security note: Same S2 physical-safety requirements as Pony Express apply.

Sister Community Integration ​

ADO priority (when scheduled): 4

Overview: Connect with other Heritage communities for joint events, resource sharing, and coordinated activities.

Key features:

  • Multi-community event coordination and shared calendar views.
  • Resource sharing between communities.
  • Sister community directory and networking.
  • Inter-community member visit coordination.
  • Best-practice sharing platform.

Candidate future epics (not yet committed to roadmap) ​

Community Learning Platform ​

A skill-sharing and adult-education platform separate from the Homeschool portal. Community workshops, guest speakers, mentorship coordination, and a learning resource library. Not yet assigned to a phase.

Community Wellness and Support ​

Mutual support tools covering care coordination (meal trains, support visits), wellness challenges, healthcare provider directory, and a prayer request system. Not yet assigned to a phase.

The delivery Epics above already exist in ADO (AB#3076, AB#3077, AB#3078, AB#3137, AB#3139); their Features, User Stories, and Tasks are decomposed when the preceding phase gate is met, not before. Candidate epics get an ADO Epic only once committed to a delivery position.

Heritage Community Hub — Internal. Access restricted via Cloudflare Access + Entra ID.

Heritage Virginia · Owner: Kristopher Turner