A fat loss protocol is a stack architecture template for testing a body-composition goal across a defined block with a fixed roster, fixed dose windows, and prewritten stop rules. It does not treat a supplement as the main driver of weight change; it makes the supplement layer stable enough that food, training, sleep, and adherence are not constantly being confused with stack changes.
Why this needs a protocol
Body-composition logs are easy to misread because daily weight, appetite, training fatigue, and water shifts move faster than the stack can be evaluated. A protocol forces the user to name the stack goal, choose one primary proxy, and hold the stack steady long enough for the review to read a trend rather than a single week.
The architecture also keeps the stack from expanding whenever weight stalls. A cleaner move is to review the current block, check adherence, and decide whether the optional tier earned another cycle.
Stack shape
The protocol uses the same core and optional tiers described in supplement stack. Core items are stable, low-maintenance choices already tolerated by the user. Optional items are short tests with a named proxy, a review date, and a removal rule.
Dose windows are chosen for interpretability. Morning items, pre-training items, and evening recovery items should not be moved around casually, because schedule drift makes the review harder to read. The timing link matters as much as the ingredient list.
Proxy pair
The primary proxy is usually a rolling bodyweight trend, waist measurement, or another body-composition marker the user can collect consistently. A secondary objective proxy protects against a narrow read, such as weight moving down while training output, sleep, or resting heart rate moves in the wrong direction.
The protocol treats disagreement between proxies as a reason to pause interpretation, not as proof that the stack worked or failed.
Stop rules
Every optional item enters with a written stop rule. The rule should name the warning signal, the review window, and the action. Examples include persistent GI disturbance, repeated sleep disruption, or adherence falling far enough that the block is no longer readable.
The safety framing should stay conservative. The relevant pillar guidance is supplement stack mistakes to avoid, especially the parts on overlap, interaction checks, and stop conditions.
How this appears in Unfair
In Unfair, a fat loss protocol would prefill the builder with a body-composition goal, a small roster, a baseline checklist, and review prompts tied to the proxy pair. The review asks whether the block was readable before it asks whether any optional item should continue.
Clinical safety note
A fat loss protocol is a tracking and stack-architecture tool, not a weight-management treatment. Pregnancy, eating-disorder history, prescription weight-management therapy, cardiovascular symptoms, or unexplained weight change should move the decision out of self-experimentation and into clinician review.