Dinner does not happen at a desk.
It happens at the fridge door, in the aisle, on the couch after work — and sometimes in a chat with an AI assistant that needs real kitchen context. Outline below: why Ration for iOS (store name Ration Kitchen Hub) matters, and how one household data model ties every surface together.
Hook
- Dinner decisions land wherever people actually are: fridge, grocery aisle, laptop, AI client.
- A second “phone pantry” that drifts from the web app is worse than no app.
- Goal: one kitchen memory that follows you — no shadow inventory.
What launched
- Ration Kitchen Hub on the App Store (iPhone).
- Native access to the full loop:
- Cargo — pantry stock, quantities, expiry
- Galley — recipes matched to what you have
- Manifest — weekly meal plan
- Supply — shop only what you are still missing
- Ask Ration — in-app Copilot on live household data
- AI scan / generate where credits apply
- Same account and household as the web app and PWA.
The value story: one household data model
- Four operational surfaces share one org-scoped kitchen: Cargo → Galley → Manifest → Supply.
- You can work that same kitchen from:
- Web / PWA
- iOS
- Ask Ration (Copilot)
- MCP (Claude, Cursor, ChatGPT, and other clients)
- No parallel pantries. No “agent copy” that diverges from what you see in the Hub.
- Semantic matching keeps recipe ingredient names honest against real Cargo names.
Closed loop in the pocket
- Orbital framing is the product, not decoration: stock → cook options → plan → shop the delta → dock purchases back into Cargo.
- iPhone is for the moments the loop is physical — standing in the kitchen or the store.
- Waste less because the list and the pantry agree; buy less “just in case.”
Two control modes, same kitchen
- Native UI — day-to-day pantry ops, planning, shopping on device.
- Ask Ration — natural language against live Cargo / Galley / Manifest / Supply.
- MCP — external agents use the same org-scoped tools (not a separate data plane).
- Choose the modality; keep one source of truth.
Who it’s for
- Households that want one shared inventory and coordinated meal planning.
- People optimizing for less waste and faster shops.
- Anyone who wants durable kitchen memory their AI assistants can read and update.
How to start
- Already on web? Sign in on iPhone with the same account — household data is already there.
- New? Create a free account on the web, or download first and sign up in-app.
- Download on the App Store
- Connecting an external agent? See /connect and the MCP guides on this blog.
Closing
- One kitchen. Every surface.
- iOS joins web, Copilot, and MCP on the same household loop — so dinner logistics stay operable wherever you are.