bodyctl: a closed loop for body comp, still being wired up

I lift. I track macros. I order groceries from Swiggy Instamart. None of those three things talk to each other, and stitching them in my head every week was getting old.

So I started building a thing that does it for me.

The pitch is simple. One input. Your weight. The rest runs in a loop.

What it tries to do

A goal engine takes your weight each week and adjusts your macros. Mifflin under the hood with a controller that doesn't overshoot. A meal planner solves for a set of meals that hit those macros within your budget and prep time, picking from a list of Indian options. A grocery aggregator turns that plan into a Swiggy Instamart cart. A Hevy hook (optional) reads your training and bumps carbs on heavy days. A dineout fallback handles the nights you eat out, recorded as a range, not a fake-precise guess.

That's the whole loop on paper.

Where it actually is

Honest version: the closed loop is mostly an open loop with a few finished sections.

Shipped: the macro engine, the food database, the schema. Mid-build: the meal planner, the Hevy integration. Blocked: the Swiggy ordering piece is sitting behind a Builders Club approval that's been pending for a while.

So no, you can't one-click your groceries yet. Most of the interesting bits are still being wired up. I'm putting this here partly to keep myself moving on it.

More

bodyctl.in. Join the waitlist if you want in once the rest of the loop is actually wired up.