Full specification

FitPact is a socially supported fitness and nutrition planning product for people who repeatedly fall out of habits despite wanting to continue them.

It helps users:

• Choose a fitness or nutrition goal.
• Assemble a practical weekly workout plan from curated exercises and workout templates.
• Assemble a macro-based nutrition framework from curated meal templates and USDA-backed food data.
• Log complete and partial adherence without shame.
• Make a time-bound pact with a trusted Pactmate.
• Receive Boosts and structured weekly Pact Pulses.
• Review and, when necessary, replace an unrealistic plan.

FitPact does not present AI as a coach, trainer, dietitian, or medical professional. AI assists with selecting, explaining, and adapting curated content. The user controls whether to exercise, eat, pause a plan, or end a pact.

Core positioning

Build your plan. Keep your pact.

Product model

FitPact connects:

1. The user, who owns their health decisions and follows a weekly plan.
2. Curated content and AI-assisted planning, which quickly assemble relevant plans without relying on unconstrained generation.
3. A Pactmate, who shows up beside the user through visibility, structured interactions, and plan-change co-signing while a pact is active.

FitPact copy universe

• Pactmate: The trusted person in a pact. It replaces “supporter” and “accountability partner.”
• Pact: A shared, fixed-term commitment between two adults.
• Pact Lane: One member’s personal commitment inside the pact. A lane contains workouts, nutrition, or both.
• Pact Pulse: The structured weekly check-in.
• Boost: A predefined encouragement or reaction.
• Reset: A proposed change to an active weekly plan.
• Co-sign: A Pactmate’s approval of a Reset.
• Finish: The successful arrival at the fixed pact end date, regardless of perfect adherence.

Preferred product language includes “Make a pact,” “Pick your lane,” “Meet your Pactmate,” “Send a Boost,” “Time for your Pact Pulse,” “Ask for a Reset,” and “Finish together.” Avoid supervisory phrases such as “hold them accountable,” “monitor progress,” “enforce the plan,” or “your partner is watching.”

---

The initial FitPact audience is inconsistent exercisers of any experience level. They may know what they want to achieve and may already understand training or nutrition, but they repeatedly fall out of exercise and diet habits because those habits are not socially supported.

Existing products often:

• Provide generic or authoritative plans.
• Treat planning as the main problem rather than sustained participation.
• Separate exercise and nutrition.
• Depend almost entirely on self-motivation.
• Use punitive streaks, surveillance, or shame.
• Fail to give a trusted person a clear, constructive role.

FitPact’s primary job is to make weekly fitness and nutrition commitments visible, socially supported, and easier to resume after partial adherence or missed commitments.

---

FitPact should become a shared fitness-planning workspace in which users make realistic weekly commitments and Pactmates help them keep those commitments without becoming coaches or authorities.

The experience should feel:

• Supportive
• User-directed
• Practical
• Flexible
• Nonjudgmental
• Fast
• Transparent about AI limitations

3.1 User bodily autonomy

The user can always pause a plan, stop an activity, revoke access, or end a pact. No Pactmate co-sign is required for these safety and autonomy actions.

3.2 Social commitment

When an active pact exists, activating a replacement plan is called a Reset and requires the Pactmate to co-sign it. Co-signing creates a deliberate shared recommitment; it does not force continued exercise or dietary behavior.

3.3 Curated before generated

Exercises, workout templates, meal templates, and recipes come from reviewed catalogs. AI selects, combines, explains, and proposes adaptations to this content rather than inventing unconstrained workouts or recipes.

3.4 Editable and explainable

Plans are editable before activation. Significant suggestions include concise reasoning and assumptions.

3.5 Realistic over optimal

Adherence, schedule, preferences, access, and sustainability take priority over theoretical optimization.

3.6 Partial effort counts

Workout and nutrition adherence are measured separately. Partial completion receives visible credit and is not converted into failure.

3.7 Support without surveillance

Pactmates receive the agreed plan and adherence visibility but cannot edit logs, prescribe behavior, or freely message through FitPact.

3.8 Safety before intensity

FitPact blocks plan assembly when reported information indicates a potentially life-threatening condition or a situation that requires individualized medical advice.

---

1. Let an adult create an account and safety profile.
2. Let a user choose a predefined goal or write a custom goal.
3. Assemble an editable one-week workout plan from curated content.
4. Assemble an editable macro-based nutrition framework with meal templates and a grocery list.
5. Let a user plan up to four weeks ahead.
6. Let workout and nutrition plans be used independently or together.
7. Support fast, simple logging with optional detailed workout data.
8. Calculate workout and nutrition adherence separately, including partial credit.
9. Let two adults make a pact lasting exactly 1 week, 1 month, 2 months, or 3 months.
10. Let each pact member choose a personal Pact Lane containing workouts, nutrition, or both.
11. Support one-way and mutual pacts: one member may have a lane, or both members may have separate lanes and back each other.
12. Let the Pactmate optionally maintain their own fitness journey from the same account.
13. Provide structured support interactions without duplicating general-purpose messaging apps.
14. Conduct a weekly Pact Pulse and propose Resets without silently altering an active plan.
15. Require a Pactmate co-sign before a Reset is activated during an active pact.
16. Send consented reminders by SMS.

Business goals

• Validate recurring weekly usage across four consecutive weeks.
• Determine whether an active Pactmate relationship improves consistency.
• Learn whether users use both workout and nutrition planning or favor one.
• Learn how frequently partial adherence leads to continued use instead of abandonment.

---

The MVP will not:

• Serve users under 18.
• Diagnose or treat medical conditions.
• Create plans for conditions requiring individualized medical guidance.
• Replace a personal trainer or registered dietitian.
• Guarantee fitness, body-composition, or health outcomes.
• Provide live coaching or exercise-form correction.
• Generate unconstrained exercises, workouts, recipes, or clinical meal plans.
• Recommend medication or supplements by default.
• Support public feeds, communities, or Pactmate groups.
• Support more than one active Pactmate relationship per user.
• Support custom pact lengths, open-ended pacts, or pacts shorter than one week or longer than three months.
• Provide unstructured in-app direct messaging.
• Provide native mobile applications or wearable integrations.
• Require detailed calorie or food logging.
• Charge users during the MVP validation phase.

---

6.1 Primary user

An adult at any fitness experience level who wants to exercise or eat consistently but has repeatedly fallen out of the habit.

The user may:

• Create workout and nutrition plans independently or together.
• Track their own adherence and progress.
• Invite a Pactmate and choose one of the four fixed pact terms.
• Choose workouts, nutrition, or both for their Pact Lane.
• Join a mutual pact in which both Pactmates have separate lanes.
• Also support a different user from the same account.

6.2 Pactmate

A trusted adult selected by the user, such as a friend, partner, family member, gym partner, or colleague.

The Pactmate:

• Creates a FitPact account and accepts the pact invitation.
• May use that same account for their own fitness journey.
• Sees the shared plan and adherence information defined in this PRD.
• Participates through structured prompts, acknowledgements, and reactions.
• May create a separate workout, nutrition, or combined Pact Lane in the same pact.
• Reviews and co-signs or declines a proposed Reset.
• Cannot edit the user’s plans or logs.
• Is not responsible for professional fitness, nutrition, or medical guidance.

---

7.1 Eligibility

• MVP users must be at least 18 years old.
• Registration includes an explicit age confirmation.
• Users who do not confirm they are 18 or older cannot continue.

7.2 Required safety information

Before any plan can be assembled, the user must answer questions about:

• Allergens
• Existing health issues
• Physical limitations

Users must provide an explicit “none known” response rather than silently skipping these questions.

7.3 Additional planning information

Users can provide:

• Primary goal
• Current activity level
• Training experience
• Workout preferences
• Available equipment
• Available days per week
• Typical session duration
• Exercise exclusions
• Height, weight, age, and sex where voluntarily provided
• Dietary preferences and exclusions
• Typical eating schedule
• Cooking preferences
• Budget and food-access considerations

Non-safety fields may be skipped when the product can still assemble a reasonable plan.

7.4 Safety decision

FitPact classifies the safety intake as:

• Eligible: Plan assembly can proceed.
• Needs caution: Plan assembly can proceed with bounded suggestions and a visible recommendation to seek qualified guidance.
• Blocked: FitPact does not assemble a workout or nutrition plan because the disclosed condition may be life-threatening or require individualized medical advice.

Blocked users receive a neutral explanation and are encouraged to consult an appropriate licensed professional. The product must not attempt to interpret, diagnose, or work around the condition.

---

8.1 Goal creation

The MVP offers a fixed list:

• Build muscle
• Lose body fat
• Improve general fitness
• Increase strength
• Improve endurance
• Build consistency
• Maintain current fitness
• Custom goal

Selecting Custom goal opens a free-text field. A user has one primary active goal and may optionally add a target date, target measure, and motivation statement.

8.2 Fixed pact terms

Every pact is time-bound. At creation, the members choose exactly one of these terms:

• 1 week: 7 consecutive calendar days.
• 1 month: From the start date through the day before the same date in the next calendar month.
• 2 months: From the start date through the day before the same date two calendar months later.
• 3 months: From the start date through the day before the same date three calendar months later.

No custom, shorter, longer, or open-ended term is available. The selected term cannot be extended in place. At the end date, the pact is marked Finished and the members may intentionally make a new pact using one of the four allowed terms.

8.3 Pact Lane scope

Each participating member chooses one lane scope independently:

• Workouts only
• Nutrition only
• Workouts and nutrition

A pact can be:

• One-way: One member has a Pact Lane and the other participates only as their Pactmate.
• Mutual: Both members have separate Pact Lanes and back each other inside the same fixed-term pact.

In a mutual pact, the two lanes may have different scopes, goals, weekly plans, adherence, privacy choices, and Reset requests. Neither member edits the other member’s lane.

8.4 Weekly plan cadence

• Active plans are organized into one-week cycles inside the selected pact term.
• The current week is active and directly loggable.
• A user may preview and prepare weekly plans up to four weeks in advance, even when the pact lasts two or three months.
• Future weeks remain planned drafts until activated.
• Each weekly boundary triggers a Pact Pulse before the next week is confirmed.
• The final weekly cycle may be shorter than seven days when necessary to end exactly on the pact end date.

---

9.1 Curated exercise catalog

Each exercise record should include:

• Stable ID and display name
• Movement pattern and primary muscles
• Required equipment
• Experience or complexity level
• Instructions and reviewed safety cues
• Contraindication or exclusion tags
• Substitution relationships
• Media reference, if available
• Review status and content version

9.2 Curated workout templates

Templates define reviewed structures by goal, experience, schedule, equipment, and duration. AI may select and parameterize a compatible template but may not introduce an exercise outside the reviewed catalog.

9.3 Food data

Food nutrient values use USDA FoodData Central data where available. The system stores source identifiers and data versions so calculations are reproducible.

9.4 Curated meal templates and recipes

Meal templates and recipes are pre-authored and pre-rendered for speed, consistency, and accuracy. Each includes:

• Stable ID
• Ingredients linked to food records
• Quantities and servings
• Estimated macro values
• Allergen and dietary-preference tags
• Preparation time and method
• Substitution options
• Grocery categories
• Review status and version

9.5 Role of AI

AI may:

• Interpret user preferences and constraints.
• Rank compatible templates.
• Explain why templates were selected.
• Propose reviewed substitutions.
• Summarize weekly adherence and user feedback.
• Propose a Reset for review.

AI may not:

• Override safety rules.
• Invent a new exercise or recipe for an active plan.
• Silently modify an active plan.
• Present estimates as medical prescriptions.
• Approve a plan on behalf of a user or Pactmate.

Deterministic services, not the language model, calculate macro totals, grocery quantities, adherence, dates, and permission checks.

---

Generated weekly plan components

• Workout days and scheduled dates
• Curated workout template
• Exercise list
• Sets, repetitions, duration, and rest periods
• Intensity guidance
• Warm-up and cooldown
• Progression guidance
• Reviewed substitutions

User actions before activation

• Add or remove a catalog exercise.
• Replace an exercise with a compatible catalog substitution.
• Change sets, repetitions, or duration within safety bounds.
• Move a workout.
• Choose a different compatible template.
• Save a draft.
• Submit or activate the plan according to pact status.

---

Macro targets are an essential MVP feature. FitPact presents them as estimates rather than clinical requirements.

Nutrition framework components

• Daily calorie estimate when enough information is available
• Protein, carbohydrate, and fat targets
• Meal frequency and optional timing guidance
• Curated meal templates and recipes
• Portion and serving guidance
• Reviewed food substitutions
• Consolidated grocery list

Requirements

• Respect all declared allergens and dietary exclusions.
• Never include a known allergen in a plan or substitution.
• Show the basis and assumptions for macro estimates.
• Allow the user to edit targets before activation.
• Recalculate macro and grocery totals deterministically after edits.
• Support lower-cost and faster-preparation filters.
• Avoid extreme calorie restriction and default supplement recommendations.

The MVP does not require users to log every food or calorie consumed.

---

Statuses

• Draft
• Awaiting Pactmate co-sign
• Active
• Paused
• Completed
• Declined
• Archived

Activation rules

• A user explicitly activates every first plan.
• Workout and nutrition plans may be activated independently.
• Only one workout plan and one nutrition plan may be active at a time.
• If no active pact exists, the user may activate a compatible plan directly.
• If an active pact exists, a replacement for an active plan is a Reset and enters Awaiting Pactmate co-sign.
• The Pactmate may co-sign or decline the Reset through a structured interaction.
• A co-sign activates the new version at its scheduled boundary and archives the prior version.
• A decline preserves the current plan and asks the Pactmate to choose a structured reason.

Autonomy and safety exception

Pactmate co-signing is never required to:

• Pause an active plan.
• Skip or modify an activity.
• Stop following a meal framework.
• Revoke sharing access.
• End the pact.
• Respond to a new health or safety concern.

If a plan is paused or stopped, FitPact must not imply that the Pactmate can compel continuation.

Version history

• Editing an active plan creates a draft version.
• The user and Pactmate can compare the proposed version with the active one.
• Prior versions remain in history.
• Reverting to a prior version follows the same Reset and Pactmate co-sign rules.

---

13.1 Simple workout logging

Every scheduled workout can be marked:

• Completed
• Modified
• Partially completed
• Skipped

13.2 Optional detailed workout logging

Users may additionally record:

• Sets
• Repetitions
• Weight
• Duration
• Perceived difficulty
• Notes

Detailed logging is never required to receive completion credit.

13.3 Nutrition logging

Users can record:

• Meal template followed
• Meal template partially followed
• Meal template not followed
• Protein target met or partially met
• Carbohydrate and fat target status
• Optional notes

13.4 Adherence model

• Workout adherence and nutrition adherence are separate scores.
• Completed commitments receive full credit.
• Modified and partially completed commitments receive partial credit.
• Skipped or unlogged commitments do not receive completion credit but do not incur punitive points.
• The UI shows the components contributing to each score.
• A combined score must not obscure separate workout and nutrition results.
• The exact point weights are a product-calibration decision and must be configurable without a client release.
• Missing data is distinct from a zero-value measurement.

The product uses neutral language such as “partially completed,” “not logged,” and “ready to revisit.”

---

FitPact does not automatically prompt a plan switch immediately after a missed commitment.

At the weekly Pact Pulse, the product:

1. Shows workout and nutrition adherence separately.
2. Highlights full and partial participation.
3. Asks what helped and what got in the way.
4. Offers to keep the current plan or prepare a Reset.
5. Summarizes proposed changes and assumptions.
6. Sends the Reset for the Pactmate to co-sign when an active pact exists.

The user may request a Reset at any time rather than waiting for the weekly Pact Pulse. No active plan changes silently.

---

15.1 Make a Pact flow

1. The initiating user invites one Pactmate by email or verified phone number.
2. The initiator selects a fixed term: 1 week, 1 month, 2 months, or 3 months.
3. The initiator picks their Pact Lane: workouts, nutrition, or both.
4. The invitee creates or signs into a FitPact account.
5. The invitee accepts or declines the pact.
6. When accepting, the invitee chooses either Back my Pactmate or Make it mutual.
7. If mutual, the invitee creates a separate Pact Lane containing workouts, nutrition, or both.
8. Both members review the term, lane scopes, default visibility, and Pact Pulse cadence.
9. Both members confirm, and the fixed-term pact becomes active on its start date.

An invitation expires after a configurable period. One account may own a Pact Lane and act as Pactmate for the other member inside the same pact.

15.2 Pact lifecycle

Pact statuses are:

• Invited
• Ready to start
• Active
• Paused
• Ended early
• Finished

The pact stores an immutable term selection plus deterministic start and end dates. It cannot remain active outside that interval. Members may pause or end it early, but they cannot extend it. At Finish, FitPact celebrates participation without requiring perfect adherence and offers a deliberate Make another pact action.

15.3 Separate Pact Lanes

• Each lane belongs to exactly one member.
• Each lane independently contains workouts, nutrition, or both.
• Each member logs, edits, pauses, and requests Resets only for their own lane.
• Each Pactmate views the other lane through that lane owner’s permissions.
• A mutual pact does not combine adherence scores or goals.
• A member may pause their own lane without automatically pausing the other member’s lane.
• Either member may leave or end the shared pact; the other member’s personal plans remain available outside the ended pact.

15.4 Default Pactmate visibility

After the user reviews and confirms the sharing summary, the Pactmate can see by default:

• Primary goal
• Active workout plan
• Active nutrition framework and macro targets
• Upcoming workouts and meal commitments
• Daily completion states
• Workout adherence
• Nutrition adherence
• Partial and missed commitments
• Pact Pulse summaries
• Upcoming Pact Pulses
• Proposed Resets

The following remain private unless separately and explicitly shared:

• Health issues and safety-intake answers
• Allergens and physical limitations beyond what is visible in the plan
• Body weight and body measurements
• Progress photos
• Private notes
• Account and contact information not required for the pact

The user sees a plain-language preview of default sharing before activating the pact and may revoke sharing or end the pact at any time.

15.5 Structured interactions

FitPact does not provide free-form direct messaging in the MVP. Pactmates can:

• Send a predefined Boost.
• React to a completed or partially completed commitment.
• Answer a structured weekly Pact Pulse.
• Ask a predefined support question.
• Co-sign or decline a proposed Reset.
• Select a structured reason when declining.

Suggested language must be supportive and must not shame, threaten, diagnose, or imply surveillance.

---

MVP reminders are delivered by SMS.

User reminders

• Upcoming planned activity
• Pact Pulse ready
• Pactmate interaction
• Reset co-signed or declined
• Pact invitation status

Pactmate reminders

• New pact invitation
• Scheduled Pact Pulse
• User response
• Reset awaiting co-sign
• Pact paused or ended

Requirements

• A verified mobile number and explicit SMS consent are required before SMS is enabled.
• SMS consent is recorded separately for each account.
• Users can disable nonessential reminders and withdraw SMS consent.
• Quiet hours use the recipient’s timezone and default to 21:00–08:00.
• Sensitive health information, weight, macro values, and adherence details do not appear in SMS text.
• SMS links require authentication before showing private information.
• Reminder frequency is configurable and rate-limited.
• The product supports legally required opt-out handling.

Structured Pactmate actions occur inside FitPact; SMS serves as the notification and return channel, not as unrestricted Pactmate-to-user messaging.

---

User navigation

• Today
• Plan
• Progress
• Pact
• Profile

Today dashboard

The dashboard answers:

• What did I commit to today?
• What have I fully or partially completed?
• Is a Pact Pulse, Boost, or Reset action waiting?

It contains:

• Today’s workout
• Today’s meal framework and macro targets
• Fast logging controls
• Separate weekly workout and nutrition adherence
• Structured Pactmate interactions
• A request-plan-change action

Pactmate navigation

• Overview
• Pact Pulses
• Resets
• Settings

The Pactmate overview prioritizes encouragement and context rather than surveillance or rankings.

---

Permissions are evaluated relative to each Pact Lane. In a mutual pact, each person is the owner of their own lane and the Pactmate for the other lane.

Role checks are relationship-scoped: being a Pactmate for one person grants no access to any other user.

---

Account and safety

• FR-001: An adult visitor can create and verify an account.
• FR-002: A user can log in, log out, reset credentials, export data, and delete the account.
• FR-003: A user must confirm they are at least 18.
• FR-004: A user must answer required allergen, health-issue, and physical-limitation questions before planning.
• FR-005: The system blocks plan assembly when safety rules require individualized medical guidance.

Goals and planning

• FR-010: A user can select a predefined goal or enter a custom goal.
• FR-011: A user can assemble a one-week workout-plan draft from curated content.
• FR-012: A user can assemble a macro-based nutrition draft from curated meal templates and USDA-backed food data.
• FR-013: A user can edit drafts within content and safety constraints.
• FR-014: A user can activate workout and nutrition plans independently.
• FR-015: A user can plan up to four weeks ahead.
• FR-016: A user can view and compare plan versions.
• FR-017: Deterministic calculations update macros, grocery quantities, and adherence.

Logging and review

• FR-020: A user can log a workout as completed, modified, partially completed, or skipped.
• FR-021: A user can optionally record detailed workout performance.
• FR-022: A user can log meal-template and macro adherence.
• FR-023: The system displays workout and nutrition adherence separately.
• FR-024: Partial adherence receives partial credit.
• FR-025: A user receives a Pact Pulse after each active week.
• FR-026: A lane owner can request a Reset at any time.

Pact and Pactmate

• FR-030: A user can invite one Pactmate.
• FR-031: Pact creation offers only 1-week, 1-month, 2-month, and 3-month terms.
• FR-032: The system deterministically computes and enforces the pact start and end dates.
• FR-033: Each member can choose workouts, nutrition, or both for their own Pact Lane.
• FR-034: The invitee can join without a lane or make the pact mutual by creating a separate lane.
• FR-035: A member reviews the term, lane scopes, and sharing summary before activating a pact.
• FR-036: A Pactmate can see the other lane’s default shared plan and adherence information.
• FR-037: Pactmates can send only structured interactions, including Boosts and Pact Pulses.
• FR-038: A Pactmate can co-sign or decline a Reset for the other member’s lane.
• FR-039: Either member may pause their lane or end the pact without a co-sign.

Notifications

• FR-040: An eligible account can opt into SMS reminders using a verified number.
• FR-041: A recipient can configure reminders, quiet hours, and opt-out preferences.
• FR-042: SMS content does not reveal sensitive health or adherence information.

---

Performance

• Main authenticated pages should target an LCP of 2.5 seconds or less at the 75th percentile on supported mobile devices.
• Template-based plan assembly should feel immediate where possible and always show progress when processing is required.
• Partial failures must preserve user-entered information.

Responsive design

• Mobile web is a primary use case.
• Core flows work on current major desktop, tablet, and mobile browsers.

Accessibility

• Target WCAG 2.2 AA.
• Support keyboard navigation and assistive technologies.
• Do not rely on color alone to communicate completion or adherence.
• Use neutral, descriptive status language.

Security and privacy

• Encrypt data in transit and at rest where appropriate.
• Apply relationship-scoped role-based access controls.
• Log sharing, pact, co-sign, and permission changes.
• Prevent Pactmates from accessing unshared health and profile data.
• Make progress photos and private notes private by default.
• Support data export and account deletion.
• Do not use sensitive details in SMS messages.

Reliability and auditability

• Store content, USDA source, calculation, safety-rule, and plan versions.
• Store user and Pactmate co-sign events.
• Maintain logs of AI-assisted selections and proposed changes for safety review.
• A catalog update must not silently alter an already active plan.

---

Account

• Account ID
• Email
• Verified mobile number
• Display name
• Adult confirmation
• Authentication state
• SMS consent and preferences
• Timezone and quiet hours
• Account status
• Created date

Fitness profile

• Account ID
• Goal and custom-goal text
• Experience and activity level
• Availability and equipment
• Workout preferences and exclusions
• Dietary preferences and exclusions
• Required safety answers
• Optional body metrics

Catalog content

• Content ID and type
• Structured content
• Compatibility and exclusion tags
• Source or author
• Review status
• Content version

Plan

• Plan ID
• User ID
• Plan type
• Weekly start and end dates
• Source template and content versions
• Plan version and status
• AI selection summary and assumptions
• User edits
• Created, submitted, co-signed, and activated dates

Scheduled commitment

• Commitment ID
• Plan ID
• Scheduled date
• Exercise, workout, meal, or macro target reference
• Completion state
• Optional detailed log
• Notes and sharing status

Adherence summary

• User ID and week
• Workout adherence components and score
• Nutrition adherence components and score
• Scoring-rule version
• Computed date

Pact

• Pact ID
• Initiating member ID
• Invited member ID
• Term enum: one_week, one_month, two_months, or three_months
• Start date and deterministic end date
• Status
• Pact Pulse cadence
• Created, accepted, started, paused, ended, and finished dates

Pact Lane

• Lane ID
• Pact ID
• Owner account ID
• Scope enum: workout, nutrition, or both
• Goal ID
• Active workout plan ID, when included
• Active nutrition plan ID, when included
• Sharing confirmation and permissions
• Lane status

Structured interaction

• Interaction ID
• Pact ID
• Interaction type
• Sender and recipient
• Template or reaction ID
• Related commitment or plan ID
• Response
• Created date

Reset co-sign

• Co-sign ID
• Pact ID
• Pact Lane ID
• Proposed plan ID
• Pactmate decision
• Structured reason
• Decision date

---

Primary MVP validation metric

Four-week recurring weekly usage: the percentage of activated users who complete at least one meaningful FitPact action in each of four consecutive weeks.

Meaningful actions include:

• Logging workout or nutrition adherence
• Completing a Pact Pulse
• Confirming or requesting a weekly plan
• Responding to a structured pact interaction
• Co-signing or declining a Reset as a Pactmate

The target percentage is TBD before launch. The metric must be segmented by users with and without an active Pactmate.

Supporting metrics

• Weekly active users
• Four-week recurring weekly users
• Plan activation rate
• Workout and nutrition plan adoption, separately
• Partial-adherence rate
• Weekly-review completion rate
• Pactmate invitation and acceptance rates
• Percentage of users with an active pact
• Pact term selection and Finish rate by term
• One-way versus mutual pact adoption and recurrence
• Pact Pulse response rate
• Reset request and co-sign rates
• Four-week recurrence difference with versus without an active Pactmate

Safety and quality metrics

• Safety block and caution rates
• Reported inappropriate-output rate
• Allergen-conflict rate, with a required target of zero known conflicts
• Unsupported catalog-item rate, with a required target of zero active-plan items
• Plan abandonment and pact termination rates

---

The MVP is ready when:

• Adult eligibility and required safety intake work.
• Safety-blocking rules have been reviewed and tested.
• Users can independently assemble and activate workout and nutrition plans.
• Plans use only compatible, reviewed catalog content.
• Nutrition calculations use versioned USDA-backed food data where available.
• Macro targets and grocery lists recalculate correctly.
• Users can plan one active week and prepare up to four weeks.
• Users can select only 1-week, 1-month, 2-month, or 3-month pact terms.
• Pact start and end dates are deterministic and enforced.
• Pactmates can create one-way or mutual pacts with separate workout, nutrition, or combined Pact Lanes.
• Simple and optional detailed workout logging work on mobile web.
• Workout and nutrition adherence are calculated separately with partial credit.
• Users can invite one Pactmate and confirm default sharing.
• Pactmate access boundaries pass permission testing.
• Boosts, Pact Pulses, and Reset co-signing work.
• Users can pause plans and end pacts without a Pactmate co-sign.
• SMS consent, quiet hours, sensitive-content restrictions, and opt-out work.
• The four-week recurring weekly usage metric is instrumented.
• Account export and deletion work.

---

Pactmate co-signing feels controlling

Mitigation: Co-signing applies only to activating a Reset during an active pact. Users can always pause, stop, revoke sharing, or end the pact. Product language frames a co-sign as shared recommitment.

Longer pacts feel endless after motivation drops

Mitigation: Every pact has a visible end date, weekly Pact Pulses, and explicit pause and end controls. The product never auto-renews or extends a pact.

Mutual pacts blur ownership

Mitigation: Give each member a separate Pact Lane, plan history, adherence score, privacy controls, and Reset workflow. Never combine goals or allow cross-editing.

Default sharing feels intrusive

Mitigation: Show a clear preview and explicit confirmation before pact activation. Keep health intake, body metrics, photos, and notes private unless separately shared.

Curated content is insufficiently personalized

Mitigation: Build catalog depth around goals, schedules, equipment, dietary preferences, cost, and preparation time. Support reviewed substitutions and track searches with no compatible result.

USDA data creates inconsistent calculations

Mitigation: Use normalized serving units, source identifiers, data versions, deterministic calculations, and reviewed mappings between meal templates and food records.

SMS becomes costly or intrusive

Mitigation: Use event-based, rate-limited messages; quiet hours; minimal sensitive content; and explicit consent. Track cost per four-week recurring user.

Users treat macro targets as medical prescriptions

Mitigation: Label values as estimates, show assumptions, avoid clinical claims, and block cases requiring individualized medical advice.

Partial-credit points encourage gaming

Mitigation: Keep workout and nutrition scores transparent and separate, prioritize reflection over rewards, and avoid competitive leaderboards.

---

• Define reviewed safety conditions for Needs caution and Blocked with qualified clinical and legal input.
• Choose the specific age-confirmation and regional eligibility implementation.
• Define configurable point weights for full, modified, partial, skipped, and unlogged commitments.
• Define the four-week recurring weekly usage target.
• Select the initial countries and SMS provider.
• Decide whether Pactmates receive only weekly summaries or can also view adherence in real time; this draft assumes real-time visibility.
• Define what happens when a Pactmate does not respond to a Reset co-sign request before the next week starts.
• Define the initial catalog size and content-review workflow.
• Define USDA FoodData Central ingestion, licensing/attribution, update, and normalization processes.

---

FitPact’s MVP is a free, adult-only responsive web app where two people make a fixed 1-week, 1-month, 2-month, or 3-month pact, choose separate workout, nutrition, or combined Pact Lanes, and help each other keep showing up through Boosts, Pact Pulses, and co-signed Resets.