e41ecfad4c
Include Loyalty/Communication/Sports Center backends and registry updates alongside production nginx and compose wiring. Co-authored-by: Cursor <cursoragent@cursor.com>
6.2 KiB
6.2 KiB
Sports Center Platform — Roadmap
Registration document. No implementation in this phase.
Framework: ai-framework/ · ADR: ADR-014 · Manifests: phase-manifest.yaml, service-manifest.yaml
| Field | Value |
|---|---|
| Service | sports_center |
| Database | sports_center_db |
| Permission Prefix | sports_center.* |
| Phases | 9.0 – 9.10 |
| Status | Phase 9.2 Member Management complete; next 9.3 Coach & Staff Management |
Vision
Deliver an independent, multi-tenant Sports Center Platform inside TorbatYar so clubs, gyms, and facilities can manage members, memberships, coaches, attendance/access, bookings, training, competitions, and integrations — without owning Accounting, CRM, Loyalty, or Communication.
Business Scope
In scope (over Phases 9.0–9.10):
- Sports members and membership lifecycle (plans, packages, renewal, freeze, transfer)
- Coaches / trainers and assignments
- Attendance and access control (including access devices)
- Booking and scheduling (facilities, courts, sessions, equipment)
- Training programs and workouts
- Competitions and sports events
- Medical / nutrition / locker / mobile as planned modules (depth per phase scope)
- Reports and analytics shells
- Integrations with Accounting, CRM, Loyalty, Communication via API/Events
Architecture Scope
| Rule | Reference |
|---|---|
Independent service + sports_center_db |
ADR-014, ADR-001 |
| Layering API → Service → Repository → Model | service-architecture.md |
| Tenant-aware business tables | ADR-003 |
Outbox-ready events sports_center.* |
ADR-006 |
| No journal ownership | ADR-010 |
| Messaging via Communication only | ADR-012 |
| Loyalty via Loyalty service only | ADR-011 |
| AI optional / independent | ai-architecture.md |
| Implementation via AI Framework | ai-framework/ |
Module Map
| Module | Responsibility | Introduced |
|---|---|---|
| Members | Sports member profiles and identity refs | 9.2 |
| Membership | Active membership instances / lifecycle | 9.2 |
| Membership Types | Plans, packages, commercial definitions | 9.1 |
| Packages / Plans / Pricing | Catalog commercial definitions | 9.1 |
| Age Groups / Sport Categories | Catalog eligibility grouping | 9.1 |
| Membership Rules / Policies | Renewal, freeze, expiration, rules | 9.1 |
| Coaches | Coaches / trainers / staff | 9.3 |
| Attendance | Check-in/out and attendance records | 9.5 |
| Booking | Reservations for facilities/sessions/equipment | 9.4 |
| Facilities | Buildings, rooms, courts, zones | 9.0 / 9.4 |
| Equipment | Bookable / trackable equipment | 9.4 |
| Programs | Training programs | 9.6 |
| Workouts | Workout definitions and assignments | 9.6 |
| Competitions | Competition definitions / results shells | 9.7 |
| Events | Sports calendar events | 9.7 |
| Medical | Clearance / note refs (privacy-aware) | 9.2+ |
| Nutrition | Nutrition plan shells | Later |
| Locker | Locker assignment status | 9.0 |
| Mobile | Mobile API contracts / deep links | Cross-cutting |
| Reports | Operational reports | 9.9 |
| Analytics | Metrics export shells | 9.9 |
| Integrations | CRM / Loyalty / Communication / Accounting adapters | 9.8 |
Canonical inventory: module-registry.md.
Integration Map
Sports Center ──API/Events──▶ Accounting (payments → postings via Posting Engine)
Sports Center ──API/Events──▶ CRM (lead/contact refs only)
Sports Center ──API/Events──▶ Loyalty (enrollment / points refs)
Sports Center ──API/Events──▶ Communication (SMS/OTP/notifications)
Sports Center ──API─────────▶ Core (entitlement, tenant)
Forbidden: cross-DB queries, embedding providers inside Sports Center for SMS, creating JournalEntry locally.
Phase Map
| Phase | ID | Name | Status |
|---|---|---|---|
| 9.0 | sports-center-9.0 |
Foundation | Complete |
| 9.1 | sports-center-9.1 |
Membership Catalog | Complete |
| 9.2 | sports-center-9.2 |
Member Management | Complete |
| 9.3 | sports-center-9.3 |
Coach & Staff Management | Planned |
| 9.4 | sports-center-9.4 |
Scheduling & Booking | Planned |
| 9.5 | sports-center-9.5 |
Attendance & Access Control | Planned |
| 9.6 | sports-center-9.6 |
Training Management | Planned |
| 9.7 | sports-center-9.7 |
Competition & Event Management | Planned |
| 9.8 | sports-center-9.8 |
Financial Integration | Planned |
| 9.9 | sports-center-9.9 |
AI & Analytics | Planned |
| 9.10 | sports-center-9.10 |
Enterprise Validation | Planned |
Details (dependencies, required docs/services, completion criteria): phase-manifest.yaml.
Future Expansion
- Wearable / IoT access device adapters
- Multi-branch franchise hierarchies (still tenant-scoped)
- Academy / youth pathways as related modules without absorbing Academy service ownership
- Deeper medical compliance connectors when regulated
Out of Scope
- Owning Accounting ledgers or Posting Engine
- Owning Sales CRM aggregates
- Owning Loyalty ledger / campaigns
- Owning SMS/email providers (Communication owns them)
- Replacing Core tenant membership (platform Member ≠ Sports Member)
- Implementing Phase 9.x code in the registration phase
- Restaurant / Ecommerce / Marketplace domains