Every week runs the same loop at my house. What's for dinner. What do we have. What do we need. Three questions, usually asked standing in front of an open fridge, usually answered with a grocery run that buys things we already own.
I'm building an app that runs that loop for you. It's called Amalthea. You plan the week's meals, and the grocery list builds itself from the plan minus what is already in the pantry. After the store, a photo of the receipt updates the inventory. That's the core. Everything else hangs off it.
I'm entering it in the RevenueCat Shipaton, and I'm building the whole thing in public. Solo founder, two CS courses running at the same time, and a live Play Store listing due by September 30. This page is where the long version of that trail lives. The short version runs on X.
What exists today
Not much, on purpose.
The repo went live on August 21. First commit, first pull request, CI green. Before a single feature, the test runner, the linter, and the type checker were wired so every change from here on has to pass through them. I've shipped enough things where tests came last to know they never come at all that way.
The history is clean from commit zero. No secrets, no leftover strings, nothing I'd have to scrub later. The repo is private while it gets built and flips public at submission, so going public had to be a switch, not a cleanup job.
That's the whole inventory. A repo, a passing build, and a plan.
How the updates work
Posts here fire on milestones, not dates. When the database schema lands, that's a post. When the closed test opens and I need 12 testers, that's a post, and a real ask. When something slips, the slip is the post. The judges score the lessons, and a miss named out loud is one.
Next update when the schema lands. Or when it doesn't.