AIm Workout Journal

Create or update a training goal (pass `id` to update). `target.goal_type` selects the shape: milestone (point target — exercise_id+value, or bodyweight+baseline_value), weekly_volume (muscle+band: mev|mev_mav|mav — "train X at least at MEV every week"), trend (exercise_id+metric, no value — "just keep it climbing", no fixed finish line), maintenance (baseline_value+tolerance_pct, exercise_id and/or muscle optional, unset means total session volume — "don't lose ground"), or omit goal_type for a plain process goal (metric=sessions_per_week). Any exercise_id must be an id from the user's catalog (list_exercises; new ones via upsert_exercise): unknown ids are rejected, and a synonymous duplicate would split the exercise's history. `review_date` is the goal's scheduled check-in date. featured=true makes this the ONE goal on the app's featured-goal card and automatically un-features any other active goal. The server rejects featured on a frequency goal; those live in the adherence widget only. A sessions_per_week goal and the profile's training_days_per_week are one number: writing either sets both. Goal succession is two records: the earlier goal with status=achieved (never featured, which the server enforces) and the next goal with supersedes_goal_id=<earlier goal's id>. The user also sets and closes goals in the app (source=user); a goal they set is theirs, and nothing changes a goal automatically. Activity goals (activity_days_per_week) are set in the app only and read in get_coaching_context.activities. Coach-proposed goals carry ratified=false until the user agrees. Goals are not deleted: status=revised/abandoned/achieved supersedes them, so history survives.

upsert_goal

Create or update an exercise in the user's catalog (keyed by its id/name). An exercise from search_exercise_pool saved with its `slug` as the `id` plus `pool_slug` keeps one identity and one history, and inherits the pool's muscles, equipment and technique cues. A hand-written exercise shows in the muscle map and the app only when `instructions` (2-3 short technique cues, in the user's language), `primary_muscles`, `category` and `equipment` are set. Fields omitted are left as they are, so a partial update is safe.

upsert_exercise

Fix a key metric of a single set, located by session + exercise + set_number. Allowed patch keys: weight_kg, reps, rir, rpe, tempo, rest_sec, duration_sec, distance_m, is_per_side, completed, notes, type. `occurrence` (1-based) picks which instance when the exercise appears more than once in the session. Returns the updated set, or null if none.

update_set

Delete a session and all its entries/sets. Returns {deleted: bool}.

delete_session

Get one session with its full nested entries, sets, cardio and wearable metrics.

get_session

The user's own activities besides workouts (e.g. football, swimming, a drink) and the days they marked them, in a date range (default: the last 28 days). Each activity has `days` and, when the user set one, `goal` {direction at_least|at_most, days_per_week, days_this_week}. A day not listed is unknown, not a day without the activity. Counts are days, not times or amounts. Activities the user keeps private are not returned. The user creates activities and their goals in the AIm app.

get_activities

This user's training data for planning a workout (task next_workout), building a program (new_program), reviewing the week (weekly_review), checking for a deload (deload_check), a periodic check-in (checkin) or the intake (intake). Returns data only: - `task` and `requested_task`: while the intake is incomplete a planning request is answered with the intake's data, so `task` is 'intake' and `requested_task` keeps the task asked for. - `intake`: {complete, status, next_field, next_field_options, remaining}: the first profile topic with nothing stored yet in intake order, the values it accepts when it is enumerated, and how many topics are still empty. `complete` needs the six core topics (motivation, experience, days per week, locations, equipment, goal); sex, age and body weight are optional. While it is false no training data is attached and `intake_required` is true for a planning task. - `goal_candidates` (when the user has no active goal): unsaved goals computed from the profile and recent lifts in upsert_goal's shape, ratified=false, each with its `basis`; how many depends on what the profile holds. - `user_profile`, `goals` (the featured goal carries a computed `progress` block), `reply_language`. - `planning_parameters`: numeric ranges for the user's primary goal (weekly hard sets per muscle, reps per set, reps in reserve, rest, progression step); for a home or outdoor profile also `without_added_load` (the reps range and the order of progression levers when no weight can be added). - `first_session_load_estimates` (next_workout / new_program): first working weights for an exercise with no logged history, from sex and body weight, for a calibration start, only for the kit the user has (all kits when equipment is unknown), with `basis`. - `training_data`: sessions this week vs target, `consistency_level` (the 0-8 level the app shows as a flame, relative to the user's own rhythm), days since the last session, `recent_sessions` (logged_in_app=true means the app recorded it set by set and it is already stored), `recent_lifts` (last working sets per exercise: weight, reps, seconds or metres as logged), `active_program` (days and who last edited them), `exercise_catalog` (the user's exercise ids), `weekly_sets_by_muscle` (direct and assisted sets in the last 7 days against MEV/MAV landmarks; the landmarks are stated in direct sets; chest and traps are judged whole, their regions carry `part_of` and no band) and `residual_load_by_muscle` (`pct_of_hard_session`: how much of one hard session's work on that muscle has not yet faded, relative to this user's own hard sessions; `fades_in_h`: when it will have; a tally of work done, not a measure of recovery or readiness). - `activities` (when the user has any): {items, note}. Each item is one of the user's own activities (football, swimming, …) with `days` it was marked in the last 28 days and, when set, `goal` {direction at_least|at_most, days_per_week, days_this_week, set_by}. An unmarked day is unknown, not a day without it; counts are days, not times or amounts; activities are not workouts and are in none of the training_data numbers (residual load, weekly sets). Private activities are never included. - `todays_constraints`: the constraints argument, echoed. `task` defaults to 'next_workout'. 'check_in' is accepted as an alias of 'checkin'. `constraints` is for TODAY-ONLY circumstances ("only 30 minutes", "gym closed, training at home"); they are not saved to the profile, durable facts are stored with update_coach_profile. `today` is the current date in the user's timezone, YYYY-MM-DD (today's date, not the day being planned), as for a session's date: everything here is anchored on which day it is for them, and the server's clock is UTC. When it is omitted the server uses the timezone stored from the web app, or UTC when none is stored, which can shift the weekly and muscle numbers by a day.

get_coaching_context

The user's goals (status: active|achieved|abandoned|revised|all). Goals on the user's own activities are in get_coaching_context.activities and get_activities.

get_goals

Get the active training program with its day templates (planned blocks/supersets and per-exercise targets), or null if there is no active program. Program-planning data is in get_coaching_context(task='new_program'), draft validation in review_program_draft, and saving or replacing a program in import_document.

get_program

Statistics for ONE exercise, or for training as a whole. The user's goals, per-muscle weekly sets and recent working weights for a review of their training are in get_coaching_context (task='weekly_review'). The parameter is named `kind`, not stat_type/stat/type/metric. It defaults to 'volume', the only value that needs no exercise_id. exercise_id is REQUIRED for kind='progression' and kind='prs' (they are per-exercise) and is ignored for kind='volume' (whole-training-volume over time). Progression or prs without an exercise_id is an error, not a whole-library default; exercise ids come from list_exercises. 'progression' → per-date top set, est-1RM (Epley), volume + PRs; 'prs' → personal records; 'volume' → total training volume over time with trend %. One movement the user logged under several catalogue rows is read as one history; `same_movement_ids` then lists those rows. get_coaching_context bundles these numbers with the user's goal and context for planning.

get_stats