On-cycle is the active testing period where a stack is intentionally run and monitored for effect and tolerability.
Why it matters
It is where dosing logic and outcome logging produce most of the adaptation signal.
What happens during on-cycle
- daily timing and dose execution
- effect and adverse tracking
- weekly review checkpoints
Weekly review should include sleep, GI tolerance, and goal progress.
Restart and escalation rules
Escalate only when:
- adherence is stable
- side effects stay low
- benefit trend remains positive
If outcomes plateau or adverse signals rise, move to maintenance review or pause escalation.
End-of-cycle exit criteria
- no additional gains after predefined trial length
- repeated adverse signals despite dose adjustment
- clear safety trigger or conflict with medications
Use explicit exit rules before you run out of interpretability.
Practical action step
Before starting each on-cycle, set a hard review day and one criterion for stopping or adjusting.
Uncertainty and limits
- Evidence is limited on the exact duration where acute effects convert to stable long-term benefits.
- Evidence is limited on individual differences in adaptation speed across similar stacks.
Cross-site references
How this appears in Unfair
On-cycle states alter recommendation confidence by favoring current-cycle adherence and de-prioritizing outdated stack behavior.
Clinical safety note
If adverse symptoms increase with repeated use, exit the cycle and request clinician input before re-entry.