AI Delivery bulletin · Issue 002 · September 2026

TechnicallySpeaking

Learn AI deeply. Question it honestly.
Build it for people.

9 minutes to read3 games for fun

Since We Last Spoke

What's materially changed?


Agents are getting their own badges

Sept. 15, 2026 · NIST and CISA

What happened

Sept. 15: NIST and CISA finalized guidance on protecting tokens, the digital passes that let people, services and AI agents into systems without a password each time. The report, NIST IR 8587, shows how to keep tokens from being forged, stolen or misused, and it explicitly covers AI agents.

Sept. 29: An executive order replaced "artificial intelligence" with "super intelligence" in federal language. NIST renamed its AI center CAISSI but left its frameworks and guidance unchanged.

Why you should care

Every AI agent that reaches a company system carries a token. Stolen tokens caused last issue's breach of more than 700 Salesforce environments. The guidance is voluntary for private companies, but expect cloud vendors and auditors to measure against it. The meta-harness in this issue's Deep End raises the stakes: it often brokers credentials for every agent beneath it.

What it confirms

Washington now treats AI agents as identities, not app features. IR 8587 applies the same token rules to agents as to people and services.

What's still uncertain

The guidance protects the token, not what each agent may do. NIST says that guidance is coming. What NIST calls signed intent, proof that a person authorized an agent's action, also needs more standards work. Most companies aren't ready either: 78% have no documented policy for creating or removing AI identities.

You didn't hear it from me…

  • To your identity team, ask whether an agent can get its own identity, separate from the person who builds it. If agents borrow their builder's login, you can't tell their actions apart, and you can't shut one off without locking out a person.
  • To your platform team, ask how long agent credentials live. Hours are a choice. Days or weeks give a stolen credential time to do damage.
  • To any vendor selling you agents, ask them to show the delegation chain for one action. You should be able to trace who asked, which agent acted and what it was allowed to do.

Read more: NIST's announcement and the Cloud Security Alliance on what it means for AI agents.

What leaders are asking…

"Do we know every AI agent we run and what each one can reach?"

Buzzword Polygraph

Real term, or did we make it up?


The three games in this issue are just for fun. Guess wildly and see how you do.

Five terms. Which are real?

signed intent Real, and unfinished. Proof of what a person actually asked the agent to do. NIST says it still needs standards work.
credential osmosis Made up, though keys drifting from config files into markdown and logs is exactly what NIST flagged.
attention sink Real, and it sounds like plumbing. Language models dump spare attention onto the first few tokens of a conversation, even meaningless ones. Keep those tokens around and long sessions stay stable; drop them and output degrades.
prompt escrow Made up, though holding a request in trust until someone approves it is close to what signed intent is trying to solve.
jagged frontier Real. Coined in a 2023 Harvard and BCG study: AI is excellent at some tasks and fails at others that look just as hard. It is why you match the model to the step.
0 of 5 answered

Deep End of the Pool

This month: Meta-Harnesses


Why meta-harnesses are becoming the next competitive advantage

Last issue covered how MCP standardized the way agents reach systems. This issue goes one layer up, to how agents are defined and governed apart from the harness that runs them. As always, the goal is enough context to know when this is useful, when to invest and when to push back on the hype.

For two years, the question in AI was which model is most capable. September made that question look dated. At least nine labs shipped new models in a single month (see Tool Directory's September roundup). And the price tags stopped lining up with the results. On the Artificial Analysis Intelligence Index, an independent composite of capability tests, Claude Opus 5.5 scored 58 at $20 per million output tokens, while Claude Fable 5.1 and OpenAI's GPT-6 Astra both scored 53 at $50. Claude Sonnet 5.5 scored 56 at $10 (scores compiled by AIToolsReview).

Paying more didn't buy more capability A scatter chart of six models released in September, with what each costs to use per million output tokens on the horizontal axis and how capable it is on the vertical axis. Anthropic models are red and OpenAI models are blue. Claude Opus 5.5 scored 58 at 20 dollars. Claude Sonnet 5.5 scored 56 at 10 dollars. Claude Fable 5.1 and GPT-6 Astra both scored 53 at 50 dollars. GPT-6.1 Sol scored 52 at 10 dollars, and GPT-6 Sol scored 48 at 10 dollars. The two most expensive models were not the two most capable. SEPTEMBER'S MODELS, SIDE BY SIDE Paying more didn't buy more Anthropic OpenAI HOW CAPABLE IT IS (INDEX SCORE) 60 55 50 45 $0 $10 $20 $30 $40 $50 WHAT IT COSTS TO USE ($ PER 1M OUTPUT TOKENS) BEST VALUE: MORE CAPABLE, LESS COST Opus 5.5 Sonnet 5.5 GPT-6 Astra Fable 5.1 both 53 at $50 GPT-6.1 Sol GPT-6 Sol
Higher and further left means more capability per dollar. Scores: Artificial Analysis Intelligence Index v4.3, Sept. 30. Prices: list rates per 1M output tokens, not cost per task.

When the best model can change every few weeks, the advantage goes to whoever can switch, combine and govern models fastest. That happens in a new architectural layer: the meta-harness.

In theory, switching should be easy: change the model and carry on. In practice, the model is the smallest part of what delivery teams build. Most of the work lives in the layer around it, called the harness: the loop that calls the model, the tools it can run, the files it can touch, the memory it keeps between steps and the rules for when it stops. Claude Code, Codex and Cursor are all harnesses.

A meta-harness is a layer above your harnesses that wraps each one in a common interface, so agents, policies and tools stay portable across them.

Databricks' answer is Omnigent, a meta-harness that coordinates agents built with Claude Code, OpenAI's Codex and custom frameworks. Rather than commit to one vendor's ecosystem, teams can pick the best agent for each job and keep their context, tools and governance shared. Because the code is open source, teams can inspect it, run it on their own infrastructure and keep using it wherever Databricks takes the product.

One layer, many harnesses, any model An open source meta-harness, for example Databricks Omnigent, sits at the top. Every agent shares its context, tools and governance, and budgets, permissions and sandboxes are set once there. Below it are four harnesses: Claude Code, Codex, Cursor and your own agent built on an SDK. Each calls a model, such as Claude Opus 5.5, Claude Sonnet 5.5 or GPT-6 Astra, or next month's leader. Either layer can be swapped without a rebuild. Without a meta-harness, every harness needs its own place to set rules. With one, there is a single place. ONE LAYER, MANY HARNESSES, ANY MODEL META-HARNESS OPEN SOURCE Example: Databricks Omnigent. Shared by every agent: CONTEXT TOOLS GOVERNANCE Budgets, permissions and sandboxes, set once. Claude Code harness Codex harness Cursor harness Your agent built on an SDK MODELS Claude Opus 5.5, Claude Sonnet 5.5, GPT-6 Astra or next month's leader. SWAP EITHER LAYER WITHOUT A REBUILD Without it: a separate place to set rules for every harness. With it: one.
Change what runs underneath. The rules stay put.

What a meta-harness holds

The agent definition: one file that describes the agent, its tools and its instructions, written once and portable across harnesses.
Policies: rules for what the agent may do, enforced outside the model so no prompt can rewrite them.
Cost controls: spending tracked per session, with limits that pause the agent for approval.
Sessions: live work that teammates can watch, review and steer together.

What that gets you

A meta-harness turns slow, expensive decisions into fast, cheap ones:

An organization that adopts the best model in days, under controls it already trusts, will outrun one that needs a quarter to rebuild.

The cost savings can also be significant. In UC Berkeley's RouteLLM research, intelligent model routing maintained 95% of GPT-4's quality on one benchmark while reducing costs by more than 85%. Not every task needs the most expensive model, and choosing the right one can make a meaningful difference at enterprise scale.

Route the routine, save 85 percent An illustrative workload of ten million output tokens a month. Using one premium model for everything, at fifty dollars per million output tokens, costs five hundred dollars a month. Sending the hardest 14 percent of work to the premium model, seventy dollars, and the routine 86 percent to a low-cost model at fifty cents per million, four dollars and thirty cents, costs about seventy-four dollars a month, 85 percent less. SAME WORK, TWO WAYS TO PAY FOR IT Route the routine, save 85% One premium model for everything Every token at the premium price 10M tokens on a premium model at $50 per 1M $500/mo The right model for each task Same 10 million tokens, two price tiers $74/mo 85% LESS 14% premium ($50 per 1M): hard steps $70 86% low-cost ($0.50 per 1M): routine work $4.30
An illustrative example at list prices. The 14% split comes from UC Berkeley's RouteLLM study, where routing kept 95% of the premium model's quality.

At 1 billion tokens a month*

$511,000

saved a year by routing

Premium $600,000 Routed $89,000

*A heavy-adopter scenario. The median large non-tech company uses 50 million to 500 million tokens a month, while a quarter of tech companies top 50 billion, per a Bloomberg Intelligence survey.

The cost of a new layer

Putting every agent behind one layer simplifies control, but it also concentrates risk. Weigh these before adopting one:

The category is also young: Omnigent is in alpha as open source and in beta as a managed Databricks service. None of this is a reason to wait. It is a reason to treat the meta-harness like any other critical system, with redundancy, review for every policy change and only the credentials it needs.

Four layers, top to bottom Four stacked layers. At the top, an optional meta-harness, for example Databricks Omnigent, composes harnesses and enforces budgets and permissions. Next, harnesses such as Claude Code, Codex, Cursor and your own agent built on an SDK, which can be swapped freely. Below them, platform plumbing such as Agent Bricks, AWS AgentCore and Microsoft Foundry provides compute, memory, identity, sandboxes and traces. At the bottom, governed data and tools, including catalogs, permissions and MCP servers, which is where access rules should live. FOUR LAYERS, TOP TO BOTTOM META-HARNESS (OPTIONAL) Composes harnesses, enforces budgets and permissions. Example: Databricks Omnigent HARNESSES SWAP FREELY Claude Code Codex Cursor Your SDK agent PLATFORM PLUMBING Compute, memory, identity, sandboxes, traces. Agent Bricks, AWS AgentCore, Microsoft Foundry GOVERNED DATA AND TOOLS Catalogs, permissions and MCP servers. Where the access rules should live.
Set the shared rules at the top. Enforce data access at the bottom.

Two things people get wrong

"A meta-harness replaces our agent frameworks." It does not. LangGraph, Claude Code and your SDK agents keep doing the work; the meta-harness coordinates them from above. If someone pitches it as a rip-and-replace, they are selling something else.

"One control layer means we're governed." Only for the agents that run through it, and only for the rules it can see. The meta-harness can cap spending and gate actions, but deciding who may read which record still belongs at the data layer, in catalog permissions and MCP servers. You need both.

Go Deeper!

Ballpark

Close enough still counts


Four questions from real polls. Guess what share of people said yes. You score for how close you land.

What percent said yes?

Closeness only

What percent of consumers would trust a personal AI agent more than their best friend to make a purchase for them?

Your guess: 50%
74%. Only 9% would let an agent make purchases fully on its own, though. Source: Accenture Consumer Pulse 2026, 25,590 people in 16 countries.

What percent of employees admit they hide how they use AI at work?

Your guess: 50%
57%. Nearly half have also uploaded company information to public AI tools. Source: KPMG and University of Melbourne, Trust in AI, 48,000+ workers in 47 countries (2025).

What percent of consumers want an AI agent that plans a whole trip for them, from airlines to hotels to activities?

Your guess: 50%
71%. Wanting the trip planned is a long way from letting the agent book and pay for it. Source: Accenture Consumer Pulse 2026.

What percent of executives say AI is tearing their company apart?

Your guess: 50%
54%, up from 42% a year earlier. The same executives report AI built in silos, friction between IT and the business, and returns that lag the spending, yet 97% have already deployed AI agents. Source: Writer and Workplace Intelligence enterprise AI survey, 2026.
0 of 4 locked in

Clusters

Sixteen terms, four groups of four


Find the four groups of 4. Four mistakes allowed. Run out and the board reveals itself!

Find the four groups

Four mistakes
Mistakes left