An argument that the harness has a ceiling, and that what sits above it is an operating system

The piece opens by drawing a line: "An AI application needs a harness. An enterprise fleet of agents needs an operating system." It takes its definition of a harness from a talk it credits to Charles Holloway, "Build Your Own Harness", given at Colorado Startup Week the week of September 16, which it calls the clearest definition of a harness it has seen. That definition inventories the harness as seven authorities around a shared model: context and state, tools, execution, orchestration, verification, observability, and governance with recovery. The organizing rule is that "each authority owns a fact the model cannot safely assert", with the verification test stated as "If the model's claim is the only evidence, then there is no evidence."

The argument is that every one of those seven is defined relative to a single agent run, and that scaling breaks each one in a different way. Two hundred agents on the same enterprise data turn memory into a permissions problem, two hundred tool lists into an unwritten combined permission set, two hundred per-run journals into a join nobody has written, and sequencing into scheduling. It then names two facts it says a harness has no schema row for at all: accounting, meaning whose budget a run spent, and identity, meaning which agent is acting for whom. Both, it argues, exist only between agents, and "there is no between in a harness." The structural claim is the one worth arguing with: "if you have two hundred control planes, then of course you have zero effective control plane."

This is a positioning argument, and it says so. The closing section is titled "The bet" and names the author's own product: "That is what WunderOS is, an operating system for agents." The post measures nothing and reports no first-party numbers. The Hacker News submission carried 17 points and 13 comments when we read it tonight, four days after posting.

The best thing in that thin thread is Holloway himself, posting as cholloway and signing off as Charles. He accepts the compliment and then declines the conclusion drawn from his own taxonomy: "I don't necessarily agree with you that the harness only solves the problem of one agent... In my view, a useful harness could/should be capable of orchestrating virtually any number of agents." He also concedes ground, saying he has "frequently dreamt of an 'ultimate harness' that could function as an OS for agents" and that the Unix and libc analogy "has caused me to reevaluate this."

Why it matters: The vendor framing is plain and the taxonomy survives it. If you accept the seven-authority inventory, the question of where your fleet's policy lives comes with a test attached: whatever owns the fact "this fleet is within policy" cannot be a member of the fleet. You can run that test against a setup you already have without buying anything. The unresolved part is the one Holloway named, which is where the harness stops and the layer under it starts. AX is one concrete answer, shipping primitives for execution, workspace setup, network policy and model configuration, and none for accounting or identity.