The product

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.

---