Less work required to meet a need
Measure the paid and unpaid hours required for a defined service, including work shifted to stewards and caregivers.
A BUILDING DIRECTION / BILLY COLEMAN III · BUDDHA
Less of life
spent surviving.
More of it living.
I want to build the post-labor fabric.
The intelligence, automation, and shared infrastructure that could help people meet their needs with less dependence on selling their time.
Not a world without contribution. A world where access to a decent life is less conditional on the market price of your labor.
01 / EXPLORE THE POSSIBILITY
A need becomes
a shared capability.
This is an illustrative dependency model—not a live network, measured impact, or a promise of abundance. Change the conditions. See what remains unresolved.
Connections represent proposed dependencies, not actual transfers of resources or services.
ISOLATED CAPABILITIES
The pieces exist in the scenario. A dependable service does not.
Available capacity is only an assumption. Separate providers still need workable commitments, coordination, and continuity.
What this could enable
Identify complementary capabilities and the agreements needed to connect them.
What still has to be secured
Land, water, energy, ingredients, safe storage, transport, and physical work. None is created by connecting software.
What must be tested
Meals actually received; full cost and labor per meal; missed deliveries; access during shortages.
02 / WHAT SUSTAINED SUPPORT MAKES POSSIBLE
Fund the capacity
to stay with the problem.
Dependable support would give me time, compute, and continuity to build and test this direction with real participants. The aim is useful, accountable infrastructure—not a growing collection of demos.
More dependable access
Track whether people receive the service, what it costs, and what happens during shortages—including for people unable to contribute.
Control that stays with participants
Test shared decision-making, transparent allocation, portable records, and replacing a provider without losing access or history.
Capacity others can reproduce
Publish working components, operating costs, maintenance demands, failures, and instructions another group can independently use.
03 / WHERE I WOULD START
Start with something
people need.
Make it easier to get.
Imagine a neighborhood where getting an affordable meal takes too much money, travel, or time. There may already be growers, a kitchen, and people who can deliver. But bringing them together can be difficult.
- Listen to the people involved. Find out what prevents meals from reaching people—and what the growers, cooks, and drivers need to keep helping.
- Build something that takes work off their hands. For example, a simple service that brings meal requests, available food, and delivery plans together, with people checking important decisions.
- Find out whether life actually gets easier. Are meals more affordable and reliable? Do families and organizers get time back? Who is still being left out?
- Share what works. Explain how another neighborhood could use it, what it costs, and who needs to keep it running.
Sponsorship would give me the time and computing resources to do this work with people, improve it, and keep going. Food is an example—not a project or partnership already agreed. The first need would be chosen with the people taking part.
What technology cannot do by itself
Someone still has to grow the food, prepare it, and deliver it. Equipment needs repairs. Supplies cost money. The people involved need fair rules, including what happens when there is not enough for everyone. My aim is to make that work easier to organize—not pretend those needs disappear.