How is Repast different from other keto meal planners?

Repast treats your carb cap as a strict mathematical constraint rather than a warning after the fact. Across 16,933 simulated days the carb overage is 0g. Furthermore, all data remains strictly on your iPhone with no account, server, or analytics.

What happens if my dietary constraints cannot be met?

Repast refuses rather than fudges. If your constraints cannot be satisfied (such as 15-minute meals, pescatarian, and no eggs), the app names the exact bottleneck rule and calculates how much loosening it unlocks instead of quietly breaking your rules.

Does Repast require an account or internet connection?

No. Repast operates entirely on your device. There is no account sign-up, no backend server, and no analytics tracking. Your weight, meals, and measurements stay on your iPhone.

How does the shopping list handle leftovers?

The shopping list counts whole cooks rather than individual sittings. Cooking a four-serving recipe eaten twice is counted as one cook session, cutting redundant grocery purchasing.

Constraint Engine·4 min read·September 2026

The Hard Carb Ceiling: Why Post-Hoc Food Logging Always Fails

The mathematical difference between warning you after the fact and generating under a hard limit.

Almost every health app on the App Store operates on a post-hoc logging model: you eat whatever you find, search for an approximation in an unverified crowd-sourced database, log it, and watch the app colour the number red when you breach your target at 10 PM. That is not planning; that is an autopsy.

1. Constraint vs. Report

In software engineering, a constraint is an invariant condition that the system refuses to violate. A report is an audit log of what already went wrong.

If you want to maintain nutritional ketosis, your daily carbohydrate limit is not an aspirational goal — it is a biochemical ceiling. Once liver glycogen replenishes beyond your threshold, ketosis halts regardless of your motivation.

Repast was engineered as a constraint solver. Across 16,933 simulated days in our verification test suite, the daily carbohydrate overage is exactly 0.0g. The algorithm will not emit a day that breaks your ceiling.

Across 16,933 simulated days in our verification test suite, the daily carb overage is exactly 0.0g.

2. The Decision Fatigue Spiral at 6:30 PM

Deciding what to cook three times a day under a strict 20g net carb ceiling imposes extreme cognitive load. By dinner time, willpower is depleted. You open the fridge, piece together what is available, and discover after logging that the sauce contained 14g of added starch.

When the entire 7-day week is decided in advance, every meal slot is pre-allocated with a signed portion size. The decision is already made before you ever step into the kitchen.

3. Per-Slot Calorie & Macro Budgeting

Generating under a ceiling is not just about keeping the daily sum low. If breakfast claims 16g of your 20g budget, lunch and dinner are forced into unrealistic, unpalatable austerity.

Repast enforces per-slot macro budgeting. Breakfast, lunch, dinner, and optional snacks each receive a balanced allocation of calories and carbs, ensuring every meal of the day is satisfying.

KEY TAKEAWAY

A true meal planner solves the math before you buy groceries, never after you swallow dinner.

UNYIELDING BOUNDARIES

Hold a 20g net carb limit with zero overage.

Repast stress-tested 16,933 multi-day profiles to guarantee exactly 0.0g carb overage. Strict ketosis, solved automatically.

Lock your carb ceiling on iPhone