The Harness Era

Koko: Most large enterprises have made AI their top investment priority, budgets keep climbing, and the overwhelming majority plan to keep increasing spend — even as a majority admit they cannot yet see the return. Max: So the universal reaction to not knowing if this is working is: more of it. Koko: Which, to be fair, is also how a lot of enterprise software buying works. But the piece makes the point that this particular gap — between adoption and actual enterprise-wide impact — is not a model problem. And that is the move that sets up the whole argument. Max: Right, because the instinct when something is not working is to blame the tool. Get a better model. Wait for the next release. And the series is essentially saying that instinct is sending you in exactly the wrong direction. Koko: And there is a very specific reason why. The frontier model, as the piece puts it, is now a commodity input — interchangeable, rapidly cheapening, available to every competitor on identical terms. Max: Which is a genuinely uncomfortable sentence if you have spent the last two years in benchmark debates. Koko: Very uncomfortable. Because it means the most powerful component in your stack is also the most evenly distributed. And if your competitor can buy the exact same thing on the same terms tomorrow, it cannot be where advantage lives. Max: So where does advantage live? Koko: The layer almost no one is funding. They call it the harness. Max: Okay, so let us define that term, because harness is doing a lot of work here. Koko: It is. And the piece is careful about it. A model reasons. A prompt produces an answer. An agent completes a task. A harness makes that task repeatable, governed, tested, auditable, and value-accountable. Those are four very different things. Max: The distinction I keep coming back to is the one between a clever demo and a capability you can fund and audit. Because most enterprises right now are stuck somewhere in that gap. Koko: That is exactly where the series plants its flag. And the reason they are stuck is not that they bought bad models. It is that they bought agents and skipped the harness. Max: And the piece gives you three specific forces that make orchestration the actual moat. First, models converge — so whatever edge you have from model choice is temporary by definition. Second, agents sprawl — so without a control plane you just have a pile of copilots that nobody can govern. And third, value stays ambiguous until you instrument it. Koko: That third one is the one that keeps cost reviews killing AI programs. If you cannot show the return, you are always one budget cycle away from being cut. Max: And the question the piece says should be driving strategy is not 'can AI answer this?' It is 'can an agent safely change the outcome of this process?' That is a much harder bar. Koko: And a much more honest one. Koko: So the series takes the harness apart layer by layer. Eight essays, eight components. Let us walk through the ones with the sharpest edges. Max: Start with the agent card, because I think it is the most underrated idea in the whole thing. Koko: The agent card is a control document for every production agent — recording its owner, purpose, persona, process, provider, model, tools, data products, risk tier, human-approval triggers, outputs, evals, controls, and value linkage. Max: Which sounds like a lot of fields until you hear the alternative framing: an agent without a card is an anonymous actor with production access. Koko: That line lands. The analogy the piece uses is the org chart — which made human accountability legible — and the data sheet, which made a physical part sourceable and auditable. The agent card does the same for autonomous work. Max: And it has to exist before anything downstream works. The piece is explicit that it is the precondition for governance, not a nice-to-have you add later. Koko: Now pair that with the value card, which is the funding mechanism. Every agent carries a baseline, a target, a value lever, an owner, and a benefit-attribution method. And the lever maps to one of five things — revenue, margin, working capital, productivity, or risk. Max: The rule the piece gives is blunt: no value card, no scale funding. Which is either obvious or revolutionary depending on how your organization currently funds AI. Koko: Most organizations fund it the way you fund a tool — by seats, tokens, prompt volume. And the piece says that is exactly why most of it dies at the first cost review. Usage is not a return. Max: Usage is not a return. Someone should put that on a poster in every AI program office. Koko: Then there is the trust debt index, which is where the piece gets a little nervy. Forrester named what they call the trust tax — the drag that ungoverned, unexplainable AI puts on adoption. The series says: give it a number. Max: A score that captures things like unsupported claims, weak evidence, missing controls, no human-in-the-loop on material actions, no evidence trail, no eval pack. Koko: The analogy is the credit score — which made counterparty risk legible and tradable. A trust debt score makes agent risk comparable and auditable across your portfolio. Max: And critically, a low score is the direct, measurable consequence of skipping the harness. You can now see, in a number, what cutting governance corners actually costs you. Koko: Which is a very different conversation to have with a board than 'we are being responsible about AI.' Max: Alright, I want to push on one thing, because I think there is a genuine tension in how the series resolves. Koko: Go. Max: The piece argues that finance is where governed agentic execution proves itself first — Month-End Closer, GL Reconciler, Billing Dispute Triage. And the logic is: clear value levers, mature controls, well-understood processes, CFO owns the budget that funds scale. Koko: And you think that is too safe? Max: I think there is a version of this where 'start in the highest-control function' becomes a way to stay in the demo zone indefinitely. Finance is controlled, yes. But it is also where the most risk-averse people in the building sit. Koko: The counter from the piece is that this is precisely the point. The highest-control function is the easiest place to let an agent change a real outcome — because the guardrails already exist. You are not building governance from scratch; you are plugging into it. Max: Okay, that is a fair read. And the sequencing is deliberate — record-to-report first, where control is highest and value is clearest, then generalize to lead-to-cash and source-to-pay, then forecast-to-fulfill and plan-to-perform. Koko: So it is not 'stay in finance forever.' It is 'prove the harness works in the most legible environment and then move.' Max: Which I buy. But I do think any executive reading this needs to ask whether their finance function is actually ready to be the proving ground, or whether it is going to become the place AI goes to get quietly shelved. Koko: That is the right challenge. The process pack idea is actually the structural answer to it — you ship agents as a deployable set with workflows, tools, controls, evals, and value metrics all bundled for one value stream. Not a point-solution chatbot with its own controls story that nobody can manage. Max: One control pack, one eval pack, metrics that roll up to the value stream. That is the architecture that keeps it from getting shelved. Koko: Assuming someone is actually holding the CIO's control plane together underneath all of it. Max: Which brings us back to the fact that the CIO's job is no longer picking a model. It is standing up a model gateway, tool registry, policy engine, approval service, evidence ledger, observability, and value telemetry. Koko: Model-agnostic, so convergence works in your favor — route each task to the cheapest model that clears the bar, swap providers without re-engineering. Max: Which is a completely different org design than most technology functions are currently running. Koko: So let us bring it down to what an executive should actually take away from this. Not the framework — the action. Max: The first one is almost embarrassingly concrete: if you have agents in production without agent cards, you have anonymous actors with production access. Fix that before you scale anything. Koko: Second: audit your funding model. If you are buying AI by seats and tokens and measuring it in usage metrics, you do not have a value story. You have an expense that will not survive a real cost review. Max: No value card, no scale funding. That is the policy to install, not just the principle to agree with. Koko: Third: stop treating the control plane as a future-state IT project. Model gateway, tool registry, policy engine, evidence ledger — these are enterprise-architecture primitives now, in the piece's framing, not science projects. Max: And the model-agnostic point is worth sitting with. If your control plane is built around one provider, you are not positioned to benefit from the commodity dynamic the piece describes. You are locked into exactly the layer where lock-in matters least. Koko: And the broader strategic frame — the piece puts it plainly. The organizations that internalize this now will spend the next few years compounding a governed, measurable capability while their competitors are still comparing benchmarks. Max: And by the time the benchmark race is settled, it will not have mattered. That is the line I keep coming back to. Koko: Because it implies that the benchmark race was never really the race. Max: It was a distraction that a lot of very smart people have been treating as the main event. Koko: The piece ends with a clean summary of where it all lands. The model was never the moat. The moat is the system you build around it and own — the agent card that makes work accountable, the value card that makes it fundable, the control plane that makes it governable, the process pack that makes it deployable, the trust score that makes it auditable, and finance as the place it proves out first. Max: Six components. All connected. And none of them are on the roadmap of the model providers who are selling you the thing. Koko: Which is maybe the most important structural observation in the whole series. The vendors with the loudest voice in enterprise AI conversations are the ones selling the commodity. Nobody is selling you the harness. Max: So you have to build it, own it, and recognize that owning it is the point. Koko: The question I would leave any executive with is this: if you had to give your current AI program a trust debt score right now — against the criteria the piece defines — what would it be? And would you be comfortable sharing that number with your board? Max: That is a genuinely uncomfortable question for most organizations running AI at scale. Or thinking they are. Koko: The full series — all eight essays, fully source-verified, with the framework intact — is on Koko Knows. If this conversation made you want to go deeper on any single layer, that is where to go. Max: And honestly, given how much AI spend is already committed, the timing for this is not 'eventually.' It is now.