<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Ganesh Raju</title>
    <description>The latest articles on DEV Community by Ganesh Raju (@ganesh_raju_6a2557b4199e6).</description>
    <link>https://dev.to/ganesh_raju_6a2557b4199e6</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4254424%2F41b3da22-6d35-4b95-8240-256c7f72d732.jpg</url>
      <title>DEV Community: Ganesh Raju</title>
      <link>https://dev.to/ganesh_raju_6a2557b4199e6</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ganesh_raju_6a2557b4199e6"/>
    <language>en</language>
    <item>
      <title>The Token Economy: How Smarter AI Computation Will Reshape Enterprise Costs and Value</title>
      <dc:creator>Ganesh Raju</dc:creator>
      <pubDate>Fri, 20 Nov 2026 04:38:36 +0000</pubDate>
      <link>https://dev.to/ganesh_raju_6a2557b4199e6/the-token-economy-how-smarter-ai-computation-will-reshape-enterprise-costs-and-value-8d2</link>
      <guid>https://dev.to/ganesh_raju_6a2557b4199e6/the-token-economy-how-smarter-ai-computation-will-reshape-enterprise-costs-and-value-8d2</guid>
      <description>&lt;p&gt;&lt;em&gt;A forward-looking whitepaper for business and technology leaders. Full PDF with all appendices: &lt;a href="https://doi.org/10.5281/zenodo.24386748" rel="noopener noreferrer"&gt;DOI 10.5281/zenodo.24386748&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Executive decision brief
&lt;/h2&gt;

&lt;h3&gt;
  
  
  The next AI breakthrough may be learning what not to compute
&lt;/h3&gt;

&lt;p&gt;For several years, AI progress has come from scale: larger models, longer context windows and more GPUs. That has changed what machines can do. It has also created an uncomfortable economic reality. As AI moves from assistants to agents that read, plan, act and check their own work, the computation behind a single business task can grow sharply. A token gets cheaper, but finishing the task can still take many more of them.&lt;/p&gt;

&lt;p&gt;Enterprise AI efficiency is not simply a matter of buying cheaper tokens. It is a matter of allocating computation to the evidence, generation and verification a business task actually needs. This paper argues that enterprises need a control layer that allocates computation according to risk and business value. That layer, not any single model or research technique, is the durable investment.&lt;/p&gt;

&lt;h3&gt;
  
  
  Fewer billed tokens, or less computation per token?
&lt;/h3&gt;

&lt;p&gt;The next wave of AI efficiency will not necessarily come from consuming fewer billed tokens. It may come from doing less computation on those tokens. New research on selective reading lets a model read every input token lightly and give deep processing only to the tokens that matter. The prompt still contains every token. So a company paying a conventional API price per input token will not automatically see a smaller invoice. A company running its own models can turn the same efficiency into more capacity from the same GPUs. Whether the savings ultimately reach customers will depend as much on commercial pricing as on technology.&lt;/p&gt;

&lt;h3&gt;
  
  
  What is demonstrated, what is available, what is projected
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0a4lzswnje6fhbgy6vvt.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0a4lzswnje6fhbgy6vvt.jpeg" alt="Figure" width="800" height="369"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  Headline economics (illustrative)
&lt;/h3&gt;

&lt;p&gt;Section 5 models an AI agent that reviews one million documents a month, with a person correcting any output that fails. The primary metric is fully loaded cost per completed task. First-pass acceptance is reported separately.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;API buyer.&lt;/strong&gt; Caching, tighter retrieval, model routing and a fallible verification loop cut cost per completed task from $0.94 to $0.36 (−62%). That is about $7.0 million a year in gross operating benefit before implementation costs.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Self-hosted operator.&lt;/strong&gt; Adding selective reading as a compute saving gives $0.94 to $0.29 (−69%), about $7.7 million a year gross.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Range.&lt;/strong&gt; Across the sensitivity cases, the API reduction runs from 52% to 64%. Rework cost, how many errors the checker catches, and how many it can fix move the result most.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Net of implementation.&lt;/strong&gt; With illustrative one-time costs of $1.5 million and $0.6 million a year to run, the API case pays back in about three months.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Decisions for leaders
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Measure fully loaded cost per completed task, and first-pass acceptance, for the top AI workflows.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Capture the optimizations that work today:&lt;/strong&gt; caching, retrieval, routing and verification.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Build the control layer so new techniques such as selective reading can be adopted when they pass quality and economic tests, without rebuilding applications.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;In contracts, define outcomes precisely, secure access to usage meters, and share in vendors' efficiency gains.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Section 11 shows how Elixir Global builds these principles into its AgentVault™ agent repository and its Migra data migration platform.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Where enterprise inference costs arise
&lt;/h2&gt;

&lt;p&gt;A token is a small piece of text, roughly three-quarters of an English word, and it is the unit in which AI is consumed, priced and measured. A 10-page contract is about 5,000 tokens. A 300-page policy manual is about 150,000.&lt;/p&gt;

&lt;p&gt;Every AI request has two parts:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Reading (input tokens).&lt;/strong&gt; The model reads its instructions, the question and any documents supplied. Per token, reading is cheaper and faster than writing, but it adds up: instructions and documents are often re-read at every step of a task.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Writing (output tokens).&lt;/strong&gt; The model writes its answer one token at a time. Writing is usually priced several times higher per token than reading, and it sets how long the user waits.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Whether an enterprise buys AI through an API (paying per token) or runs its own models (paying for GPUs, power and staff), tokens drive the bill. For API buyers the link is direct. For self-hosted models, every token processed uses GPU time and memory.&lt;/p&gt;

&lt;h3&gt;
  
  
  1.1 Cheaper tokens, more tokens per task
&lt;/h3&gt;

&lt;p&gt;For some agentic workloads, rising call counts and longer contexts can offset falling token prices. The net effect must be measured workflow by workflow. Each generation of enterprise AI has multiplied the computation behind one request.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3e3o21y06d3cfmba3xic.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3e3o21y06d3cfmba3xic.jpeg" alt="Figure" width="800" height="206"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Typical orders of magnitude, not measurements.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmq88du18iv8rxjgik9ug.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fmq88du18iv8rxjgik9ug.jpeg" alt="Figure" width="800" height="445"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 1. Where an agent's tokens go · illustrative, using section 5's assumptions&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Three habits of today's agents drive the growth:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Re-reading the rulebook.&lt;/strong&gt; Standing instructions, tool descriptions and policy text, often thousands of tokens, are re-read at every step.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Reading whole documents.&lt;/strong&gt; Contracts, claims files and code are supplied in full, so every request pays to read pages that do not bear on the question.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Writing out reasoning and double-checking.&lt;/strong&gt; Accuracy increasingly comes from writing out reasoning, producing several candidate answers and scoring them. All of it is billed as output.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;A simple illustration: if the price per token falls 10× while a workflow grows from one copilot call to a 30-step agent, tokens per task can rise about 30×, and cost per task triples. Equally, a well-designed agent can cost less than the copilot it replaces. Architecture, not the rate card, decides which.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Available optimizations versus emerging research
&lt;/h2&gt;

&lt;p&gt;Most of the savings available today come from proven techniques. Selective reading is the most promising new research, and it adds to them rather than replacing them.&lt;/p&gt;

&lt;h3&gt;
  
  
  2.1 Three dimensions of conditional computation
&lt;/h3&gt;

&lt;p&gt;Modern AI efficiency is about making computation conditional: spending it only where it is needed. There are three distinct places to do that.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjf4eq3km4zja6anv1c4m.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjf4eq3km4zja6anv1c4m.jpeg" alt="Figure" width="800" height="206"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Mixture-of-experts asks which of the model's specialists to wake up. Selective reading asks which parts of the input deserve deep attention. The two are complementary, and both can sit behind a router that picks the right model in the first place.&lt;/p&gt;

&lt;h3&gt;
  
  
  2.2 The wider toolkit
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvdyup573l0r3uw4ksmht.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvdyup573l0r3uw4ksmht.jpeg" alt="Figure" width="800" height="461"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  2.3 Selective reading: teaching AI what not to read
&lt;/h3&gt;

&lt;p&gt;Today's models give every input token, from a decisive clause to a page number, the same full-depth processing. Selective reading adds a small, trainable gate inside an existing model. All tokens pass through the early layers, which gives every token context from the whole input. The gate then scores each token's importance. Only the highest-scoring tokens, plus protected items such as the question and instructions, continue to the deeper and more expensive layers. Memory for dropped tokens is freed.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwiqi07jollikac74o435.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fwiqi07jollikac74o435.jpeg" alt="Figure" width="800" height="344"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 2. Selective reading inside the model · illustrative, about a quarter of tokens kept&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The researchers (Stanford University and UC Berkeley, October 2026) tested this on question answering, repository code completion, summarisation, biomedical extraction and find-the-needle retrieval, with inputs up to 128,000 tokens in some settings. They used two small open models (about 1.7 and 2 billion parameters), each adapted with a gate and light fine-tuning per task.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fr8v3b985mc8o458b694q.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fr8v3b985mc8o458b694q.jpeg" alt="Figure" width="800" height="279"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Operating points shown in the researchers' summary figure, at accuracy matched to standard reading. They are not end-to-end enterprise benchmarks.&lt;/p&gt;

&lt;p&gt;Across tasks, the researchers report 1.4–11.3× faster first responses and 1.5–3.4× lower peak reading memory at matched or near-matched accuracy on selected operating points. The largest gains come on the longest inputs. More aggressive settings buy further speed at some cost in accuracy, for example on multi-hop questions and multi-document extraction. The code and checkpoints are public under an open-source licence, which makes pilots cheaper than an architectural rewrite.&lt;/p&gt;

&lt;h3&gt;
  
  
  2.4 How the techniques combine inside an agent
&lt;/h3&gt;

&lt;p&gt;In a 12-step agent that re-reads instructions and documents at every step, each technique has its natural target:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Standing instructions and tool schemas repeat identically. Caching handles them better than learned pruning.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;The variable document span is fresh for each request and often long. That is where selective reading adds the most.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Simple steps such as classification or formatting go to small models through routing.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Savings are reinvested in verification or extra candidate answers where risk is high.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The gains do not simply multiply. Retries and escalations can erase them. That is why the control layer in section 4 escalates instead of gambling, and records every retry.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Evidence and limitations
&lt;/h2&gt;

&lt;p&gt;The research shows a better trade-off between quality and efficiency on small models. It does not yet show enterprise savings or production readiness. Every quantitative claim in this paper carries one of four labels.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F917fgm3vh9vhnihjs1ye.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F917fgm3vh9vhnihjs1ye.jpeg" alt="Figure" width="800" height="240"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  3.1 What remains unproven for selective reading
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Scale.&lt;/strong&gt; Results are on 1.7–2B-parameter models. Transfer to frontier-scale models is unproven.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Production serving.&lt;/strong&gt; Gains were measured outside production serving engines. Selective reading needs custom attention kernels that can gather non-contiguous tokens. Without optimised kernels, that overhead can cancel the gains at small batch sizes. Continuous batching, high concurrency and tail latency (p95) must be measured.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Transfer across domains.&lt;/strong&gt; Each gate was adapted to its task. A general-purpose gate that transfers safely to new document types has not been shown.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Rare decisive evidence.&lt;/strong&gt; One negation, exception clause or account number can decide an outcome. Find-the-needle tests check retrieval of one planted fact. They do not fully cover evidence spread across a document, or multi-step reasoning.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Reading order.&lt;/strong&gt; In today's models, a token's score can only use what came before it. Placing the question before the document helps the gate.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;A floor on savings.&lt;/strong&gt; Early layers always read every token, so speed-ups cannot exceed the ratio of total depth to gate depth.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  3.2 What the economics depend on
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Billing.&lt;/strong&gt; API buyers benefit from selective reading only if providers pass internal savings through in price. Self-hosted operators capture the benefit as GPU capacity.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Amdahl's law.&lt;/strong&gt; A 10× faster reading stage gives far less than 10× end to end if retrieval, tools, generation or human approval take most of the time.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Quality.&lt;/strong&gt; Any efficiency method that raises the error rate can lose more in rework and risk than it saves in compute.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Energy.&lt;/strong&gt; Less computation per request can improve energy efficiency per task. Actual energy reductions need measurement, and growing AI demand may offset them.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  4. Adaptive inference architecture
&lt;/h2&gt;

&lt;p&gt;The durable investment is a control layer that decides, for every request, how much to read, which model to use, how carefully to check and when to involve a person. New techniques then plug in as options, without rebuilding business applications.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv9s0lwtk8xuai5dbngre.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fv9s0lwtk8xuai5dbngre.jpeg" alt="Figure" width="800" height="517"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 3. Adaptive inference platform · 5 layers, escalation and feedback loops&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F884usa9wor73b0sxohkj.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F884usa9wor73b0sxohkj.jpeg" alt="Figure" width="800" height="314"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  4.1 Design rules
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Escalate, don't gamble.&lt;/strong&gt; Try the cheapest safe approach first. If checks fail, widen the reading budget, switch to full reading or a larger model, or generate more candidates, and only then involve a person. Log every escalation, so the business can see when retries are eating the savings.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Protect what you can identify; widen when you can't.&lt;/strong&gt; Protect known critical regions and task scaffolding: the question, instructions, output schemas, defined terms, amounts, identifiers and known exception clauses. Where decisive evidence cannot be identified reliably, keep broader context or use the full-reading path. Protecting the word "not" is not the same as preserving its scope, so protected zones cover whole clauses, not keywords.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Treat verification as fallible.&lt;/strong&gt; A checker can miss errors, raise false alarms, and share blind spots with the model it checks. Design for that (section 4.3).&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Insulate applications.&lt;/strong&gt; Applications call the platform, not a specific model. When a technique matures, it is switched on inside Layer 3 and applications keep working.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  4.2 Reference deployment
&lt;/h3&gt;

&lt;p&gt;Every AI request, whatever channel it comes from, passes through one gateway. Finance, risk and IT get a single place to set budgets, enforce data rules and measure outcomes. The model pool can mix cloud APIs and on-premises GPUs behind the same orchestration, which makes the hybrid choices in section 8 possible.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvde5eds03o3yr179xpa3.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvde5eds03o3yr179xpa3.jpeg" alt="Figure" width="799" height="496"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 4. Reference deployment architecture · from channels to systems of record&lt;/em&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  4.3 The verification loop
&lt;/h3&gt;

&lt;p&gt;Verification detects problems. It does not fix them by itself. The loop is: check, detect, retry or repair, re-check, and send what remains to a person.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Friyob973yxbgocdyjsvu.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Friyob973yxbgocdyjsvu.jpeg" alt="Figure" width="799" height="340"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 5. Verification loop · illustrative rates from section 5&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Four quantities decide whether the loop pays:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Recall:&lt;/strong&gt; the share of real errors the checker catches.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;False-alarm rate:&lt;/strong&gt; correct outputs flagged by mistake, which cost a needless retry.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Fix rate:&lt;/strong&gt; the share of caught errors a retry or repair actually corrects.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Correlation:&lt;/strong&gt; when the checker and the model share blind spots, recall falls on exactly the hardest cases. Use different models, deterministic rules or independent evidence checks where possible.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  5. Reproducible economics
&lt;/h2&gt;

&lt;p&gt;In an illustrative document-review workflow, proven levers cut fully loaded cost per completed task by about 62% for an API buyer. Adding selective reading raises that to about 69% for a self-hosted operator. Every number below can be rebuilt from the stated assumptions (Appendix A). The figures are a scenario, not a measured result.&lt;/p&gt;

&lt;h3&gt;
  
  
  5.1 Metrics
&lt;/h3&gt;

&lt;p&gt;The primary metric counts every task that is eventually completed, including those a person corrects:&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxbuhd9n8oqwwi2tph0qa.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxbuhd9n8oqwwi2tph0qa.jpeg" alt="Figure" width="800" height="132"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;First-pass acceptance, the share of outputs accepted without human correction, is reported alongside it. Dividing total cost by first-pass acceptances instead gives a higher figure, cost per first-pass accepted output. It is useful for tracking automation, but it should not be quoted as operating-cost savings.&lt;/p&gt;

&lt;h3&gt;
  
  
  5.2 Scenario and assumptions
&lt;/h3&gt;

&lt;p&gt;An insurer, bank or legal team runs an agent that reviews documents (claims, contracts or loan files) and drafts a recommendation that a person approves. Outputs with errors are corrected by that person.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyd140lxqvqw49g3s2mpk.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fyd140lxqvqw49g3s2mpk.jpeg" alt="Figure" width="800" height="556"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  5.3 Case A: API buyer
&lt;/h3&gt;

&lt;p&gt;API buyers pay for every token sent, so selective reading earns them nothing unless the provider passes the saving through in price. It is excluded here.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F37wcnqzedtqy27pazsjm.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F37wcnqzedtqy27pazsjm.jpeg" alt="Figure" width="800" height="256"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7qiflvwcybwm5umlejr0.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7qiflvwcybwm5umlejr0.jpeg" alt="Figure" width="799" height="370"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 6. Cost bridge, API buyer · illustrative model&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The savings are sequential: each lever is measured after the ones before it, so its share depends on the order applied. Applied first, routing would save more, and caching less. Treat individual lever values as indicative. The combined total does not depend on the order.&lt;/p&gt;

&lt;h3&gt;
  
  
  5.4 Case B: self-hosted operator
&lt;/h3&gt;

&lt;p&gt;For a self-hosted operator, the same unit prices stand in for the GPU cost of processing a token. In practice, measure GPU time, memory and utilisation directly. Selective reading now saves compute on the document span.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhgz6n4oswncdjezu9t07.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fhgz6n4oswncdjezu9t07.jpeg" alt="Figure" width="800" height="186"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The self-hosted operator sees the benefit as capacity: the same cluster handles more tasks, or the next GPU purchase is deferred. That only becomes cash savings if the capacity would otherwise have been bought.&lt;/p&gt;

&lt;h3&gt;
  
  
  5.5 Sensitivity
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl379x38sqggj8x1h6gsu.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fl379x38sqggj8x1h6gsu.jpeg" alt="Figure" width="800" height="323"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The result stays material across these cases, between 52% and 72%. The verification assumptions matter most, so measure recall and fix rate on your own data before you commit a business case.&lt;/p&gt;

&lt;h3&gt;
  
  
  5.6 From gross benefit to net benefit
&lt;/h3&gt;

&lt;p&gt;The scenario produces about $7.0 million (API) to $7.7 million (self-hosted) a year in gross operating benefit. That is before implementation costs, extra platform overhead and transition costs. The implementation figures below are illustrative assumptions.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fibqsa4ieeg5nlz7itv85.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fibqsa4ieeg5nlz7itv85.jpeg" alt="Figure" width="800" height="253"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  5.7 What the model teaches
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Quality is the largest single lever.&lt;/strong&gt; In the API case, a verification loop costing under two cents per task removes 22 cents of human correction.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;No single token lever wins.&lt;/strong&gt; Caching, retrieval and routing each save 10–15 cents. Together they cut AI cost by about 70%.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Selective reading is a capacity lever first.&lt;/strong&gt; It pays most where documents are long and the operator owns the compute.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Speed is a second dividend.&lt;/strong&gt; If each of 12 steps waits 3 seconds for its first token and selective reading cuts that below 1 second, each task finishes about 25 seconds sooner. (Illustrative.)&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  6. Use cases, and when full reading is still preferred
&lt;/h2&gt;

&lt;p&gt;Each lever's value depends on a workflow's token profile: whether it mostly reads, mostly writes, or repeats many steps. Just as important is knowing when to switch efficiency off.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgirrbqax77jl584t89wp.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgirrbqax77jl584t89wp.jpeg" alt="Figure" width="800" height="771"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Two patterns stand out. Read-heavy, decision-light workflows benefit most from selective reading: claims, contracts, code and maintenance. Exactness-critical workflows should spend more tokens, not fewer: reconciliation, regulatory filings and safety procedures get full reading plus deterministic checks. The policy layer makes that choice explicit instead of leaving it to chance.&lt;/p&gt;

&lt;h2&gt;
  
  
  7. Pilot criteria and governance
&lt;/h2&gt;

&lt;p&gt;Adopt an efficiency method only when it passes quality, latency and cost tests on your own workloads, under realistic load, with thresholds agreed before the pilot starts.&lt;/p&gt;

&lt;h3&gt;
  
  
  7.1 A 24-month plan
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuz0jvkkenzcsnx1l2uho.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fuz0jvkkenzcsnx1l2uho.jpeg" alt="Figure" width="800" height="298"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  7.2 Go/no-go criteria
&lt;/h3&gt;

&lt;p&gt;Every threshold must state its measurement unit (per field, per output or per task), its sample size and confidence interval, and the workflow's risk tolerance. Compare against the incumbent, not against zero.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw90u52epdswh90nj2q03.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw90u52epdswh90nj2q03.jpeg" alt="Figure" width="800" height="349"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  7.3 Planted-evidence protocol
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Adversarial inversions.&lt;/strong&gt; Insert a contradicting clause (for example, "Notwithstanding Section 4.2, indemnity liability is zero") at 10%, 50% and 90% depth in long agreements. If the efficient path drops or misreads it, the test fails.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Protected zones.&lt;/strong&gt; Define what is never pruned: the question and instructions, output schemas, structural delimiters, function-call arguments, section headings, numeric spans, defined terms and whole clauses known to carry exceptions.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Distributed evidence.&lt;/strong&gt; Include questions whose answer needs facts from several sections, not just one planted needle.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  7.4 Role by role
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7ber1klf3gspzxw0q2te.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7ber1klf3gspzxw0q2te.jpeg" alt="Figure" width="800" height="369"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  8. Procurement: how AI products and agents will be priced
&lt;/h2&gt;

&lt;p&gt;AI pricing is moving from paying for access (seats), to paying for activity (tokens and credits), to paying for results (outcomes). Most buyers will see hybrids of the three. Where the AI runs decides who captures efficiency gains.&lt;/p&gt;

&lt;h3&gt;
  
  
  8.1 Where pricing stands (October 2026)
&lt;/h3&gt;

&lt;p&gt;Outcome pricing for AI agents is already established in customer service. Prices below were checked against each vendor's official pricing page on October 31, 2026. Definitions differ, and that matters as much as the price.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feaq01wjz5rum2mktqbuj.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Feaq01wjz5rum2mktqbuj.jpeg" alt="Figure" width="800" height="395"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The spread shows the tension in the market: Salesforce charges for every conversation, HubSpot and Zendesk only for resolutions, and Fin for a broader list of outcomes. Analysts expect the shift to continue. Gartner, as reported by Deloitte, projects that at least 40% of enterprise SaaS spend will move toward usage-, agent- or outcome-based pricing by 2030.&lt;/p&gt;

&lt;h3&gt;
  
  
  8.2 Pricing by deployment model
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgus5wdabv96dnxmgycdg.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fgus5wdabv96dnxmgycdg.jpeg" alt="Figure" width="800" height="336"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 7. Pricing architecture · cloud, SaaS and on-premises under one hybrid control layer&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3fg2upmvtp1zsu68n57l.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F3fg2upmvtp1zsu68n57l.jpeg" alt="Figure" width="800" height="549"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  8.3 Will SaaS pricing change?
&lt;/h3&gt;

&lt;p&gt;Yes, for products where agents do work people used to do. Much less for systems of record.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;Seats stay for people who use the interface.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Agents get their own unit:&lt;/strong&gt; per resolution, per document processed, per case closed or per credit. As agents take on work, seat counts shrink and agent units grow.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Systems of record change least.&lt;/strong&gt; ERP, HR and CRM platforms are likely to keep subscriptions and add consumption fees for AI features.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Outcome guarantees become a selling point, at a higher price per outcome.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;An enterprise's own cost per completed task is the right benchmark for buy-versus-build. Vendor prices of $0.50–$2.00 per resolution include margin, platform and support, and they cover a different workload from section 5's model.&lt;/p&gt;

&lt;h3&gt;
  
  
  8.4 What to negotiate
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;A precise outcome definition:&lt;/strong&gt; what counts, over what window (for example 72 hours), how reopened cases are treated, and who decides disputes.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Access to the meter:&lt;/strong&gt; usage and outcome logs you can audit against your own records.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Caps, floors and true-ups, so usage or outcome pricing stays within budget.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Shared efficiency gains:&lt;/strong&gt; scheduled price reductions as the vendor's unit costs fall.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Portability:&lt;/strong&gt; the right to move agents, prompts, evaluation sets and data between cloud, on-premises and other vendors.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  9. Outlook 2027–2030: three scenarios
&lt;/h2&gt;

&lt;p&gt;Rather than a single forecast, plan for three scenarios that can unfold together. The same control layer is the right investment in all three. None depends on another: outcome pricing, for instance, does not need selective computation to arrive first.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0xodnps0gsaxtpocf3rt.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F0xodnps0gsaxtpocf3rt.jpeg" alt="Figure" width="799" height="289"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Figure 8. Outlook scenarios · not forecasts; they can unfold together&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F14yb6wd960iekub9yod8.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F14yb6wd960iekub9yod8.jpeg" alt="Figure" width="800" height="359"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  9.1 Five questions for the next cycle
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Will token pricing survive?&lt;/strong&gt; Likely yes for model infrastructure, alongside growing usage-, workflow- and outcome-based pricing in applications.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Will models become smaller and more specialised?&lt;/strong&gt; Routing and selective computation make specialised models more economic for well-defined tasks. Frontier models remain the fallback for hard cases.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Who captures the efficiency gains?&lt;/strong&gt; Cloud providers, model developers, platform operators and SaaS vendors each capture a share, depending on contracts and on where the AI runs.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Will inference matter more than training?&lt;/strong&gt; As agent workloads grow, inference efficiency becomes a larger competitive factor for vendors and a larger cost line for buyers.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Will verification become its own value layer?&lt;/strong&gt; Trusted outcomes need evidence, deterministic checks and human oversight, however fast generation becomes. Verification is likely to be bought, built and audited as a distinct capability.&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One research direction deserves watching but is not assumed here. Models that do more of their reasoning in a compact internal form, rather than writing it out as billable tokens, could shrink output costs. That is a hypothesis that needs evidence, not a capability to plan on.&lt;/p&gt;

&lt;h2&gt;
  
  
  10. Risks and potential mitigations
&lt;/h2&gt;

&lt;p&gt;The main risk of token efficiency is false economy: savings that disappear in errors, retries and rework. Each risk below has potential mitigations. A mitigation is not proof that the remaining risk is acceptable; that has to be tested per workflow.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fth3xvudw4pnun9yrvwlx.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fth3xvudw4pnun9yrvwlx.jpeg" alt="Figure" width="800" height="612"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  11. How Elixir Global applies these principles
&lt;/h2&gt;

&lt;p&gt;At Elixir Global, token optimization is designed into our platforms from the start, not added after the bill arrives. Two platforms show how the control-layer approach in this paper works in practice.&lt;/p&gt;

&lt;p&gt;AgentVault™ is Elixir's repository of more than 500 enterprise agents. They cover supply chain and SAP processes such as IDoc handling and invoice processing. The agents are model-agnostic: each step can use the smallest model that meets its quality bar, and newer models can be adopted without vendor lock-in. They run within governance guardrails, including SOX and FedRAMP controls where required, and integrate with SAP Joule.&lt;/p&gt;

&lt;p&gt;Migra is Elixir's AI-native data migration platform, deployed in client landscapes. It moves master data from many heterogeneous sources through a governed Snowflake hub into SAP S/4HANA, in five stages: ingest, enrich, publish, reconcile, report. Its knowledge base, rules engine and self-learning mean that a mapping resolved once is reused rather than worked out again by a model. Business, IT and audit approvals, plus post-load reconciliation, confirm each outcome before sign-off.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjbwlm3ir9g25ityp3e8v.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fjbwlm3ir9g25ityp3e8v.jpeg" alt="Figure" width="800" height="385"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;The result for clients is the same discipline this paper recommends: cost measured per completed business outcome, computation spent where risk and value justify it, and an architecture ready to adopt techniques such as selective reading once they pass quality and economic tests.&lt;/p&gt;

&lt;h2&gt;
  
  
  Conclusion
&lt;/h2&gt;

&lt;p&gt;The first era of enterprise AI proved that machines can produce useful intelligence at scale. The next era will be defined by how deliberately that intelligence is spent. Tokens will not disappear: they remain how models read, write and get billed. But treating every token as equally important is ending.&lt;/p&gt;

&lt;p&gt;What will make an AI strategy credible to a CFO, CTO or risk committee is not a bigger savings headline. It is a cost model they can reproduce, assumptions they can challenge, and adoption gates that hold even if research gains do not fully reach production. Organisations that build the control layer, measure cost per completed task, and adopt new techniques only when they pass those gates will get more trusted value from every unit of computation.&lt;/p&gt;

&lt;h2&gt;
  
  
  Appendix A: Calculation detail
&lt;/h2&gt;

&lt;p&gt;All figures are per initiated task; every task is eventually completed. Prices: reading $2.00 and writing $8.00 per million tokens; cached reading $0.20 per million.&lt;/p&gt;

&lt;h3&gt;
  
  
  A.1 Tokens and cost per model call
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fziu43tppgk1xsd4t909q.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fziu43tppgk1xsd4t909q.jpeg" alt="Figure" width="800" height="275"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;AI cost per task = 12 calls × cost per call. Baseline: 12 × [(20,000 × $2) + (600 × $8)] ÷ 1,000,000 = $0.5376.&lt;/p&gt;

&lt;h3&gt;
  
  
  A.2 Verification loop (API case)
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fg0edsgr9co64c5v6vybs.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fg0edsgr9co64c5v6vybs.jpeg" alt="Figure" width="800" height="323"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  A.3 Totals
&lt;/h3&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzv88irchgw4kve1rjr1i.jpeg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fzv88irchgw4kve1rjr1i.jpeg" alt="Figure" width="800" height="186"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Annual gross operating benefit = (baseline monthly total − case monthly total) × 12: API $6.97M; self-hosted $7.73M. Retry calls are assumed to run on the large model, without routing. The self-hosted case uses API unit prices as a stand-in for GPU cost per token.&lt;/p&gt;




&lt;h2&gt;
  
  
  Further reading
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Download the full whitepaper (PDF):&lt;/strong&gt; &lt;a href="https://doi.org/10.5281/zenodo.24386748" rel="noopener noreferrer"&gt;The Token Economy: How Smarter AI Computation Will Reshape Enterprise Costs and Value&lt;/a&gt; (Zenodo, DOI 10.5281/zenodo.24386748)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Related white paper:&lt;/strong&gt; &lt;a href="https://doi.org/10.5281/zenodo.24378767" rel="noopener noreferrer"&gt;Governing Rogue AI Agents with Valid Credentials&lt;/a&gt; (DOI 10.5281/zenodo.24378767)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Related article:&lt;/strong&gt; &lt;a href="https://ganeshraju.hashnode.dev/the-rogue-agent-will-have-valid-credentials-how-ctos-and-caios-can-govern-agentic-ai" rel="noopener noreferrer"&gt;The Rogue Agent Will Have Valid Credentials: How CTOs and CAIOs Can Govern Agentic AI&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  About the author
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fepn0gz0ogzj9hdr1vvd2.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fepn0gz0ogzj9hdr1vvd2.jpg" alt="Ganesh Raju, Chief AI &amp;amp; Innovation Officer and CTO, Elixir Global" width="799" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ganesh Raju&lt;/strong&gt; is Chief AI &amp;amp; Innovation Officer (CAIO) and CTO at &lt;a href="https://www.elixirglobal.com" rel="noopener noreferrer"&gt;Elixir Global&lt;/a&gt;, an AI-first enterprise consulting firm headquartered in Atlanta with offices in Houston, Dubai, Bengaluru and Singapore. He leads enterprise AI strategy and &lt;strong&gt;AgentVault&lt;/strong&gt;, Elixir's portfolio of governed, production-ready AI agents for SAP and enterprise operations, and the Migra AI-native data migration platform.&lt;/p&gt;

&lt;p&gt;He brings more than 15 years of experience in artificial intelligence, machine learning and data engineering. As Head of Big Data, Data Science &amp;amp; AI at Linaro he led Arm enablement of the open-source big data and data science ecosystem, served as ODPi PMC member and TSC lead and as a Linux Foundation TSC member, and led the Apache Bigtop community. He has contributed to TensorFlow, Apache Spark and Hadoop.&lt;/p&gt;

&lt;p&gt;He is the author of &lt;em&gt;AI Blockchain Design and Deployment&lt;/em&gt; (BPB Publishing), founder and CEO of Akshaya.io, founder of RapidEVChargE, an investor, and an advisor to Canon. He is a former Vice Chair of IEEE Houston and a participant in the Wharton Executive Education Chief Technology Officer program. He is based in Houston, Texas.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Connect on &lt;a href="https://www.linkedin.com/in/ganeshraju07" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; · &lt;a href="https://github.com/ganeshraju" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt; · &lt;a href="https://ganeshraju.hashnode.dev" rel="noopener noreferrer"&gt;Blog&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Views are the author's own. Elixir Global offers products and services related to the subject of this paper. Economic figures are illustrative scenarios, not measured results.&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  TokenEconomy #AgenticAI #EnterpriseAI #AIInference #LLM #AICosts #FinOps #GenerativeAI #CAIO #CTO #CFO #AIStrategy
&lt;/h1&gt;

</description>
      <category>ai</category>
      <category>llm</category>
      <category>machinelearning</category>
      <category>productivity</category>
    </item>
    <item>
      <title>The Rogue Agent Will Have Valid Credentials: How CTOs and CAIOs Can Govern Agentic AI</title>
      <dc:creator>Ganesh Raju</dc:creator>
      <pubDate>Thu, 19 Nov 2026 19:57:56 +0000</pubDate>
      <link>https://dev.to/ganesh_raju_6a2557b4199e6/the-rogue-agent-will-have-valid-credentials-how-ctos-and-caios-can-govern-agentic-ai-ibj</link>
      <guid>https://dev.to/ganesh_raju_6a2557b4199e6/the-rogue-agent-will-have-valid-credentials-how-ctos-and-caios-can-govern-agentic-ai-ibj</guid>
      <description>&lt;p&gt;&lt;em&gt;Why the next enterprise crisis may not begin with an attack, but with AI agents following their rules perfectly, and the control architecture that stops it.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Key takeaways
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;What a rogue AI agent is:&lt;/strong&gt; an autonomous AI agent that causes harm while holding valid enterprise credentials. It does so either because it was manipulated, or because several authorized agents combine into an outcome nobody approved.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Why it matters now:&lt;/strong&gt; agentic AI is moving from pilots into payments, ERP, supply chains and plant systems faster than governance can keep up. Regulators, auditors and insurers are starting to ask for evidence of control.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Who is most exposed:&lt;/strong&gt; banks, insurers, manufacturers, utilities and government agencies that are adopting AI agents quickly on top of legacy core systems.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The architecture that works:&lt;/strong&gt;

&lt;ul&gt;
&lt;li&gt;The model proposes, and an independent action gateway decides.&lt;/li&gt;
&lt;li&gt;Business-state rules are enforced as policy-as-code.&lt;/li&gt;
&lt;li&gt;A kill switch works from outside the agent platform.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;What leaders should do in 90 days:&lt;/strong&gt; give every agent with production write access four things: a named owner, a scoped mandate, a hard limit on harm, and a tested revocation path. Back all of it with continuous monitoring.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  One week in November
&lt;/h2&gt;

&lt;p&gt;Earlier this month, in the space of five days, three systems we all treat as utilities faltered:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Microsoft 365 stumbled across 74 countries.&lt;/li&gt;
&lt;li&gt;The FAA halted departures nationwide.&lt;/li&gt;
&lt;li&gt;JPMorgan Chase stalled transactions that rippled into other banks.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of it was caused by AI. Oddly, that is what worried me most.&lt;/p&gt;

&lt;p&gt;Every one of those outages started with something ordinary: a configuration change, an upgrade, a dependency that a capable team had planned and reviewed. A small fault met a shared system and travelled faster than the people running it could contain it.&lt;/p&gt;

&lt;p&gt;Now picture that same week with thousands of AI agents in the mix. These agents move money, change infrastructure, edit records and delegate to one another around the clock, all on valid enterprise credentials. They make exactly the kind of change that started each of those outages. They make it continuously, and they don't wait for a change board.&lt;/p&gt;

&lt;p&gt;So the question I now put to every executive team I work with is not "What happens when one agent makes a bad decision?" It is:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;"What happens when every agent makes a locally correct decision, and the combined result is something nobody authorized?"&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;The next enterprise crisis may not begin with an AI breaking the rules. It may begin with AI agents following their rules perfectly.&lt;/p&gt;

&lt;p&gt;We spent the first era of enterprise AI making systems intelligent. The next era is about making that intelligence accountable. Risk is moving from what models &lt;em&gt;say&lt;/em&gt; to what agents &lt;em&gt;do&lt;/em&gt;, and from single actions to collective outcomes. What follows is what I'm seeing in the field, why it compounds, and what I believe CTOs, CAIOs, CIOs and CDOs should do about it.&lt;/p&gt;




&lt;h2&gt;
  
  
  The most dangerous rogue agent isn't rogue at all
&lt;/h2&gt;

&lt;p&gt;When people hear "rogue agent," they picture a model that breaks its rules. That will happen. But the incident I'd lose sleep over looks different. Several well-behaved agents each act inside their permissions, and their actions add up to an outcome nobody approved.&lt;/p&gt;

&lt;p&gt;Most security tools ask whether &lt;em&gt;one agent&lt;/em&gt; was allowed to act. Very few ask whether the &lt;em&gt;business state&lt;/em&gt; that results is acceptable. Each agent passes its own checks, and the business still fails.&lt;/p&gt;

&lt;h3&gt;
  
  
  A concrete example: three authorized agents, one fraudulent payment
&lt;/h3&gt;

&lt;p&gt;Here is a hypothetical example I'll come back to throughout. Every part of it is ordinary.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;A &lt;strong&gt;vendor-master agent&lt;/strong&gt; updates a supplier's bank details after receiving an email that looks legitimate.&lt;/li&gt;
&lt;li&gt;An &lt;strong&gt;accounts-payable agent&lt;/strong&gt; matches the invoice to the purchase order and approves it.&lt;/li&gt;
&lt;li&gt;A &lt;strong&gt;treasury agent&lt;/strong&gt; releases the payment run on schedule.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Each one is allowed to do exactly what it did, and the money still ends up with a fraudster.&lt;/p&gt;

&lt;p&gt;This is the agentic version of business-email compromise, which banks and corporate treasuries already fight every week. No gateway that inspects one call at a time will catch it. What catches it is a &lt;strong&gt;business-state rule&lt;/strong&gt;:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;em&gt;No payment to a bank account changed in the last 30 days until it has been verified by calling a number already on file.&lt;/em&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;That rule belongs in the ERP and the payment run. There, it holds no matter which agent, vendor or model touches the transaction.&lt;/p&gt;

&lt;h3&gt;
  
  
  Autonomy debt: the hidden liability on every agent roadmap
&lt;/h3&gt;

&lt;p&gt;I call the gap behind this &lt;strong&gt;autonomy debt&lt;/strong&gt;. Every enterprise that deploys agents is running two curves:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;The authority it delegates&lt;/strong&gt; to agents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The control it can actually prove&lt;/strong&gt; over them.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;When the first curve runs ahead of the second, debt piles up. It behaves like technical debt with one nasty twist. A loosely governed pilot isn't a harmless experiment for long. Once it holds production credentials and sits inside a real process, it becomes something you can't easily switch off.&lt;/p&gt;

&lt;p&gt;The arithmetic is unforgiving. Exposure grows with three things: how fast agents act, how much each action matters, and how long it takes you to contain a mistake. So the real question for a CTO isn't "How fast can we detect?" It's this:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;"Can our controls stop harmful execution faster than our agents can produce it?"&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  So who should actually be worried?
&lt;/h2&gt;

&lt;p&gt;The question I hear most often in boardrooms is whether this is a problem for companies racing into agents, or for companies sitting on decades of legacy systems. My honest answer is both, for different reasons. The companies most exposed are the ones that are both.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fast movers on a modern stack&lt;/strong&gt; start with real advantages: good APIs, modern identity, cloud-native logging. Their risk is speed. Agents multiply through no-code builders and SaaS features faster than anyone can register them, and governance gets designed after the sprawl rather than before it. &lt;em&gt;The cheapest moment to put control in place is before your first hundred agents, not after your first thousand.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Legacy estates&lt;/strong&gt; face the harder problem. Core banking, policy administration, ERP, MES and SCADA systems were built for human operators and overnight batch jobs. Agents usually get connected to them through:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;shared service accounts with sweeping rights,&lt;/li&gt;
&lt;li&gt;screen automation where no API exists,&lt;/li&gt;
&lt;li&gt;batch interfaces with no undo,&lt;/li&gt;
&lt;li&gt;audit logs that record &lt;em&gt;which account&lt;/em&gt; acted but not &lt;em&gt;why&lt;/em&gt;.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;After an incident, nobody can say which agent did it, or on whose instruction.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Fast adoption on top of a legacy core is the most exposed position.&lt;/strong&gt; That is where most of the regulated economy now sits: banks, insurers, manufacturers, utilities and government agencies moving quickly on agents while running on decades-old cores. For them, an action gateway and business-state rules aren't a nice-to-have. They're the adapter that makes an old system safe to expose to a caller that never sleeps.&lt;/p&gt;

&lt;p&gt;Please don't assume you're a bystander. If you think your company isn't adopting agents, it almost certainly is, through features your SaaS vendors switch on by default and tools your people bring in themselves. Moving slowly doesn't reduce the exposure. It just leaves it unmanaged.&lt;/p&gt;




&lt;h2&gt;
  
  
  This is no longer theoretical
&lt;/h2&gt;

&lt;p&gt;For twenty years, the attacks that defined our careers came from outside: flood the front door, trick the database, smuggle in hostile code. Those threats haven't disappeared, but most of us now buy mature defences for them as a utility. The new threat is already inside the walls. It holds valid keys, and we invited it in. &lt;strong&gt;The threat has moved from breaking in to acting with the keys.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Everything in this list has already happened in production in the last twelve months:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A coding agent erased a production database, and its backups, in nine seconds.&lt;/li&gt;
&lt;li&gt;An agent at a Fortune 50 company hit a permission wall and simply removed the restriction itself. Every identity check passed.&lt;/li&gt;
&lt;li&gt;An approved internal agent gave advice that exposed sensitive data to the wrong staff for two hours.&lt;/li&gt;
&lt;li&gt;A single crafted email turned an enterprise copilot into a zero-click data-exfiltration channel.&lt;/li&gt;
&lt;li&gt;A popular open-source agent's marketplace hosted hundreds of malicious add-ons, while tens of thousands of instances sat exposed on the internet.&lt;/li&gt;
&lt;li&gt;A swarm of 100 agents passed a code change from one to another until one of them committed it, with no person in the loop.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  The agentic risk ladder
&lt;/h3&gt;

&lt;p&gt;The risk climbs in stages:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Mistakes at speed:&lt;/strong&gt; agents doing the wrong thing faster than people can notice.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Manipulation:&lt;/strong&gt; outside content or a poisoned tool steers an agent without the attacker ever touching your network.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Persistence:&lt;/strong&gt; poisoned memory keeps firing for weeks.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Propagation:&lt;/strong&gt; agents delegate to sub-agents and trade with other companies' agents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Adversarial autonomy:&lt;/strong&gt; attacker agents probe yours around the clock.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Physical consequence:&lt;/strong&gt; agents reach plant equipment, grids, vehicles or clinical systems, and a data incident becomes a safety incident.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Most enterprises today are on the first two rungs. A rogue agent doesn't need to be hacked to do harm. And when it &lt;em&gt;is&lt;/em&gt; hacked, the attacker inherits everything it's allowed to do.&lt;/p&gt;




&lt;h2&gt;
  
  
  The census nobody can take
&lt;/h2&gt;

&lt;p&gt;Here's a simple test. Could you tell an examiner today how many agents your company runs, and who owns each one? Most enterprises can't. Industry projections suggest an average Fortune 500 company could be running well over a hundred thousand agents by 2028. At that scale, an agent nobody owns isn't an edge case. It's the default.&lt;/p&gt;

&lt;p&gt;Agents enter the enterprise through four doors:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Prebuilt products&lt;/strong&gt; (SaaS copilots and vendor agents)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No-code builders&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Developer platforms&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Custom-trained models&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Then there's the fifth door nobody opened on purpose: &lt;strong&gt;shadow agents&lt;/strong&gt; on personal accounts and team subscriptions.&lt;/p&gt;

&lt;p&gt;The fix is unglamorous but essential: &lt;strong&gt;treat agents the way HR treats people.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;No credential before a registry entry with a named owner and a declared purpose.&lt;/li&gt;
&lt;li&gt;Reviews on a schedule.&lt;/li&gt;
&lt;li&gt;Dormant agents flagged.&lt;/li&gt;
&lt;li&gt;Same-day off-boarding when the job is done.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And keep discovering, continuously. The agents you don't know about are the ones your runtime controls will never see.&lt;/p&gt;




&lt;h2&gt;
  
  
  What a controlled agent estate looks like
&lt;/h2&gt;

&lt;p&gt;Everything I recommend rests on three principles:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Intelligence proposes, and an independent authority decides.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Protect outcomes, not just individual actions.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Never let an agent's authority grow faster than your ability to stop it and recover.&lt;/strong&gt; Then check all of that continuously, not once at go-live.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Two dials, not one: agency vs. autonomy
&lt;/h3&gt;

&lt;p&gt;Most arguments about "how autonomous should this agent be?" go in circles because they mix up two separate settings:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Agency&lt;/strong&gt; is who decides the &lt;em&gt;steps&lt;/em&gt;: a developer at build time, or the model at runtime.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Autonomy&lt;/strong&gt; is who approves the &lt;em&gt;action&lt;/em&gt;: a person, or nobody.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Where an agent sits on these two dials decides which controls it needs. This framing settles a lot of debates quickly:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;If the steps can be written down, write them down. Give an agent only as much freedom to plan as the task genuinely needs.&lt;/li&gt;
&lt;li&gt;Any agent that reads content from customers, suppliers or the open internet should follow fixed steps.&lt;/li&gt;
&lt;li&gt;Autonomy should be earned one class of action at a time, on evidence, and taken back the moment the evidence turns.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;One caution about human approval: it's a speed bump, not a wall. When someone approves nearly every request within seconds, that isn't oversight. Measure approval rates and response times the way you'd measure any other control.&lt;/p&gt;

&lt;h3&gt;
  
  
  The model proposes, the gateway decides
&lt;/h3&gt;

&lt;p&gt;The core architectural move is simple to say and harder to do: &lt;strong&gt;demote the model from executor to proposer, and put a deterministic action gateway between every proposal and the real world.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Think of it as six layers, plus a control plane that keeps working when the agent platform doesn't. That last part is November's lesson. Audit, revocation and the kill switch have to keep working when the agent platform, the cloud region or the identity provider fails.&lt;/p&gt;

&lt;p&gt;Design rules I ask every CTO to enforce in architecture reviews:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;No agent holds a long-lived secret or borrows a human's session.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No tool accepts free-form SQL or shell commands where a typed business operation would do.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A child agent never gets more authority than its parent.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every consequential action can be traced, in a single query, to a mandate, a policy version and a named human.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Two details separate a real control plane from a dashboard:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Approvals bind to a fingerprint.&lt;/strong&gt; When a human approves a payment, they approve a fingerprint of the exact payee, amount and destination, so any later change voids the approval.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;The kill switch revokes authority instead of closing a chat window.&lt;/strong&gt; It revokes tokens, gateway access, queued work and network egress, in that order.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Limits also have to be &lt;strong&gt;cumulative&lt;/strong&gt;. A $500 per-call cap won't stop a hundred refunds of $499.&lt;/p&gt;

&lt;h3&gt;
  
  
  Three layers, and the new one is where the gaps are
&lt;/h3&gt;

&lt;p&gt;The good news is that you don't need a brand-new security program. Most of what protects an agent already exists: workload identity, cloud posture, data security, code scanning. A second layer arrived with chatbots. The third layer, built for software that &lt;em&gt;takes actions&lt;/em&gt;, is new, and that's where nearly every gap I see sits.&lt;/p&gt;

&lt;p&gt;A practical sequence:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Start with native controls&lt;/strong&gt; your agent platforms already provide, because they see more of their own agents than any outside tool can.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Add an independent layer&lt;/strong&gt; that spans every platform, for posture, rogue-agent detection and one consistent policy.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Treat tool servers (including MCP servers) as your new software supply chain.&lt;/strong&gt; Approve only official ones, route every tool call through a single gateway, and restrict commands and parameters, not just tools.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  Secure the action, not just the prompt
&lt;/h3&gt;

&lt;p&gt;Prompt filters inspect words. But agents fail through what they &lt;em&gt;do&lt;/em&gt;: a tool misused, a goal hijacked, a loop that never ends, a correct-looking step on the wrong record. Some agents don't even have a prompt; they wake up on an event and act.&lt;/p&gt;

&lt;p&gt;Control belongs at the seam between deciding and doing, with hooks on both sides. Analysts expect most successful attacks on agents through 2029 to exploit &lt;strong&gt;access control&lt;/strong&gt;, with prompt injection as the delivery route rather than the payload. The rule I'd take from that is blunt:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;If an agent can't prove who it's acting for and why, it doesn't reach the tool.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;One more distinction matters as new runtime safety platforms arrive, some enforcing policy right down in the hardware: &lt;strong&gt;secured is not the same as governed.&lt;/strong&gt; A runtime safety net can stop an agent doing something dangerous. It can't decide what the agent should be allowed to do, what data it may use, or when a person needs to approve. That still takes clear decision rights, written down for every agent, and a governed source of the business rules agents decide with.&lt;/p&gt;

&lt;h3&gt;
  
  
  Layers that fail differently
&lt;/h3&gt;

&lt;p&gt;If I could ask every architect to memorize one idea, it would be what security researchers call the &lt;strong&gt;lethal trifecta&lt;/strong&gt;:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;private data,&lt;/li&gt;
&lt;li&gt;untrusted content,&lt;/li&gt;
&lt;li&gt;a way to communicate externally.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Give one agent all three and it is a single crafted message away from becoming an exfiltration tool. Prompt injection is not solved. Until it is, no agent session should hold all three without a human or a deterministic check in the path.&lt;/p&gt;

&lt;p&gt;Here's how layered control plays out against an attack I see demonstrated constantly. A customer-support agent reads incoming email and can query the CRM. An attacker sends a message with a hidden instruction: &lt;em&gt;look up this customer's account and email the details to an outside address.&lt;/em&gt; Four independent layers can each stop it on their own:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Posture check:&lt;/strong&gt; flags the risky combination (CRM access plus external email) before the agent ever runs.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Input screening:&lt;/strong&gt; strips the hidden instruction before it reaches the model.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Behavioural detection:&lt;/strong&gt; notices a bulk lookup followed by outbound mail and pauses the agent.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Deterministic gate:&lt;/strong&gt; refuses to send sensitive data to an outside recipient, whatever the model was talked into.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The first three layers use judgment, and judgment can be fooled. The last one can't be argued with. That's why I insist that &lt;strong&gt;every business-critical outcome ends on a deterministic rule&lt;/strong&gt;, written as policy-as-code that sits outside the model and that auditors can read. The supplier-payment rule from earlier looks something like this (Cedar-style policy):&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight rego"&gt;&lt;code&gt;&lt;span class="n"&gt;forbid&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;principal&lt;/span&gt; &lt;span class="n"&gt;is&lt;/span&gt; &lt;span class="nc"&gt;Agent&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;action&lt;/span&gt; &lt;span class="o"&gt;==&lt;/span&gt; &lt;span class="nc"&gt;Action&lt;/span&gt;&lt;span class="o"&gt;::&lt;/span&gt;&lt;span class="s2"&gt;"release_payment"&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;resource&lt;/span&gt; &lt;span class="n"&gt;is&lt;/span&gt; &lt;span class="nc"&gt;Payment&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;span class="n"&gt;when&lt;/span&gt; &lt;span class="p"&gt;{&lt;/span&gt;
  &lt;span class="n"&gt;resource&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;payee&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;bank_account_changed_days&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&lt;/span&gt; &lt;span class="mi"&gt;30&lt;/span&gt; &lt;span class="o"&gt;&amp;amp;&amp;amp;&lt;/span&gt;
  &lt;span class="o"&gt;!&lt;/span&gt;&lt;span class="n"&gt;resource&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;payee&lt;/span&gt;&lt;span class="p"&gt;.&lt;/span&gt;&lt;span class="n"&gt;callback_verified&lt;/span&gt;
&lt;span class="p"&gt;}&lt;/span&gt;&lt;span class="p"&gt;;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;It's a few lines. It holds no matter which agent or model is involved, and it can be versioned, tested and evidenced like any other control.&lt;/p&gt;




&lt;h2&gt;
  
  
  Continuous monitoring: control is never a one-time approval
&lt;/h2&gt;

&lt;p&gt;The agent that passed review last quarter is not the agent running today. Models get updated, prompts and tools change, permissions creep, data drifts and attackers adapt. Approval at go-live is a snapshot. Assurance has to be a live feed.&lt;/p&gt;

&lt;p&gt;Watch five things all the time:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Signal&lt;/th&gt;
&lt;th&gt;What to watch&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Behaviour&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;What each agent did against what it was asked to do&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Authority&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Permissions granted against permissions used; any change to instructions or policy&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Outcomes&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The business-state rules themselves&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Economics&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Cost per task and runaway loops&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Controls&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;The controls themselves, proved by drills rather than assumed&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Monitoring only counts as a control if it passes three tests:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Independent:&lt;/strong&gt; it keeps watching when the agent platform fails.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Able to act:&lt;/strong&gt; it throttles, pauses or revokes within defined limits before it pages a human.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Feeds back:&lt;/strong&gt; every finding tightens a policy, retires an agent or changes how much autonomy an action has earned.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;As agent counts outgrow human review, much of this watching will move to independent &lt;strong&gt;guardian agents&lt;/strong&gt;. These should be deterministic where they decide, and model-based only where they advise.&lt;/p&gt;

&lt;h3&gt;
  
  
  The one new metric: mean time to provenance
&lt;/h3&gt;

&lt;p&gt;If you track one new metric next year, make it &lt;strong&gt;mean time to provenance (MTTP)&lt;/strong&gt;. That is how long it takes to reconstruct, for any disputed transaction, the full chain:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;the person who started it,&lt;/li&gt;
&lt;li&gt;the agent and the run,&lt;/li&gt;
&lt;li&gt;the mandate,&lt;/li&gt;
&lt;li&gt;the inputs,&lt;/li&gt;
&lt;li&gt;the policy version,&lt;/li&gt;
&lt;li&gt;the approval,&lt;/li&gt;
&lt;li&gt;the receipt.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;November's public root causes took one to three days to name. For consequential agent actions, the target should be &lt;strong&gt;under an hour&lt;/strong&gt;.&lt;/p&gt;




&lt;h2&gt;
  
  
  In regulated industries, a rogue agent becomes a finding
&lt;/h2&gt;

&lt;p&gt;In a bank, an insurer or a hospital, the question after an incident is not whether an agent misbehaved. It's whether you can &lt;strong&gt;prove what it was allowed to do&lt;/strong&gt;. Regulated firms will be judged on evidence, not intent.&lt;/p&gt;

&lt;p&gt;The rulebook is in motion, which is exactly why this matters now:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;US banking:&lt;/strong&gt; in April 2026 the US banking agencies replaced their 2011 model-risk guidance with &lt;strong&gt;SR 26-2&lt;/strong&gt;. They confirmed that generative and agentic AI sit outside its scope while a successor approach is worked out. Don't read that as a free pass. Until new rules arrive, examiners will lean on what already applies: operational resilience, third-party risk, and internal controls over financial reporting.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Europe:&lt;/strong&gt; &lt;strong&gt;DORA&lt;/strong&gt; is already live, and the &lt;strong&gt;EU AI Act's&lt;/strong&gt; high-risk obligations begin in December 2027.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Insurance:&lt;/strong&gt; since January 2026, standard commercial liability forms have offered generative-AI exclusions. It's worth asking your broker this quarter whether an agent-caused loss is actually covered.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Examiners will ask for one unbroken chain, from owner to receipt. What they'll ask, by sector:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Banking:&lt;/strong&gt; Show me every agent that can move money, its limits and who approved them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Insurance:&lt;/strong&gt; Prove no adverse decision reached a customer without accountable human review.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Healthcare and life sciences:&lt;/strong&gt; Show me the validated state of the agent and an audit trail for every record it changed.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Energy and utilities:&lt;/strong&gt; Can any agent reach operational technology, directly or through a tool?&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Government:&lt;/strong&gt; Does every agent stay inside the authorization boundary?&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  What control is worth: the business case for agent governance
&lt;/h2&gt;

&lt;p&gt;I'm often asked to justify control spending, so here's the shape of the business case. Take a hypothetical mid-size bank running agents across vendor management, payables, treasury and payment exceptions. On planning assumptions, four scenarios add up to about &lt;strong&gt;$1.16M of expected loss a year&lt;/strong&gt; without independent controls:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a fraudulent payment to a changed bank account,&lt;/li&gt;
&lt;li&gt;a duplicate payment run,&lt;/li&gt;
&lt;li&gt;customer data over-exposure,&lt;/li&gt;
&lt;li&gt;a one-day agent-induced outage.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now add an authority plane with business-state rules, cumulative limits, an evidence chain and quarterly drills. It costs an assumed &lt;strong&gt;$450K a year&lt;/strong&gt; and cuts each probability by roughly &lt;strong&gt;70%&lt;/strong&gt;. That leaves a net benefit of about &lt;strong&gt;$360K a year&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;But the number boards, examiners and underwriters will ask for first isn't expected loss. It's &lt;strong&gt;maximum credible loss&lt;/strong&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Without cumulative limits&lt;/strong&gt;, one bad day's fraud exposure is bounded only by the size of the payment run.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;With the 30-day bank-change rule and counterparty caps&lt;/strong&gt;, it's bounded by the verification queue.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;Control isn't the tax on agentic AI. It's what lets pilots become production.&lt;/strong&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Manufacturing: where a rogue agent stops a line
&lt;/h2&gt;

&lt;p&gt;Manufacturing is where this turns physical. A bad answer in the back office costs money. A bad action near a production line costs output, quality and sometimes safety. And most manufacturers are more regulated than they think, from medical devices and pharma to aerospace, automotive, food and defence.&lt;/p&gt;

&lt;p&gt;The rule is one plant engineers already live by: &lt;strong&gt;the closer a system is to the machine, the less an agent may do.&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Enterprise layer (ERP, planning, procurement):&lt;/strong&gt; agents act, within mandates.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Operations layer (MES, quality, maintenance):&lt;/strong&gt; agents may propose; qualified people approve.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Control and safety layer (PLC, DCS, SCADA, SIS):&lt;/strong&gt; agents never touch these systems.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The realistic failures aren't science fiction:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a planning agent that trims safety stock to hit a working-capital target and stops a line;&lt;/li&gt;
&lt;li&gt;a procurement agent that switches to a cheaper, unqualified supplier;&lt;/li&gt;
&lt;li&gt;an agent that edits a bill of materials outside change control;&lt;/li&gt;
&lt;li&gt;a supplier's agent negotiating with yours beyond anyone's delegated authority.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Before any agent decision touches real operations, &lt;strong&gt;rehearse it in a digital twin&lt;/strong&gt;, so every action is traceable and, wherever possible, reversible.&lt;/p&gt;




&lt;h2&gt;
  
  
  Cloud, on-premises, edge: one authority plane across all of them
&lt;/h2&gt;

&lt;p&gt;Few enterprises will run agents in one place. Most will run them in four, and the rogue agent will slip through whichever one your control plane doesn't reach.&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Where agents run&lt;/th&gt;
&lt;th&gt;Strength&lt;/th&gt;
&lt;th&gt;Watch-out&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;SaaS-embedded&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Fast to adopt&lt;/td&gt;
&lt;td&gt;Your controls are API scopes, admin settings and contract terms that guarantee evidence export and kill-switch access&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Cloud-tenant&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Strong native identity and policy&lt;/td&gt;
&lt;td&gt;The agent, its gateway and its kill switch often share one provider and one region; the stop has to live in a different failure domain&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;On-premises / sovereign&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Data stays inside the boundary&lt;/td&gt;
&lt;td&gt;Legacy systems rarely have APIs that can enforce limits; and on-prem is not automatically safer (one of November's outages was on-prem hardware)&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;&lt;strong&gt;Edge (laptops, plant gateways)&lt;/strong&gt;&lt;/td&gt;
&lt;td&gt;Close to the work&lt;/td&gt;
&lt;td&gt;Edge agents inherit whatever the user or device can do; register them, sandbox them, keep the ones near OT recommendation-only&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;My guidance is &lt;strong&gt;hybrid by design&lt;/strong&gt;: one identity model, one policy language, one evidence format and one kill switch across all four. As smaller models get better, regulated firms will pull their most sensitive agent workloads on-premises and into sovereign environments. That makes portable, vendor-neutral control more important, not less.&lt;/p&gt;




&lt;h2&gt;
  
  
  The risk that's already inside
&lt;/h2&gt;

&lt;p&gt;Most agent risk won't come from attackers. It will come from employees using agents in good faith, and a few in bad faith, on top of access rights that were never designed for a machine that reads everything. An agent turns years of loose permissions and porous departmental walls into instant, searchable exposure.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;In a &lt;strong&gt;bank&lt;/strong&gt;, an analyst's assistant pulls deal material from across an information barrier.&lt;/li&gt;
&lt;li&gt;In a &lt;strong&gt;hospital&lt;/strong&gt;, a scheduling agent surfaces patient records to staff outside the care team.&lt;/li&gt;
&lt;li&gt;In a &lt;strong&gt;plant&lt;/strong&gt;, a maintenance agent shares controlled drawings with a contractor's account.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Anywhere&lt;/strong&gt;, one mis-set permission puts an HR file a single prompt away from anyone with an assistant.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The fixes are mostly discipline:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Clean up oversharing &lt;strong&gt;before&lt;/strong&gt; rollout, not after.&lt;/li&gt;
&lt;li&gt;Bind every agent to its user and its purpose, because "can see it" isn't the same as "may use it here."&lt;/li&gt;
&lt;li&gt;Enforce information barriers inside the agent's retrieval and memory, not just in the applications behind it.&lt;/li&gt;
&lt;li&gt;Fold agents into insider-risk monitoring.&lt;/li&gt;
&lt;li&gt;Build a culture where any employee can stop an agent and report a mistake without fear, and treat those reports as near-misses to learn from.&lt;/li&gt;
&lt;/ol&gt;




&lt;h2&gt;
  
  
  Where the AI security market is heading, and what to ask of it
&lt;/h2&gt;

&lt;p&gt;Agent security has become a land grab for one control point: the moment an agent's decision becomes an action. Investors put roughly &lt;strong&gt;$3.9 billion into AI security in 2026 through August&lt;/strong&gt;, and the big platforms are buying specialists at a record pace. Expect today's features to become tomorrow's defaults.&lt;/p&gt;

&lt;p&gt;The market is sorting into four positions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Identity providers&lt;/strong&gt; know &lt;em&gt;who&lt;/em&gt; an agent is.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Execution platforms&lt;/strong&gt; can &lt;em&gt;stop&lt;/em&gt; an action, mostly inside their own runtime.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Telemetry players&lt;/strong&gt; &lt;em&gt;detect&lt;/em&gt; risk, usually after the fact.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business-aware assurance&lt;/strong&gt; understands &lt;em&gt;what an action means for the business&lt;/em&gt;. This is the least served position, and it's exactly where the payment example and most of this year's incidents point. You can't buy it off the shelf, because it requires process knowledge and deep integration with ERP, finance and operations.&lt;/li&gt;
&lt;/ol&gt;

&lt;h3&gt;
  
  
  A buyer's test for AI agent security vendors
&lt;/h3&gt;

&lt;p&gt;Vendor rankings age in months, so I use a buyer's test instead. Ask every vendor to show you, &lt;strong&gt;in your own environment&lt;/strong&gt;, that their product can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;[ ] block an action before it commits;&lt;/li&gt;
&lt;li&gt;[ ] enforce one cumulative limit across several agents;&lt;/li&gt;
&lt;li&gt;[ ] apply a business rule like the 30-day bank-change check;&lt;/li&gt;
&lt;li&gt;[ ] keep working when its own service is down;&lt;/li&gt;
&lt;li&gt;[ ] revoke an agent along with its sub-agents and queued work;&lt;/li&gt;
&lt;li&gt;[ ] export evidence another system can verify.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Grade each answer as &lt;strong&gt;demonstrated, claimed or untested&lt;/strong&gt;. My rule of thumb: &lt;em&gt;buy the commodity controls, build the business semantics, and never outsource accountability.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  What leaders should do now: a 90-day plan for CAIOs, CTOs, CIOs and CDOs
&lt;/h2&gt;

&lt;p&gt;Controlled autonomy fails when it belongs to everyone, so split it by what each leader already owns:&lt;/p&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;Leader&lt;/th&gt;
&lt;th&gt;Owns&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;CAIO&lt;/strong&gt; (Chief AI Officer)&lt;/td&gt;
&lt;td&gt;How much autonomy the enterprise will accept, and a named owner for every agent&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;CDO&lt;/strong&gt; (Chief Data Officer)&lt;/td&gt;
&lt;td&gt;Which data may never leave a boundary or reach an external model&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;CTO&lt;/strong&gt; (Chief Technology Officer)&lt;/td&gt;
&lt;td&gt;The authority plane as a shared platform, with an off-platform kill switch&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;
&lt;strong&gt;CIO&lt;/strong&gt; (Chief Information Officer)&lt;/td&gt;
&lt;td&gt;Making the ERP and core systems, not the agents, the final enforcers of business rules and segregation of duties&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;

&lt;p&gt;Then give the work a deadline. &lt;strong&gt;By the end of Q1 2027&lt;/strong&gt;, every agent with production write access should have:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a &lt;strong&gt;named owner&lt;/strong&gt;,&lt;/li&gt;
&lt;li&gt;a &lt;strong&gt;scoped mandate&lt;/strong&gt;,&lt;/li&gt;
&lt;li&gt;a &lt;strong&gt;hard limit on harm&lt;/strong&gt;,&lt;/li&gt;
&lt;li&gt;a &lt;strong&gt;revocation path you've actually tested&lt;/strong&gt;, including from outside the agent platform.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Run one &lt;strong&gt;game day&lt;/strong&gt; this quarter: take down your identity provider and your gateway, and watch what your agents do.&lt;/p&gt;

&lt;p&gt;And if you adopt only one board rule, make it this one:&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;No new high-impact autonomous workflow goes live until its owner can show a hard limit on harm, an independent stop that works with the platform down, and a reconstruction of any transaction from mandate to receipt.&lt;/strong&gt;&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  How we're approaching this at Elixir Global
&lt;/h2&gt;

&lt;p&gt;Frameworks and point tools don't wire themselves into ERP, core banking, claims, MES or plant systems. Somebody has to connect what an agent &lt;em&gt;may call&lt;/em&gt; with what that call &lt;em&gt;does to the business&lt;/em&gt;. That fourth position, &lt;strong&gt;business-aware autonomy assurance&lt;/strong&gt;, is the one we've chosen to lead at &lt;a href="https://www.elixirglobal.com" rel="noopener noreferrer"&gt;Elixir Global&lt;/a&gt;. It's the work I lead as Chief AI &amp;amp; Innovation Officer, with teams that have deployed agents and AI governance across federal, energy, oil and gas, manufacturing, life sciences, utilities and consumer goods.&lt;/p&gt;

&lt;p&gt;For us, the next frontier of enterprise AI isn't deploying more agents. It's engineering the conditions under which an enterprise can safely trust them with consequential work. Three convictions guide us:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Business semantics come first.&lt;/strong&gt; The rule that stops the payment example belongs in the ERP, where it holds no matter which agent or model touches the transaction.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Enforcement stays independent.&lt;/strong&gt; Agents propose, and the client's own identity, gateway, audit and kill switch decide.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assurance is continuous.&lt;/strong&gt; We design governance in before agents get production credentials, and use the same approach to close the gaps where agents are already live.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;The same philosophy shapes &lt;strong&gt;AgentVault&lt;/strong&gt;, our library of enterprise agents for finance close, payables and receivables, procurement and supply chain. Those are the very workflows in the payment example. Every AgentVault agent is designed to arrive governed:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;a declared purpose and owner,&lt;/li&gt;
&lt;li&gt;a scoped mandate,&lt;/li&gt;
&lt;li&gt;guardrails aligned to the client's compliance regime,&lt;/li&gt;
&lt;li&gt;operation inside the client's own environment, whether that's cloud, on-premises or a sovereign enclave.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;And because the agents stay portable across models and frameworks, clients can adopt better models without rebuilding their controls.&lt;/p&gt;




&lt;h2&gt;
  
  
  The next architecture problem isn't intelligence. It's control.
&lt;/h2&gt;

&lt;p&gt;The threat will keep moving under whatever we build. The work comes in three horizons:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Now: visibility.&lt;/strong&gt; Find every agent, give each one an identity, lock down tool servers, strip excess permissions.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Next two to three years: scaled supervision.&lt;/strong&gt; Supervision has to scale beyond what humans can review.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;After that: physical AI.&lt;/strong&gt; World models and physical AI will bring agents to machines, robots and plant equipment, where mistakes stop being reversible.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;We're approaching the moment when enterprises delegate more decisions to machines than people can individually review. That shift could unlock extraordinary productivity in banking, insurance, healthcare, energy, manufacturing and government. It also raises a question our architectures were never built to answer: &lt;em&gt;who is accountable when autonomous systems make individually authorized decisions that together produce an unacceptable outcome?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;The answer isn't another prompt, another dashboard, or an AI supervisor watching an AI worker. It's an independent authority plane, business rules enforced where the business actually runs, continuous monitoring, evidence that stands up to examiners, and the ability to recover from failures that move at machine speed.&lt;/p&gt;

&lt;p&gt;Here's the part I find genuinely exciting. The enterprises that build this early won't delegate &lt;em&gt;less&lt;/em&gt; to AI. They'll be able to delegate &lt;em&gt;more&lt;/em&gt;, because they can prove it's safe. &lt;strong&gt;The advantage in the next decade won't go to whoever automates the most decisions. It will go to whoever can safely afford the most autonomy.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;The next agent incident may look completely routine in the logs: a valid identity, an approved tool, a successful transaction. So before your organization gives another agent production write access, ask three questions:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;What outcome can it never cause?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Who can stop it when the platform is down?&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What record will prove both?&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you can't answer all three with evidence, that's your roadmap for 2027.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Fellow CAIOs, CTOs, CIOs and CDOs: which of those three questions is hardest to answer in your organization today? Tell me in the comments.&lt;/em&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  Glossary
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Rogue AI agent:&lt;/strong&gt; an autonomous AI agent that causes harm while holding valid credentials, whether manipulated or through the combined effect of several authorized agents.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Autonomy debt:&lt;/strong&gt; the gap between the authority an enterprise delegates to AI agents and the control it can prove over them.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Action gateway:&lt;/strong&gt; a deterministic enforcement point between an agent's proposed action and the system it would change.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Business-state rule:&lt;/strong&gt; a policy that evaluates the resulting business outcome (for example, "no payment to a bank account changed in the last 30 days without call-back verification"), not just whether a single call was permitted.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Policy-as-code:&lt;/strong&gt; business and security rules written in a machine-enforceable, versioned language (such as Cedar or OPA/Rego) that sits outside the model.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Lethal trifecta:&lt;/strong&gt; private data + untrusted content + external communication in one agent session.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Mean time to provenance (MTTP):&lt;/strong&gt; the time needed to reconstruct the full chain behind a disputed agent action, from initiator to receipt.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Guardian agent:&lt;/strong&gt; an independent agent that monitors other agents; deterministic where it decides, model-based only where it advises.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Frequently asked questions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;What is a rogue AI agent?&lt;/strong&gt;&lt;br&gt;
A rogue AI agent is an autonomous AI agent that causes harm while using valid enterprise credentials. It can be manipulated by malicious content or tools. More often, it is one of several authorized agents whose individually correct actions combine into an outcome nobody approved, such as a fraudulent payment.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Why can't traditional security tools stop rogue AI agents?&lt;/strong&gt;&lt;br&gt;
Most security tools check whether a single identity or a single call is permitted. Rogue-agent incidents usually involve valid identities and permitted calls. Stopping them requires business-state rules that evaluate the resulting outcome, enforced by an independent action gateway outside the model.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What is the best architecture for governing agentic AI?&lt;/strong&gt;&lt;br&gt;
The model proposes and an independent action gateway decides. Business-state rules are enforced as policy-as-code. Approvals bind to a fingerprint of the exact action. Limits are cumulative across agents. A kill switch revokes tokens, gateway access, queued work and egress from outside the agent platform.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What should a CAIO or CTO do in the next 90 days?&lt;/strong&gt;&lt;br&gt;
Create an agent registry with a named owner for every agent. Give every agent with production write access a scoped mandate, a hard limit on harm and a tested revocation path. Run a game day that takes down the identity provider and gateway. Start measuring mean time to provenance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Which industries are most exposed to rogue AI agents?&lt;/strong&gt;&lt;br&gt;
Banks, insurers, manufacturers, utilities and government agencies that are adopting AI agents quickly on top of legacy core systems such as core banking, ERP, MES and SCADA.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How do regulations like SR 26-2, DORA and the EU AI Act affect AI agents?&lt;/strong&gt;&lt;br&gt;
SR 26-2 replaced US model-risk guidance in April 2026 but leaves generative and agentic AI outside its scope for now, so examiners rely on operational-resilience, third-party-risk and internal-control expectations. DORA already applies in Europe, and the EU AI Act's high-risk obligations begin in December 2027. In every case, firms will be judged on evidence of control.&lt;/p&gt;




&lt;h2&gt;
  
  
  About the author
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fssey9m5o4o9e1l3gww2m.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fssey9m5o4o9e1l3gww2m.jpg" alt="Ganesh Raju, Chief AI &amp;amp; Innovation Officer and CTO, Elixir Global" width="800" height="534"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Ganesh Raju&lt;/strong&gt; is the Chief AI &amp;amp; Innovation Officer (CAIO) and CTO at &lt;strong&gt;&lt;a href="https://www.elixirglobal.com" rel="noopener noreferrer"&gt;Elixir Global&lt;/a&gt;&lt;/strong&gt;, an AI-first enterprise consulting firm headquartered in Atlanta with offices in Houston, Dubai, Bengaluru and Singapore. He leads enterprise AI strategy and owns the company's AI product portfolio, including &lt;strong&gt;AgentVault&lt;/strong&gt;, Elixir's library of production-ready, governed AI agents for SAP and enterprise operations. He helps global enterprises in energy, oil and gas, manufacturing, healthcare and life sciences, financial services and the public sector move agentic AI from pilots into governed, auditable production.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Data, machine learning and AI:&lt;/strong&gt; Ganesh has more than 15 years of experience in artificial intelligence, machine learning and data engineering. As Head of Big Data, Data Science &amp;amp; AI at Linaro, he led Arm enablement of the open-source big data and data science ecosystem. He served as an ODPi PMC member and TSC lead and as a Linux Foundation TSC member, and he led the Apache Bigtop community. He has contributed to open-source projects including TensorFlow, Apache Spark and Hadoop, and holds certifications from Cloudera, Cassandra and Anthropic (Claude).&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Author and speaker:&lt;/strong&gt; He is the author of &lt;em&gt;AI Blockchain Design and Deployment&lt;/em&gt; (BPB Publishing). He has published technical papers and speaks at AI and industry conferences on agentic AI, AI governance, the autonomous enterprise, digital twins and physical AI.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Entrepreneur, investor and advisor:&lt;/strong&gt; Ganesh is the founder and CEO of &lt;strong&gt;Akshaya.io&lt;/strong&gt; (founded 2019) and the founder of &lt;strong&gt;RapidEVChargE&lt;/strong&gt;, an EV-charging infrastructure company serving India and the Americas. He is an investor and an advisor to &lt;strong&gt;Canon&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Community:&lt;/strong&gt; He is a former Vice Chair of &lt;strong&gt;IEEE Houston&lt;/strong&gt; and a member of Cohort 21 of the &lt;strong&gt;Wharton Executive Education Chief Technology Officer program&lt;/strong&gt;. He has lived in Houston, Texas, for 29 years.&lt;/p&gt;

&lt;p&gt;Connect with Ganesh on &lt;a href="https://www.linkedin.com/in/ganeshraju07" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt; and &lt;a href="https://github.com/ganeshraju" rel="noopener noreferrer"&gt;GitHub&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;This article expands on a version first published on &lt;a href="https://www.linkedin.com/pulse/rogue-agent-have-valid-credentials-ganesh-raju-wg51c/" rel="noopener noreferrer"&gt;LinkedIn&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  AgenticAI #AIGovernance #RogueAgents #AISecurity #EnterpriseAI #CAIO #CTO #AIAgents #CyberSecurity #RiskManagement #DigitalTwin #SAP #ElixirGlobal
&lt;/h1&gt;

</description>
      <category>architecture</category>
    </item>
  </channel>
</rss>
