How abhishek21lift-oss/619-erp-backend works
619 Fitness ERP is a multi-studio fitness operations backend. Staff manage personal-training clients and their plans; members access their own profile, payments, workouts, diet, consent forms, and messages. Progress and business metrics support operational decisions, while automation queues client communications. Platform administrators have separate oversight and storage-accounting capabilities. The graph emphasizes source-supported runtime links; several broader subsystems are visible in the tree, but their wiring was not sampled.
Main entry points: pool.js PostgreSQL · client-portal.routes.js Member portal · pt-os.routes.js PT operations · progress.routes.js Progress tracking
Components 24
PT Operations
- PT operations
src/modules/pt-os/pt-os.routes.js - PT services
src/modules/pt-os/pt-os.service.js - Progress tracking
src/modules/progress/progress.routes.js - Fitness scoring
src/modules/progress/fitness-scoring.js - Payments API
src/routes/payments.js
Member Experience
- Member portal
src/modules/client-portal/client-portal.routes.js - Portal services
src/modules/client-portal/client-portal.service.js
Insights Automation
- Insights API
src/modules/insights/insights.routes.js - Metric engine
src/modules/insights/metric-engine.js - Insights engine
src/modules/insights/insights-engine.js - Automation engine
src/modules/automation/automation.engine.js - Automation repository
src/modules/automation/automation.repository.js - WhatsApp service
src/services/whatsapp.service.js
Platform Operations
- Super-admin API
src/modules/platform/super-admin.routes.js - Storage reporting
src/modules/platform/super-admin/storage.js
File Storage
- File storage
src/lib/fileStorage.js - Storage ledger
src/lib/storageLedger.js
Other components
- Studio staff
- Studio member
- Payment provider
- PostgreSQL
src/db/pool.js - Studio decision-maker
- Platform administrator
- R2 object storage
Connections 25
- Studio staff → PT operations: manages clients
- PT operations → PT services: calls services
- PT operations → PostgreSQL: reads and writes
- Studio staff → Progress tracking: records progress
- Progress tracking → Fitness scoring: scores fitness
- Progress tracking → PostgreSQL: reads and writes
- Studio member → Member portal: accesses account
- Member portal → Portal services: requests portal data
- Member portal → PostgreSQL: reads and writes
- Member portal → File storage: serves consent PDF
- Studio staff → Payments API: records payments
- Payments API → PostgreSQL: reads and writes
- Payments API → Payment provider: payment integration
- Studio decision-maker → Insights API: requests insights
- Insights API → Metric engine: requests metrics
- Metric engine → PostgreSQL: queries canonical data
- Metric engine → Insights engine: provides metrics
- Automation engine → Automation repository: loads rules and records outcomes
- Automation engine → WhatsApp service: enqueues messages
- Platform administrator → Super-admin API: administers platform
- Super-admin API → Storage reporting: mounts storage API
- Storage reporting → PostgreSQL: queries storage records
- File storage → R2 object storage: stores and serves files
- File storage → Storage ledger: records file changes
- Storage ledger → PostgreSQL: records attribution