“More agency” should eventually become visible in a life someone is glad to be living.
That sounds obvious until it meets most AI productivity conversations. We say people will be empowered, time will be freed, and potential will expand. Useful claims need more precision. Who gains capacity? For which recurring responsibility? At what cost of supervision, coordination, and repair? A tool can save time on one activity while adding a new obligation to manage the arrangement it created.
Use dinner as a test case. It is ordinary, specific, and unforgiving in the way recurring human life tends to be. People get hungry again tomorrow. A helpful system would not merely generate meal ideas. It would fit the actual week, know what is in the house, respect budget and preferences, prepare a usable shopping flow, handle exceptions, and reduce the burden on the person who normally holds the whole thing together.
The feedback is concrete. Did the ingredients arrive? Did the meal fit the evening? Could the human understand and change the plan? Did fewer obligations fall through? Did the system remain useful during an unusual week? How often did someone have to rescue the process? Those questions tell us more than the number of tasks an agent reports completing.
The rescue question is especially important. A system may look successful because a capable person compensates for its failures. They notice the missing ingredient, correct the schedule, chase the delivery, rewrite the instruction, and remember the exception. The outcome eventually happens, so the automation receives credit. The human supplied the missing coherence and now has one more system to maintain. Count that work before announcing how much work disappeared.
The same test belongs at work. If AI helps a team produce twice as much material, ask what happened to decisions, review queues, rework, and the people who absorb ambiguity. More output can be valuable. It can also make unresolved coordination problems arrive faster. Before calling it greater agency, ask whether the people responsible for the result gained a meaningful ability to direct it.
A useful measurement set would include human time spent running the system, exception frequency, rescue frequency, decision clarity, review burden, error recovery, and the user’s ability to understand and change the arrangement. For an enterprise workflow, add evidence availability, accountable owner, permission boundary, and whether the system still works at reduced capacity. Agency is not the same as throughput. Agency includes the capacity to steer.
This is also a stewardship question. Attention, capacity, resources, and responsibility are given toward something. Work has a purpose beyond its own continuation. Love becomes practical in decisions about what we protect, what we make possible, and whom we remain available to. That conviction applies as much to institutional governance as to a meal. Architecture should return to the people it is supposed to serve.
The design implication is simple: establish the human outcome before optimizing the machinery. If the purpose is to make evenings less chaotic, the system must reduce coordination burden at the time it matters. If the purpose is to help a team make responsible decisions, the system must preserve evidence, understanding, and authority. The model or agent architecture follows from the purpose, not the other way around.
That trace also tells us when to simplify. An elaborate arrangement may be worth maintaining because it serves a complex need. A smaller one may serve the need with less overhead. The measure is whether people can do what matters with more understanding and less avoidable friction. A magnificent control tower for dinner may be technically impressive. It should still remember that it exists because people get hungry.
The future of intelligence should not only help us build larger things. It should help responsibility become more livable at human scale.
The future of intelligence should arrive in time for dinner.