1. Autopilots for x.plural

    Every "autopilot for X" was waiting on an operating system.

    You've seen the pitch a thousand times. Autopilot for accounting. Autopilot for recruiting. Autopilot for sales ops, legal review, support triage, invoice reconciliation. It's a good pitch. It's also a filter. To build autopilot for X, somebody has to raise money for X, hire for X, sell into X, and defend a category called X against three other companies doing the same.

    Read →
  2. Formable

    Stop shopping for solutions. Start forming them.

    Every piece of software you use is somebody else's frozen answer to a problem they decided was worth answering. That isn't a complaint. Frozen answers are great. Someone thought hard, built the thing, and now you don't have to. The whole industry runs on it and mostly that's good. But freezing has costs, and they're easy to miss, because they show up as absence.

    Read →
  3. Modelbound

    Your files should outlive your model.

    Nobody starts work. You resume it. You sit down and before you can do the thing, you have to rebuild the situation you left. The draft tells you what you wrote but not what you ruled out. The folder tells you where the file is but not why there are three of them. So you go looking — through yesterday's messages, your own notes, the tabs you left open as a message to yourself.

    Read →
  4. Wrapware

    Rebuilding is the easier path.

    Right now every attempt to put AI into an operating system looks about the same. There's an assistant in a sidebar. It can see your screen. It reaches into your apps through whatever crack it can find — either driving the interface like a very fast hand, or calling the handful of functions some vendor decided to expose.

    Read →
  5. Software 3.0 Needs an Operating System

    Karpathy describes a new programming substrate. ISPO is an attempt to build the durable, permissioned desktop around it.

    In his 2025 talk “Software Is Changing (Again)”, Andrej Karpathy gives the current AI transition a useful name: Software 3.0. Software 1.0 is the code we write directly. Software 2.0 is the behavior learned into neural-network weights. Software 3.0 is software programmed in natural language, with large language models interpreting intent and taking action.

    Read →