The workout is an execution layer
A workout session records what happened. It should not silently rewrite routine prescriptions or activated weekly plans.
Execution Layer
Workout execution: what you planned, what you did, and what carries forward.
The workout screen is where the plan meets real life. RAMM’s direction is to log the performed result clearly without letting a rushed set, one-time substitution, or fatigue adjustment silently corrupt future goals.
9:41
D1 Push · Set 2 of 3
Incline Dumbbell Bench Press
Today's goal
28 kg × 11
Last on this workout: 28 kg × 12
Weight
26
Reps
10
Set intention
Fatigue — apply to this set only
What gets saved
- Performed result: 26 kg × 10
- Original goal: 28 kg × 11
- Intent: fatigue
Context matters
Fatigue, equipment, pain, controlled tempo, and one-time substitutions are different signals. They should not collapse into the same future target.
Future goals need reviewable evidence
Goal generation can use performed work safely only when it understands the prescription, measurement type, and execution context.
Planned target versus performed result
A planned target is the goal RAMM asks you to attempt. A performed result is what you actually completed. They often match, but they do not have to. Real training includes short rests, missed reps, stronger-than-expected sets, equipment changes, and days where you deliberately train with lower volume.
The mistake is treating every performed result as the new truth. If a lifter performs less weight because of fatigue, the next goal should not automatically fall. If they exceed the target on one set, the next goal should not automatically jump beyond the routine’s intended range. Execution is evidence for a later decision.
Changing weight or reps mid-workout
Mid-workout changes are useful when they are intentional. Reducing load may keep the movement controlled. Adding reps may show a target was too conservative. Stopping early may protect quality. The app should make those changes easy without pretending they all mean the same thing.
That is where intent metadata matters. A set marked as fatigue is different from a set marked as controlled lower-volume work. A whole-exercise intent is different from a one-set note. Both should remain visible in the training history.
Set-level versus exercise-level intent
Sometimes only one set needs explanation: a slipped grip, a rushed rest, a technical reset. Other times the whole exercise changed: you chose a lighter load for form, managed fatigue, or used different equipment. RAMM should preserve that scope.
This matters later. A single fatigued set should not carry the same weight as a deliberate whole-exercise adjustment. Good execution data helps the deterministic engine decide when to progress, hold, or require review.
Switching exercises
Exercise substitutions are common, especially when equipment is busy or you train away from your usual gym. But substitutions are not always comparable. A behind-the-back cable curl is not automatically the same prescription as a preacher curl. A band overhead press is not the same progression path as a dumbbell press.
If a substitution is one-time, it belongs in execution history. If it is permanent, the routine prescription should be versioned so future goals reference the new movement directly.
What future goal generation can safely use
Original prescription
The exact sets, ranges, role, goal type, and progression profile for the routine slot.
Execution record
The completed set logs, substitutions, skipped work, and set or exercise intentions.
Quality gate
A deterministic check that decides whether the next goal can be generated or review is required.
Fatigue, pain, and controlled execution
Fatigue can explain a performance drop, but it does not diagnose the body. Pain-related adjustments deserve extra caution and should avoid confident claims. Controlled execution is also different from failure: lowering load to move better can be a deliberate training choice.
The safest content and product boundary is simple: record what happened, record the reason, and require review when the system cannot safely interpret the result.
What happens at workout completion
After a workout, RAMM can summarize the session: targets hit, missed sets, substitutions, and intentions. That summary becomes part of the evidence for future progression. It should not mutate the active weekly plan that already existed.
This keeps history explainable. If the next goal changes, the change should trace back to a progression decision rather than a hidden copy-forward rule.
Example scenarios
Fatigue
You reduce load on set three after short rest. The log stores fatigue context instead of automatically lowering next week.
Equipment swap
The cable station is busy, so you use dumbbells. The workout records a substitution and may require review.
Permanent change
You decide the substitute is now the routine movement. That should become a new routine prescription version.
Workout execution FAQs
Does using less weight lower next week’s goal?
Not automatically. A lower performed set should be stored with context. It may lead to a hold, review, or adjustment, but it should not silently overwrite the future prescription.
What happens when I switch an exercise?
A one-time substitution can be logged as execution. If the substitute is meant to become permanent, the routine prescription should be versioned rather than pretending the old exercise is the same movement.
Can I save a temporary change to my routine?
A temporary execution change and a permanent routine update are different decisions. RAMM’s architecture keeps those boundaries explicit.
How does RAMM treat pain or fatigue?
RAMM can record fatigue or pain as context and require review. It should not diagnose pain, claim recovery status with certainty, or automatically rewrite goals from one affected set.
What is controlled execution?
Controlled execution means the lifter intentionally reduces load, reps, speed, or volume to prioritize form or a specific training intent. It should be logged differently from an unplanned miss.
Execution is one part of the system
To see how execution becomes a reviewable progression decision, continue with Progressive Overload or the full How RAMM Works system overview.
Ready to train with a plan?
Join the early access list and be the first to experience RAMM.
No spam. Just early access updates.