The same guarantees, at kitchen scale.
A household is a small organization with no IT department, the same coordination problems, and far more at stake in the data it hands to strangers.
This week at home
- Lentil stewOn the plan for Tuesday
- Cupboard checkedLentils in, carrots short
- Added to the listSix carrots, one stock
- 11.40 euroLands on the week as a cost, not a guess
Illustrative example · a plan becoming a cost
The situation
People plan meals, track what is in the cupboard, manage dietary needs, shop, split costs, remember what the doctor said, and coordinate who is doing what. Each of these has an app, each app wants an account, and the accumulated record of a family's life ends up distributed across a dozen companies that will each be acquired or shut down.
How this usually goes
Every app is free because the household is the product.
The data that would make the next app useful is stuck in the last one.
A service closes and takes years of records with it, which is annoying for recipes and serious for health notes.
Nothing connects: the meal plan does not know the cupboard, the cupboard does not know the shop, the shop does not know the budget.
What happens here
Meals, supplies, health, and money for a household, held to the same rules about ownership, memory, and exit as anything an organization runs.
1. The household is a first-class boundary
It is a real scope with members, roles, and permissions, so a teenager, a parent, and a visiting carer see appropriately different things without anyone administering a permissions matrix.
2. The domains connect because they share a record
Planning a week of meals draws on what is in the cupboard, produces what needs buying, respects dietary constraints, and lands as a cost. That chain works because the domains publish to the same event history, not because someone built an integration.
3. Health and dietary information stays scoped
Sensitive records live under explicit policy, including where they may be processed and what a delegated assistant is allowed to see. Convenience does not get to quietly widen that.
4. Leaving is the same operation as for anyone else
A household export is not a smaller, worse version of the enterprise one. It is the same documented format, because the guarantees are properties of the system rather than tiers of a plan.
Why this belongs on this site
A platform that only protects organizations has decided that ordinary life is where surveillance is acceptable. The household scale is also the honest test of the design: if the contracts are too heavy to serve a family of four, they are too heavy, and that would be worth finding out early.