Automating Toward Freedom

Play video

The signals

• Omar: We wildly overindex the things we can count and show. List the ten most important things in your life, then score each one twice, on how quantifiable it is and on how visible it is to other people. Those two naturally get the energy. Sit with it long enough and the things that matter most are in neither column. His example is becoming a father: "It really is invisible to everyone except for me, and hopefully one other person in the universe called my daughter."
• Sam: Forty of fifty repositories were not to the current standard, and the automation had no stated target. Sam pointed the episode's takeaway, an agentic skill, at about fifty of his own repositories and asked one narrow question of each: is where this project is going actually expressed, so the agents working across it align to the same thing? Forty came back not to standard. When the intent is written down, the agents "can tack themselves". The question underneath: "the automation is great, but what am I automating towards?"

The subtractions

• Omar: Six hours door to door. The rule arrived in a single sitting in meditation and it governs acquisitions for the whole group: they will not look at a business that takes longer than six hours to reach from the office. It survives because it is simple enough to say once and have everyone apply it without him. Sam's reading of the real unit of measure: "Two bath times, sorry." He culls the inputs deliberately and keeps no digital platform of any kind.
• Sam: Every obligation names an accountable party, and almost none name the backup. Running his own skill across everything he has taken on, the gap was not ownership, it was fallback. So the skill asks "who is the backup to that accountable party", the question regulated industries systematically miss, because regulation forces you to name accountability and not the backup. The cuts have not been made yet.

About this episode

The spine of the episode is the sailboat, and it is worth the runtime on its own. The speedboat is the model most people carry: set a direction, fill the tank, go in a straight line regardless of conditions. Sailing is the honest one. You can set the intention, you can make the craft effective, you can make the crew effective, "and then I must sail with whatever wind shows up." The hardest case for a driven person is when the wind is not against you but absent, where "the most wise thing to do is literally just sit there and read a book." Progress has to be measured against the conditions you are actually in, and he is candid that the same reasoning doubles as an excuse generator if you let it. Three things he can control, and only three: where I am going, how effective is my vessel, how effective and whole is the crew. Then the daily practice of getting still enough to notice when he has gone astray, which he distinguishes carefully from the wind being unhelpful: the failure that matters is heading the wrong way regardless of the wind.

For anyone building with agents, the transferable part is the four questions and the loop around them. Why, who, where, and what now, answered clearly enough that people can act without routing back to him. On the who, he does not flinch at the obvious extension: if the work is entirely AI generated, it may be just him and computers, and "those are the who's". Underneath the four questions sits the attuning, "like looking at your instruments", and above it the monthly cadence. They keep scorecards like any other business, and the question asked of them is deliberately not what all the data is saying. Money can be up while four things that matter went the wrong way, and money can be down in a year that was strategically excellent. He also notes the conversations that create the clarity are stubbornly analog, because they are between humans.

Omar's one direct word to the people building this stuff comes from his own training as a mechanical engineer. The engineering mind starts from what could I do, gets excited, and starts doing. His encouragement is to install a pause: "not just what can I do, but will that be a useful thing even if I'm successful?" The follow-on is the part builders skip, that plenty of wonderful things have been built for which there turned out to be no market, and that pausing at milestones to ask who is going to use this and why is cheap next to finding out later.

The closing frame is borrowed and very old. The inner scorecard against the outer scorecard, which he credits to Warren and Charlie and then places correctly as a stoic idea with about two thousand years on it. Old problems, old solutions. It is the same move he made in his thirties when the balanced life he had built still did not feel different on the inside, and he went looking for the oldest viable solution to a problem humans have always had.

Want to bring your own signal and subtraction? Find yours.

The newsletter

Issue 69 · Sunday 20 September 2026 · sent on Substack and LinkedIn.

One signal, one subtraction, one analogy, in five minutes. It draws on this episode but stands on its own. Every issue.

The method from this episode is one page with its copy-paste prompt and schema: Name the Human, linked under the decision above. Every takeaway.