Glossary

Custom Stack Builder

Updated February 22, 2026

The custom stack builder is the manual logic layer where you assemble ingredients, timings, and constraints before recommendation logic optimizes around them.

Why it matters

It differs from recommendation logic: builder logic captures intent, while recommendation logic suggests adjustments.

Builder logic vs recommendation logic

• Builder logic: user-owned structure for goals, dose windows, exclusions, and personal constraints.
• Recommendation logic: system-generated suggestions based on current inputs, evidence signals, and observed outcomes.

Use this distinction before you override a stack: if builder logic is stale, recommendations can look disconnected from your actual routine.

Practical template flow

1. Choose a goal and a primary outcome.
2. Set constraints: time windows, exclusions, budget, and safety toggles.
3. Validate baseline safety checks.
4. Add cadence rules for loading, maintenance, or skip conditions.

Anti-overload safeguards

Practical defaults prevent overwhelm:

• cap ingredient count for dense stacks,
• set a default maximum on cycle duration before review,
• require explicit confirmation before adding duplicate intents.

This keeps safety checks readable and adherence realistic for real schedules.

Cross-site references

• Stack planning
• Stack favorites
• Maintenance phase

Uncertainty

• Evidence is limited on an “ideal” cap size for all goals and work/rest profiles.
• Evidence is limited for long cycles without periodic de-loads.

How this appears in Unfair

Unfair uses the builder structure to separate manually set boundaries from suggestion layers, so your explicit stack decisions remain auditable.

Clinical safety note

If complexity drives missed doses or unsafe additions, reduce ingredient count and re-run the cadence review.