The Consent Cabinet
A household stack should make shared life easier without turning the people inside it into one shared account.
Personal capability becomes social the moment it coordinates care, money, schedules, memories, or a home. That is where a stack needs drawers.
A household stack is a coordinated set of records, routines, and AI assistance that helps people run a shared life while keeping each person’s authority visible.
The app-to-stack transition described in The First Stack Generation is often pictured at work: one person assembling tools, sources, preferences, and methods that improve with use. But the first consequential stack may be closer to home. It may remember the school form, the recurring repair, the care instruction, the renewal date, the family recipe, the account that only one person should see, and the question nobody has decided.
Applications already coordinate parts of this life. A calendar holds appointments. A bank app holds transactions. A group chat holds fragments of logistics. The problem is not that these systems are useless. It is that each one makes a different, usually hidden guess about who may see, decide, or act. A more capable stack can connect those fragments. It can also turn convenience into quiet surveillance if it assumes that connection means entitlement.
App People share a login. Stack People negotiate a boundary.
App People are not careless. They often solve a household problem with the tools available: forward the password, add everyone to the calendar, keep the answer in one person’s notes, or let the most technically fluent person become the administrator of everything. The arrangement can work until a relationship changes, a child becomes independent, a caregiver needs limited access, or a private decision becomes visible by default.
Stack People have a chance to make the boundary more exact. The useful question is not “Who owns the app?” It is “What may this person know, change, or carry forward—and for how long?” That is a design question, not merely a settings question. It requires naming the shared purpose before choosing the tool.
Every useful drawer needs a different key.
This is not a proposal for a universal family dashboard. It is a test for the kinds of context a household stack might hold. Choose a drawer to see what changes when the stack treats a boundary as part of the work.
means
private.
A stack can help a person prepare, remember, and decide without making their health note, financial concern, personal correspondence, or unfinished thought legible to the rest of the household. Intimacy does not erase a person’s right to an interior.
needs a
purpose.
A repair schedule, a grocery pattern, a school pickup plan, or a recurring bill can be maintained together. The shared record should state what it is for, who may revise it, and how a disagreement becomes visible instead of being silently resolved by the most active account.
is not
unlimited.
Emergency access matters. So does its scope. A stack can make a medication list, travel document, or care instruction available when a defined condition occurs without converting an exception into permanent permission to browse someone else’s life.
Care should not require invisible administrators.
Household labor often disappears into the person who remembers. That person tracks the appointment, notices the expiring form, translates a letter, orders the replacement, and knows which detail will matter later. AI can reduce some of that burden. It can create reminders, summarize a shared decision, turn a recurring repair into a checklist, and surface a missing handoff.
But assistance is not fairness by itself. A stack that only amplifies the existing administrator can make the imbalance more efficient and less visible. The better use is to make the work inspectable: what is pending, what is shared, what is waiting for a decision, and what must remain with its owner.
- 01
Separate memory from permission
A system may remember that a task exists without granting every household member the underlying documents.
- 02
Make delegation reversible
Access to coordinate care or pay a bill should be reviewable, time-bounded, and easy to withdraw when circumstances change.
- 03
Leave a human decision where it belongs
A stack can prepare a choice, but it should not quietly convert convenience into consent or a suggestion into a family rule.
The social unit of the stack is not the account.
As personal AI capabilities become more durable, ordinary life will produce more shared systems: a couple’s move, a parent’s care plan, a group household’s budget, a neighborhood repair circle, a family archive. None needs to become a corporate operating system. Each needs a way to distinguish the person, the group, the task, and the exception.
That is the cultural challenge inside App to Stack. The stack should not make every relationship into a merged data environment. It should make coordination more capable while preserving the fact that a shared life is made of separate people. A well-built cabinet does not prove its usefulness by opening every drawer. It proves it by helping people find the right one when they need it.