Progression Without Guesswork: Why Fitflux Uses Rules Before AI

Progression is where a training plan meets reality. A program can look sensible on paper, but the next step still depends on what was prescribed, what the athlete completed, and what the coach wants to change.

That is why Fitflux separates two jobs that are often blurred together:

• AI-assisted tools can help draft or explain a plan.
• Progression rules and logged training signals shape the next prescription.

The distinction matters. Generative AI is useful when there are many reasonable ways to express or organize an idea. Training progression needs a more traceable path from inputs to proposed changes.

Three Parts of the Progression Workflow

Fitflux does not treat progression as one automatic decision. The workflow has three connected parts.

1. The Program Defines the Starting Rules

A coach builds the program structure: exercises, sets, reps, load targets, phases, and any progression or auto-regulation settings that should apply.

Those authored settings remain the baseline. Fitflux does not replace them with an opaque recommendation simply because new data arrives.

2. The Preview Shows What Comes Next

The progression preview compares the current program with the next week or session. It can surface projected changes in working load, set volume, exercise structure, and other signals that deserve attention.

The preview can also provide advisory guidance such as holding steady, reviewing fatigue, or checking the progression setup. That guidance is there to make the next decision easier to inspect. It is not a hidden rewrite of the program.

If the schedule is incomplete or recent training context is limited, the preview says so instead of presenting a confident-looking answer.

3. Logged RPE Can Create a Bounded Adjustment

When auto-regulation is enabled, a completed program workout can feed an RPE-based adjustment workflow.

Fitflux keeps the authored target RPE separate from the athlete's logged RPE. The backend can compare those values, apply the program's configured thresholds and caps, and create an adjustment for the appropriate upcoming week.

The important word is create. An adjustment record is a traceable proposal with a source workout, exercise, week, and program target. It is not a free-form instruction produced from a prompt.

What the System Actually Reads

The progression and auto-regulation paths work from specific product data:

• the assigned program and its phase structure;
• the current and upcoming session targets;
• the program's progression and auto-regulation settings;
• a completed workout log;
• the prescribed target RPE and the athlete's actual logged RPE;
• the exact exercise and week the adjustment belongs to.

Readiness is not currently an input to this adjustment calculation. Recovery and wellness information can still be useful coaching context, but it remains separate from the RPE progression contract.

Missing, malformed, or ineligible inputs fail closed. Fitflux should not invent an adjustment when it cannot connect the workout, program, week, and exercise honestly.

Review Is Part of the Product Contract

Some adjustments require trainer review. Those records remain pending and do not affect the progressed prescription until a trainer approves and commits them.

The trainer can inspect the source signal, review the proposed change, add context, approve it, or reject it. Approval is handled through a protected backend action that rechecks ownership and applies the change only to the recorded program target.

This is an important product boundary: the system can do the repetitive comparison work without pretending to own the coaching decision.

Adjustments that are eligible under the active configuration can flow into progressed sessions. Review-required changes cannot bypass their approval state.

What the Athlete Sees

Client and portal program views read the progressed session rather than a disconnected recommendation feed. When an eligible adjustment is applied, the upcoming prescription reflects it in the same place the athlete already trains.

That keeps the workflow connected:

1. the athlete completes the workout and logs effort;
2. Fitflux connects the signal to the correct program target;
3. the coach reviews changes that require a decision;
4. the approved or otherwise eligible adjustment appears in the progressed session.

The athlete gets a clear next session. The coach keeps the context behind it.

Where AI Helps—and Where It Stops

AI can be useful for drafting a program, organizing information, or helping turn context into an editable starting point. Those are open-ended tasks where a coach benefits from speed and flexibility.

Progression is different. A proposed load, rep, or set change should be connected to visible program rules and training data. Fitflux therefore keeps the progression path rule-based and reviewable instead of asking a generative model to make the final prescription.

That does not make the system infallible, and it does not guarantee an outcome. It makes the path easier to inspect:

• what changed;
• which signal contributed;
• where the change will apply;
• whether trainer review is required;
• who approved or rejected it.

The Bottom Line

Good coaching software should reduce repetitive work without erasing responsibility.

Fitflux uses program rules to build the baseline, training signals to surface possible changes, and explicit review states to keep important decisions visible. AI can assist around that workflow, but it does not become the coach.

Rules calculate. Signals inform. Coaches decide.