What Are We Saving Time For?

If AI gives us back an hour, I hope we leave some of it open.

I want to build at a scale that matters. The prospect of a small team doing work that once required a large organization excites me. Someone with a good idea could have more of what they need to begin. A business owner could spend less of the day on paperwork and more of it with customers. More people should have a real chance to build something worthwhile.

I founded Gooroo because I wanted good teaching to be easier to reach. AI could bring patient help within reach of a student whose family cannot afford a tutor. It could also give a teacher more time to notice a student who has gone quiet. I want better tools to make learning easier to begin and difficult things less frightening to attempt.

Over the coming years, I expect more of us to give software an outcome and let it work out the steps. Those steps will cross tools, organizations, and accounts. The number of actions may grow far faster than our ability to inspect them. In that future, dependable delegation will need infrastructure of its own.

If every action needs someone watching, we will spend much of the attention we hoped to get back. I want systems that can do useful work within limits we can understand and enforce. Those limits need to survive a change of plan or a handoff to another system. A person’s “stop” should still mean something when the system is moving fast.

That is part of why I am building HALTSEAL. The first problem is a payment with an unresolved outcome. The original attempt may have paid or may still pay; sending again through another provider could pay the same obligation twice. HALTSEAL is designed to hold that second attempt while the first outcome remains unresolved, across the paths it governs. Before release, it checks the exact payment against current authority and evidence about earlier attempts. A new route should not create a new right to pay.

Payments are the starting point. I want HALTSEAL to become one part of the infrastructure that makes consequential software actions safe to entrust. The safety I am working toward should let people delegate more with confidence while preserving the limits they set. A small team should be able to take on larger work without having to live in constant supervision of its software.

My Christian faith shapes this ambition. I believe a person’s worth is already there, before anything they accomplish. Love of neighbor asks me to care about the people affected by my work, including those who never chose to use it. In software, that care has to reach into the design: whose money is at risk, whose decision is being carried out, who has to recover when something goes wrong. Care should arrive before someone has to bear the consequence.

That standard has to apply to my own life, too. Building technology that gives people time would mean little if I became too busy to notice the person in front of me. I want to keep asking what my ambition makes possible for other people, and what it is doing to me.

We will also have to decide what the saved time is for. An afternoon freed by software could simply fill with more work. Efficiency does not automatically become freedom. I hope some of the gain becomes time people can call their own: time to learn something slowly because it interests them, room to begin again after a hard year, a dinner that runs long because nobody wants to leave.

I want to help build a future we have time to live in.