Public V1 Scope Contract

Purpose

Public V1 is the complete first public launch scope for CoachMe. It is not a small partial launch. The app can be built, tested, and accepted through narrow internal milestones, but public release waits until the required Public V1 scope is complete and the readiness gates are satisfied.

This contract is the source of truth for launch naming:

• Public V1: required before the first public app release.
• V1 baseline: feature-level policy, limit, provider stance, or implementation constraint used for Public V1.
• Internal Milestone: private build/test sequence used to deliver Public V1 one feature group at a time.
• V1 Candidate / Needs Decision: useful for Public V1, but not yet confirmed as required before public launch.
• Post-V1: explicitly deferred until after the first public launch.

Product Surfaces

Public V1 keeps separate app experiences while sharing one identity, backend, contracts, and role/workspace model.

• Coach Web: the primary dense creation and management surface.
• Coach Mobile: coach-facing mobile operations, task inbox, review, messaging, client profile/progress, nutrition review, risk signals, and lightweight actions. Full mobile-native builder parity is not a Public V1 launch blocker.
• Client / Personal Mobile: daily execution, onboarding, logging, progress, messaging, and personal/self-coaching behavior where enabled.

A single user account can hold multiple roles or contexts:

• coach workspace owner or coach user;
• coached client in a coach-client relationship;
• personal workspace owner for self-organization and self-coaching;
• both coach and client, with access separated by workspace and relationship context.

The data model should support personal workspaces before implementation hardens, even if personal/self-coaching UI is delivered after Public V1.

Required Public V1 Scope

Public V1 uses the Core Coaching + Nutrition Baseline scope. It includes the core paid coaching loop:

1. Coach registers, creates workspace, and configures baseline account/workspace settings.
2. Coach invites a client through a validated invitation flow.
3. Client registers after invite validation and completes or skips the onboarding questionnaire task.
4. Coach reviews profile, questionnaire, goals, status, private notes, and readiness.
5. Coach creates and assigns forms, programs, and nutrition guidance, with coach web as the primary builder surface.
6. Client uses mobile Today view to complete workouts, meals, check-ins, quick logs, reminders, and progress tasks.
7. Client can log workouts offline and sync safely when connection returns.
8. Coach reviews adherence, workout performance, progress photos, measurements, deterministic risk signals, task inbox items, and messages.
9. Coach and client communicate through in-app messaging, attachments, short capped voice notes, and push notifications.
10. Product supports Arabic and English, RTL, dark mode, accessibility, secure media handling, and privacy/retention rules.

The feature database remains the detailed list of Public V1 feature records. This contract controls terminology and launch interpretation.

V1 Candidates / Needs Decision

No open V1 Candidate items remain from this scope pass. New candidate items must be added deliberately and resolved before Public V1 launch.

Post-V1 Scope

Post-V1 items should not block public launch unless this contract is updated:

• Payments, subscriptions, packages, invoicing, receipts, revenue reporting, and multi-currency accounting.
• Full coach mobile builder parity for program, questionnaire, nutrition, and template creation.
• Full Priority view as a separate ranked-client product surface. Public V1 may use task inbox sorting and deterministic risk signals instead.
• System-defined segmentation filters beyond basic client list filters.
• Program adaptation suggestions, AI coaching suggestions, and predictive trend intelligence.
• Water intake tracking unless later added as a simple nutrition baseline metric.
• Gamification, points, badges, levels, leaderboards, challenges, privacy controls for competitions, and custom challenges.
• Coach business dashboard, program effectiveness analytics, volume/intensity analytics beyond basic workout history, and affiliate/referral mechanics.
• Redemption store and reward fulfillment.
• Wearables and companion watch apps.
• Email, calendar, Zoom/video conferencing, and cloud storage integrations.
• Third-party comprehensive food database integration, barcode scanning, and provider food search. Public V1 uses coach-authored/workspace foods and immutable snapshots.
• Assistant coaches, staff assignment, multi-coach team queues, and advanced workspace collaboration.

Internal Milestone Model

Internal milestones are private delivery checkpoints, not public releases.

1. Foundation: monorepo, auth, roles, workspace model, database, object storage, queues, contracts, localization/RTL, CI, environments, and deployment baseline.
2. Onboarding: coach registration, workspace setup, invitation validation, client registration, onboarding questionnaire, profile readiness, and consent/legal copy.
3. Coach Setup: client management, forms, program builder, exercise provider integration, nutrition templates, and assignment flows on coach web first.
4. Client Execution: Today view, quick logs, workout logging, offline sync, nutrition execution, check-ins, progress capture, and push reminders.
5. Coach Review: task inbox, risk flags, progress review, adherence summaries, messaging, attachments, voice notes if included, and coach mobile review flows.
6. Coach Mobile Polish And Launch Hardening: coach mobile lightweight actions, accessibility, dark mode, Arabic/RTL QA, app-store smoke testing, observability, support runbooks, and launch hardening.

A feature can be built and tested internally as soon as its contracts are ready. It does not imply public release.

Documentation Completion Gate

Before broad implementation starts, the docs should include:

• Public V1 scope contract approved.
• Workflow State Map approved.
• Roles and Permissions matrix approved, including personal workspace and self-coaching contexts.
• REST API Contract Standard approved.
• Event and Outbox Standard approved for backend/server events and transactional outbox behavior.
• Offline Sync Protocol approved for mobile local outbox, operation receipts, replay, conflicts, and pruning.
• Privacy And Retention approved for data lifecycle, privacy, consent, retention, export, delete, anonymization, media purge, mobile cache purge, and legal-review gates.
• Provider Decision Register approved for external providers, self-hosted application integrations, auth, exercise, food deferral, push, media, messaging, credentials boundaries, terms and limits, fallbacks, launch evidence, and future integrations.
• Environment Runbook approved for platform setup, secrets, deployment gates, backups, restore, and rollback.
• Toolchain Contract approved for scripts, migrations, codegen, lint, typecheck, tests, builds, mobile build tooling, dependency updates, release notes, and CI command shape.
• Observability Plan approved for Public V1 logging, metrics, error and crash reporting, synthetics, dashboards, alerts, safe client diagnostics, and diagnostic playbooks.
• Test And Release Gate approved for pull-request, staging, production, security, accessibility, RTL, dark mode, offline sync, mobile E2E, performance, OTA, native-binary, release-evidence, and app-store smoke gates.

Public Launch Gate

Public V1 is ready for launch only when:

• all required Public V1 feature groups are implemented or explicitly moved to Post-V1 in this contract;
• all V1 Candidate items are decided;
• no critical privacy, security, sync, media, or permission risks remain open;
• coach web, coach mobile, and client/personal mobile pass the Public V1 test gate;
• Arabic/English, RTL, accessibility, dark mode, notifications, and offline flows are verified on target devices;
• support, backup, restore, incident, and provider-outage runbooks are ready.