The SOP became the runtime.

The SOP became the runtime.

Monday, September 28. Cognizant put Workflow Agentic Processing on TriZetto Facets and QNXT. Agents carry out a health plan's standard operating procedures on eligible routine pended claims. Denials, exceptions, complex cases route to human reviewers. Change the procedures and the automation moves with them. No custom rebuild every time policy shifts. More than 200 million members sit on those platforms. Over $500 billion in annual healthcare spend moves through claims, eligibility, prior auth, payment integrity.

Three days earlier, September 23. UiPath launched Cartographer. Builds a Map of Work: living, governed, unique to each process, with a named owner who approves every change. Decisions feed back into the map. Nothing changes on its own. Same day Avalara unveiled Aviator, an agent hub for tax and compliance with an audit-defensible record for every action. Avi orchestrates lead agents on research, certificates, returns. People keep the judgment calls. Same day Valtech launched Agent Factory at DMEXCO and ran a roundtable titled "The ghost in the org chart: Who actually manages your AI workforce?"

September 22. Teradata turned Tera into an agentic coworker. Context Engine, Harness, Agent Skills. Eighty-four execution patterns applied before inference so the agent starts with a plan instead of burning tokens inventing one. Ships Q4.

Last week Amazon put unauthorized AI agent on a Muse popup and cut the path on identity. This week is the buyer side wiring agents into the systems that already run the business. Claims. Tax. Process maps. Data work. Different seam.

The read everyone had

Default take: more copilots, now with MCP tools and nicer audit logs. Vendors racing to stick agents inside the apps enterprises already pay for. Governance bolted on. Human-in-the-loop as the press-kit noun.

That read is right about the packaging and wrong about the layer.

These ships are not asking the agent to draft an email about a claim. They are asking the agent to execute the operating procedure the buyer already wrote. Cognizant is blunt: the health plan's own SOPs guide the run. Cartographer is blunt: the Map of Work is customer-owned, with a named owner. Avalara wants every action audit-defensible. Valtech is asking who manages the AI workforce once it shows up in the org chart as a ghost.

The runtime is the procedure.

Procedure without an owner is just a prompt with better branding

Restate what shipped without the product gloss. Cognizant: update the SOP, automation follows. UiPath: map how work actually runs, including the exceptions people quietly handle, and keep a human approving changes. Avalara: a record for every action you can defend. Teradata: start from known execution patterns, not from scratch every loop. Valtech: versioning, rollback, approval gates, one inbox for work that needs a person.

Pull the vendor logos off and you have the same missing object. A versioned procedure. A named owner. A record of which version ran, on which case, under which exception path. That is not a dashboard. That is the instrument.

I keep landing on how little of that looks like a commercial object yet. Most of it still lives as a PDF in SharePoint, a Confluence page nobody touched since Q2, or tribal knowledge in the claims desk that trained the new hire last spring and then left. Cartographer is trying to make the object real. Cognizant is hanging an agent on whatever SOP the plan already has. Those are not the same maturity. One is inventing the map. The other is running against a map that may not exist cleanly, and pretending the PDF counts.

I've watched physical markets choke when the "procedure" was a spreadsheet with three owners and no version stamp. The work still happened. Nobody could prove which rules were live when something broke. Agents compress that failure mode. They don't invent it.

The machine-speed problem

Human SOP drift had slack. Someone noticed the desk was using last year's exception rule. A supervisor yelled. A wiki got edited. Ugly, slow, recoverable.

An agent that clears routine pended claims against a procedure that changed on Thursday and a twin that still has Wednesday's copy does not leave that slack. By the time audit reconstructs which version ran, a few thousand claims have already moved. Avalara's audit-defensible record helps after the fact. It does not answer whether the procedure the agent executed was the one the principal meant to be live when the claim posted.

Same category as last week's identity problem, different surface. Amazon refused a session it could not name. Here the buyer can name the agent and still not name the procedure version with confidence. Identify the machine. Then identify what it was allowed to run.

I wonder if the first expensive failure this winter is not a rogue agent but two agents running two versions of the same SOP against the same book, both authorized, both logged, both wrong relative to each other. The audit trail will be spotless. The book will not.

What the right layer looks like

What the buyer and the auditor both need is thinner than another agent shelf. A procedure object with a version, a named owner, a change log, and a binding to the run. This SOP, this revision, this agent, this case, this exception path. Checkable when the claim posts, not excavated when the regulator asks. Independent of which vendor's agent executed it. Aimed at the people who have to defend the outcome: the plan, the tax desk, the process owner Valtech is hunting in the org chart.

UiPath's named-owner language is the closest public cut this week. Cognizant's update-the-procedure-not-the-code language is the closest operational cut. Neither is a portable instrument yet. They are pressure in the right direction, which is as far as a press cycle usually gets before the next demo.

Watch who builds the procedure object as something an auditor, a counterparty, or a regulator can hold without trusting the operator's wiki. Everything else this week is still a better way to run against a document nobody owns.

The order is always wrong

#027 was refuse on identity. Seller side. Can I see the agent as an agent before I let it in.

This week flips to the buyer side. Agents are already inside the core systems, executing the buyer's own procedures. Capability shipped first. Claims automation. Tax hubs. Process maps. Agent factories. The procedure object with an owner and a version stamp that travels with the run is still the layer most of the market has not priced as a thing you can hold.

I've watched that sequence enough times to stop being surprised by it. Systems of record get agents. SOPs get treated as prompt fuel. Ownership of the live version stays fuzzy until something expensive forces the org chart to name a human. Valtech called it the ghost. That noun travels.

Close

Monday Cognizant put agents on TriZetto and told them to run the plan's SOPs. Wednesday UiPath put a named owner on the Map of Work. Avalara wants an audit trail for every action. Teradata wants the plan before the loop. Valtech asked who manages the AI workforce.

Last week the seller refused the unnamed login. This week the buyer is discovering that naming the agent is not enough if the procedure it runs has no owner and no version you can check when the claim already posted.

Watch who treats the SOP as a commercial object, not a wiki page. The runtime already moved. Ownership has not.

Max

Disclosure: Accords, where I'm Executive Chairman, is a portfolio position I chair.

Max Curnin has spent 11 years and 45+ investments on the physical rebuild of the economy: energy, compute, robotics, and the materials underneath. He writes The Agent Economy on the category he invests in.