Public ledger
Signal Ledger
The record behind the thesis series: every tracked signal, both of its thresholds, and its latest dated reading.
What this is
This page is the master record behind the thesis series. Seventeen signals are tracked here, each with a definition, a named recurring source, the cadence that source publishes on, two thresholds — one that would confirm it, one that would weaken it — and its latest dated reading. The theses argue; the ledger keeps score.
Signals belong to the ledger, not to any single thesis. A publication updates the signals it brings evidence for and may add new ones; nothing here obliges a publication to appear. The obligation runs the other way and it is dated: the nine staked calls in section 04 are graded on their resolution dates, whether they land or miss.
- 17 Signals tracked, all currently active, across seven clusters Opened by Thesis 01, 17 August 2026; five added by Thesis 02, 18 August 2026; six added by Thesis 03, 24 August 2026
- 9 Staked calls open, each with a fixed grading date 15 November 2026, 30 November 2026, 30 June 2027, 31 December 2027 and 30 June 2028
- 5 Registries behind the ledger: outcome prices, pricing models, agent acquisitions, adjudicated claims, data deals The data-deals registry went live with Thesis 03, 24 August 2026
How this ledger updates
- Publications update what they touch. A thesis or a note updates the subset of signals it has evidence for. Partial updates are the normal case: a signal a publication did not move is not a signal that was ignored.
- The bi-monthly Scorecard covers the rest. Every two months each live signal is re-read and re-scored, and “no change” is a legitimate result that gets written down. First Scorecard: October 2026.
- Staked calls are graded at their resolution dates. This is the only hard obligation in the system. A call is graded in public on its date, including when it misses.
- Retirement is written down. A signal leaves active status only with a dated line of reasoning. Silent deletion is not permitted, because a ledger you can quietly prune is not evidence of anything.
Lifecycle. Active — read at every Scorecard and by any publication with evidence for it. Dormant — retained, but its source has stopped publishing or the question is parked; no score is issued while dormant. Retired — closed with a dated reason, kept visible in the reading history. Resolved — a threshold was crossed and the question is settled; the crossing is recorded with its date.
Provenance. Every reading carries a date, the publication that logged it and a link to its source. Registry rows carry a disclosure column stating how the number is known: published-primary (the vendor's own rate card or pricing page), company-announced, press-reported, or vendor-undisclosed. Where only secondary reporting exists, the row says the price is unverified instead of repeating it as fact. Scores run −2 to +2 and are mine.
The signals
One table per cluster, one row per signal, each showing its latest dated reading. Net score across the seventeen is +1: pricing and infrastructure move with the theses, the consumer-transaction signal does not, bundling moves against the claim that these layers are independently investable, and the authority signal has been re-scored to neutral with its reasoning printed in the row. The six signals in the new supply cluster net zero between them, which is why the whole-ledger figure does not move: the pricing and disclosure signals there point one way, the institutionalisation signals point the other, and nothing in that cluster is yet a trend.
One convention is worth stating before the tables, because a reader who misses it will read half the ledger backwards. Every score runs against that signal's own confirming threshold, not for or against a thesis. R02.5 sits at −1 because no frontier lab has annexed canonical business state — which is exactly what CALL C (Thesis 02) predicts will not happen. A minus there supports the argument; a minus on R01.1 undercuts one. R03.5 and R03.6 work the same way and their rows print the sign note in the cell. The threshold columns say which is which.
Commerce
| Signal | Status | Latest reading | Confirms if | Weakens if | Updated by |
|---|---|---|---|---|---|
| Checkout share of agentic activityShare of observed agentic web activity routed to checkout and payment flows, as a percentage of all agentic route types. Source: HUMAN Security, State of Agentic Traffic — monthly [1] | Active | −1 · 2.34% (2.3% Dec 2025 · 3.16% Apr 2026 · 2.4% May · 2.34% Jun) MEASUREDLogged 17 August 2026 · reading dated 30 June 2026, from the June edition published 6 July 2026; no July edition existed as of 17 August 2026. The April and May figures are secondary readings cross-checked against HUMAN's own June post. | checkout share exceeds 5% of agentic activity by Q2 2027 | still below 3% by Q2 2027 | Thesis 01 |
Pricing
| Signal | Status | Latest reading | Confirms if | Weakens if | Updated by |
|---|---|---|---|---|---|
| Outcome-pricing adoptionShare of surveyed AI builders using outcome-based pricing, cross-checked against published vendor list prices per resolved outcome in the outcome price and pricing model registries. Source: ICONIQ, State of AI — semi-annual, with the registries read quarterly [2] | Active | +1 · 23% of AI builders (2% Q2 2025 → 18% Q4 2025, N=297 → 23% Q2 2026); 37% plan a pricing-model change within a year. Added 18 August 2026: hybrid pricing at 37% of 230+ self-selected business-software and AI companies against 25% twelve months earlier, with AI credits active at 29% and a further 33% planning to introduce them within 6–12 months [3] MEASUREDLogged 17 August 2026, extended 18 August 2026 by Thesis 02 · the ICONIQ reading is dated 31 July 2026 and the monetization-survey reading 13 May 2026, its publication date, fielded April–May 2026. Unit warning that rides with any use: ICONIQ measures the share of AI builders offering outcome-based pricing, the monetization survey measures hybrid pricing across a different self-selected sample. Same direction, different denominators — they must never be blended, and neither measures the share of contracts signed on outcomes or says anything about incumbent seat-based software. Incentive disclosure: the monetization survey is published by a pricing advisory practice, and ICONIQ invests in the software companies it surveys. Score unchanged in direction. | share of AI builders offering outcome-based pricing as their primary model exceeds 30% (CALL 2 bets it stays under 30% through end-2027) | the ICONIQ vendor-adoption series stalls below 25% or reverts toward hybrid or consumption pricing | Thesis 01 · Thesis 02 |
| Price of the shared agent surfaceWhether any tracked vendor publishes a price for the shared multi-user agent surface as a distinct product — per channel, per shared agent, or per multiplayer seat — or whether that surface stays unpriced while the seat persists and consumption meters accumulate beside it. Tracked vendors fixed at first reading: Anthropic, OpenAI, Microsoft, Google, Asana. Deliberately not R01.2: that is a survey of outcome-pricing adoption among AI builders, this is a census of published pricing pages for one named capability, and the two must not be collapsed at a Scorecard. Source: published vendor pricing pages and product documentation — quarterly [4] | Active | +1 · 0 of 5 tracked vendors price the shared agent surface as a distinct product. Anthropic: adding Claude to Slack adds no per-seat charge — channel and thread work draws on an organization-funded usage balance under an admin spend limit with no published per-unit rate, while a direct message bills to the sender's own seat. Asana markets its shared agents as multiplayer by design and publishes no price for them, pricing seats ($10.99 Starter, $24.99 Advanced, per user per month billed annually) with monthly AI credit allowances beneath. Microsoft states that use of agents published to Microsoft 365 Copilot is included in the licence, at $18.00 per user per month paid yearly. Google bundles Gemini across Workspace tiers and lists an expanded-access add-on with no price on the pricing page. OpenAI meters its workspace agents in credits with no published per-unit rate. On 5 August 2026 a third party outside the tracked set, Cloudflare, open-sourced its own company agent platform with neither a licence name nor a price anywhere in the announcement — recorded without moving the score, because it is not one of the five tracked vendors MEASUREDLogged 18 August 2026 · reading dated 18 August 2026, a pricing-page census across the five tracked vendors on that date. Every published price is the vendor's own claim; the absence of a shared-surface price is measured across the five pages checked, and it is a search over five vendors rather than an exhaustive one — that scope travels with the null. Anthropic and OpenAI list their standard and premium seat ladders at the same published numbers, $20 annual / $25 monthly and $100 annual / $125 monthly; the OpenAI figures are marked author to verify because openai.com returned HTTP 403 to the research workstation, and Google's US-dollar list prices could not be read at all, so the Google entry rests on the bundling structure rather than on a number. Score +1: the confirming condition holds at baseline and has eighteen months to run. | through 31 December 2027 no tracked vendor publishes a distinct price for a shared-agent surface, while at least two add further non-seat meters beside a persisting seat | two or more tracked vendors publish a distinct price for the shared-agent surface as its own product | Thesis 02 |
Margins
| Signal | Status | Latest reading | Confirms if | Weakens if | Updated by |
|---|---|---|---|---|---|
| Vertical-AI gross marginAggregate gross margin on AI products, used as the closest observable proxy for human-exception cost. No public series reports human-exception rates directly — stated as a proxy, not a measurement. Sources: ICONIQ State of AI [2]; Bessemer Venture Partners State of AI — annual to semi-annual [5] | Active | +1 · 45% (2025) → ~53% projected 2026 → 59% projected 2027, N≈300; Bessemer cohorts ~25% (fastest-growing) and ~60% (disciplined), August 2025. Added 18 August 2026 from the January 2026 snapshot: 41% (2024) → 45% (2025) → ~52% projected 2026, N=269, and split by primary differentiator the pure application layer is the lowest of three archetypes at a projected 45% in 2026 against 53% for balanced builders; model inference rises from 20% to 23% of AI product cost while talent falls from 32% to 26% (N=202) MEASUREDLogged 17 August 2026, extended 18 August 2026 by Thesis 02 · the July 2026 edition reading is dated 31 July 2026 and the bi-annual snapshot reading 31 December 2025, the end of its field period. Proxy measure: gross margin stands in for human-exception cost because no public series reports exception rates. The application-layer figure is measured and published by an investor in the application layer, which makes it evidence given against its own interest. Correction recorded: the 23% is a share of cost, not of revenue — secondary write-ups converting it into a per-revenue figure are invalid and the conversion must not be repeated. The ~52% and ~53% projections are two editions of the same forecast, not a measurement change. Score unchanged. | margins keep climbing toward 60%+ | margins flatten below 50%, implying human exceptions are not falling | Thesis 01 · Thesis 02 |
| Non-seat agent revenue at scaleWithin a cohort fixed at first reading and never changed silently — Salesforce, HubSpot, Atlassian, monday.com, Asana, Smartsheet — whether any member discloses agent or non-seat meter revenue as a disaggregated line in its financial statements, and at what share of total revenue. Unaudited management metrics do not count, by construction: two cohort members already publish them, so a looser test would be partly pre-resolved on the day it was minted. Sources: quarterly results, shareholder letters and revenue disaggregation for the named cohort — quarterly [6] | Active | −1 · 0 of 6 cohort members disaggregate a non-seat agent revenue line in their financial statements; the cohort is verified at four of six. Closest: Salesforce discloses Agentforce ARR of $1.2B, up 205% year over year (Q1 FY2027, 27 May 2026), as an unaudited supplemental metric against roughly $44B annualized revenue — about 2.7% — while its statements disaggregate by product family, not by meter. monday.com reports AI-product ARR at 17% of net new ARR (Q2 2026, 10 August 2026), up from 10% a quarter earlier. Atlassian reports agent credit usage growing 20%+ month over month, seats expanding, and no agent revenue line (30 April 2026). HubSpot: no separate line found, secondary sourcing only. Asana and Smartsheet in-window filings not yet opened COMPANY CLAIMLogged 18 August 2026 · reading dated 18 August 2026, a cohort census against disclosures dated 30 April to 10 August 2026. ARR and net-new-ARR shares are management-defined unaudited metrics sitting beside audited statements, and issuers have a direct interest in demonstrating agentic traction. Unit trap recorded in the definition: monday.com's AI-products metric counts seat-priced AI tiers, so it does not evidence a non-seat meter. Counter-evidence on the same axis, deliberately included: Microsoft reported over 30 million paid Microsoft 365 Copilot seats with net seat adds more than doubling quarter over quarter, and described the model as moving beyond per-seat to per-seat-plus-consumption (29 July 2026) — additive, not substitutive. Score −1: the migration of revenue onto non-seat meters is not visible in the cohort's statements, and the seat is being deepened rather than displaced. | at least one cohort member reports a disaggregated non-seat agent revenue line exceeding 10% of total revenue by 31 December 2027 | no cohort member disaggregates such a line at all through 31 December 2027 while seat revenue keeps growing | Thesis 02 |
Authority
| Signal | Status | Latest reading | Confirms if | Weakens if | Updated by |
|---|---|---|---|---|---|
| Authority standardsProgress from concept papers toward a shipped, normative agent-authorization profile with incumbent IAM implementations. Sources: NIST AI Agent Standards Initiative / NCCoE [7]; Agentic AI Foundation (Linux Foundation) MCP releases and IAM vendor GA notes — event-driven [8] | Active | 0 · Standards movement and proprietary movement running in opposite directions. Standards side: the NIST NCCoE concept paper posted 5 Feb 2026 with comments closed 2 Apr 2026; the MCP specification of 28 Jul 2026 with authorization hardening; Agent2Agent past 150+ supporting organizations under Linux Foundation governance around 9 Apr 2026, a self-reported membership count. Proprietary side: Entra Agent ID and Entra ID Governance bring agents into the identity governance model used for people, Agent 365 was described on 18 Nov 2025 as the control plane for agents, the Work IQ interfaces reached general availability on 16 Jun 2026 with Agent2Agent and remote MCP endpoints inside the tenant trust boundary, Entra Agent ID reached Dataverse on 6 Aug 2026, Claude Tag gives the agent admin-provisioned service accounts scoped per channel with spend caps (23 Jun 2026), and an admin compliance interface shipped 22 Apr 2026. No normative agent-authorization profile has shipped MEASUREDLogged 17 August 2026, re-scored 18 August 2026 by Thesis 02 · reading dated 6 August 2026, the most recent qualifying event. A deliberate re-score from +1 to 0, with the reasoning stated rather than drifted: this signal confirms when a normative profile ships and an IAM incumbent reaches general availability against it, and weakens when drafts stall while vendors ship proprietary schemes. Both halves are now visible at once — the incumbents shipped agent identity at general availability against their own schemes rather than against a profile — so neutral is the honest reading. Every vendor capability statement here is a company claim and none is independently audited. Demand-side counterweight from three surveys whose publishers all sell into the gap they measure, so the incentive stack is three deep and every figure carries it: 71% of developers say their agents can reach sensitive information, roughly four in ten organizations have agents reaching data outside what was approved, fewer than half of security executives are confident they can identify every agent in their environment, and the aggregated governance maturity score is 35 out of 100. Field periods for two of the three are undisclosed in the aggregation and must be retrieved from each primary before any figure is printed elsewhere. Earlier-dated reading, score unchanged. The standards side has a legislative track as well as a voluntary one, and this reading records it: S.5051, the AI AGENT Act of 2026, was introduced and referred to the Senate Commerce Committee on 21 July 2026 — a bill text directing NIST to identify or develop verifiable-delegation standards: scope-limited revocable credentials, agent identity verification, real-time revocation and auditable action records. No committee action has followed — verified on congress.gov on 25 August 2026 — and the text carries no harm-allocation provision. Introduction is not enactment and a bill is not a shipped normative profile, so the score holds at 0 and the latest reading remains the one dated 6 August 2026. | a normative agent-authorization profile ships — not a concept paper — and an IAM incumbent reaches GA against it | drafts stall and vendors ship proprietary schemes instead | Thesis 01 · Thesis 02 |
| Cross-vendor agent invocationWhether a competing vendor's agent can be invoked, observed and governed with an audit trail inside another vendor's shared work surface, in general availability. Explicitly not R01.4: that tracks whether a normative authorization profile ships and whether IAM incumbents implement it, this tracks cross-vendor invocation in production surfaces. The non-overlap is part of the definition and the two must never be merged. Sources: marketplace and release announcements from four named surface owners, plus MCP and Agent2Agent release notes — event-driven, reviewed at every Scorecard [9] | Active | +1 · Two surfaces at or near the confirming bar. Notion 3.6 shipped external agents in general availability on 1 Jul 2026 — a competing vendor's coding and chat agents assignable and mentionable from a team-shared board, following an alpha on 13 May 2026. Microsoft's Work IQ interfaces reached general availability on 16 Jun 2026 exposing Agent2Agent and a remote MCP server, with agent actions described as auditable inside the Microsoft 365 tenant trust boundary; agents in Teams channels working with third-party agents over MCP remain in public preview. Agent2Agent passed 150+ supporting organizations under Linux Foundation governance around 9 Apr 2026. Against: Claude Tag runs first-party only, in Slack alone COMPANY CLAIMLogged 18 August 2026 · reading dated 18 August 2026, an event census against events dated 9 April to 1 July 2026. Every capability description is the vendor's own; the Agent2Agent figure is a self-reported membership count published by the foundation's press function and is not an adoption measurement — it must not be rendered as one. Standing counterweight, carried as precedent from outside the evidence window: the owner of one major shared surface restricted third-party software from storing or indexing messages reached through its API in mid-2025, which is the documented case of a host closing a surface it owns. Whether that host loosened or tightened third-party agent access to conversational data inside the evidence window is unresolved, and is the single most valuable open item on this signal. | two or more major shared surfaces ship governed third-party agent invocation with audit trails in general availability | surfaces close to first-party agents only, or a host restricts third-party retention of surface data as one did in mid-2025 | Thesis 02 |
Structure
| Signal | Status | Latest reading | Confirms if | Weakens if | Updated by |
|---|---|---|---|---|---|
| Platform bundling (two-sided test)Whether independent authority and assurance vendors reach $100M+ ARR independently, or are acquired and bundled into IAM and hyperscaler incumbents. Sources: earnings calls, press releases and funding announcements, with row-level detail in this series' agent M&A registry — quarterly [10] | Active | −1 · Absorption moves from 6 to 7 among authority- and execution-outcome-layer deals (the two-sided test's scope; the registry's rail-routing and execution-context rows sit outside it), on Okta's definitive agreement to acquire Permiso. CrowdStrike/SGNL: announced 8 Jan 2026, completed 20 Feb 2026, with total consideration transferred of $637.1M read from CrowdStrike's Form 10-Q for the quarter ended 30 April 2026; the technology shipped into Falcon as Continuous Identity for AI Agents on 15 Jun 2026. Okta/Permiso: definitive agreement announced 30 Jul 2026, pending close in Okta fiscal Q3 2027, no price published by either party. Standing rows: Cisco/Astrix and SailPoint/Entro both completed 29 Jun 2026; Cisco/WideField Security announced 18 Jun 2026, completed 31 Jul 2026, with no price disclosed by any party — the same acquirer's second authority-layer absorption of the year, its technology stated as going into Splunk's Agentic SOC; Zendesk/Forethought completed 26 Mar 2026; Salesforce/Fin ($3.6B) pending close. The independence side remains at zero on this signal's own confirming threshold: no independent authority or assurance vendor has published an ARR figure of any size, let alone $100M, as of 19 Aug 2026 — an absence-of-evidence finding, stated as such. Independent capital in the window totalled $370M across four rounds in seventeen days — Neo $100M on 20 Jul 2026, Zenity $125M and Obsidian Security $85M on 4 Aug 2026, Oligo Security $60M on 5 Aug 2026 MEASUREDLogged 19 August 2026 by Note 03 · reading dated 19 August 2026. Score unchanged at −1: the Permiso agreement takes the absorption side to seven, while the $370M of independent capital is recorded as capital rather than as evidence against the score, because this signal's confirming clause is measured in disclosed ARR and none of those vendors has published a revenue figure of any size. Row-level detail lives in the agent M&A registry; this reading is the summary state of that registry. Excluded from the count and recorded so the exclusions stay visible: Cyera/Oasis Security, ~$1B press-reported against a letter of intent announced 28 Jul 2026, because Cyera is a private challenger rather than an incumbent; and Palo Alto Networks/CyberArk, completed 11 Feb 2026 from a 30 Jul 2025 announcement, because it is incumbent-to-incumbent consolidation of a public company. Two scope flags are carried forward for a dated amendment at the next Scorecard rather than amended here: the definition text reads IAM and hyperscaler incumbents while this registry's operative construction is platform incumbents in identity or security, which is how Cisco, twice, and CrowdStrike are counted; and the confirming threshold carries no requirement that the vendor still be independent at the resolution date, which CyberArk shows is not the same test the signal claims to run. Bounding observation, score unchanged. A third disposition appears that this two-sided test does not cover: the capability shipped as a free platform feature, bought by nobody and priced at nothing. Cloudflare, 5 Aug 2026, from its own product posts: identity-aware AI Gateway with Cloudflare Access in OPEN BETA, and User Insights — the analytics half, the record — GENERALLY AVAILABLE “to every AI Gateway customer at no additional cost”; alongside them WriteGuard in PRIVATE BETA, the vendor's “shared policy, attribution, and auditing layer” for MCP write actions. On 14 Aug 2026 the same gateway began classifying MCP traffic from the protocol-version header, with no volume published. The score holds at −1 because Cloudflare sits on neither side of the test: it is not an independent vendor to be counted and no transaction occurred, so the absorption count stays at seven and disclosed independent ARR stays at zero. It is recorded because “no additional cost” is a published price statement, and it is the strongest measured evidence here that this layer may never become a priced category — an absorbed vendor at least sets a transfer price, a bundled one sets that the capability is worth nothing standalone. Third scope flag for the next Scorecard, not amended here: the two-sided construction has no branch for a capability that is given away. | an independent authority or assurance vendor publicly passes $100M ARR without being acquired | further absorption into IAM or hyperscaler incumbents | Thesis 01 · Note 01 · Note 03 |
| Harness multiplayer parityHow many of five named frontier harnesses — Anthropic, OpenAI, Google, Microsoft, Meta — have shipped, in general availability and not in beta or research preview, a shared agent that lives in a team surface with persistent group state and its own scoped identity distinct from the invoking user. All three conditions plus general availability must hold. This strict reading is the registry's reading and does not change between Scorecards; a Scorecard that counts previews as shipped is scoring a different signal. Sources: vendor newsrooms, changelogs and product documentation for the five named harnesses — event-driven, reviewed at every Scorecard [11] | Active | 0 · 0 of 5 on the strict reading; 2 of 5 on the loose reading (Microsoft, OpenAI). Anthropic: Claude Tag is public beta on 18 Aug 2026, Slack only, Team and Enterprise plans only, with admin-provisioned service-account identity per channel. OpenAI: workspace agents launched in research preview 22 Apr 2026 and the page carried a generally-available banner by 18 Aug 2026, but no OpenAI page states that the agent acts under an identity distinct from the invoking user. Microsoft: Copilot in Teams group chats generally available since February 2025, with Teams Mode and Agent 365 still in preview. Google: its Chat agent (22 Apr 2026) is framed as a personal agent. Meta: consumer group-chat AI and a customer-facing business agent (3 Jun 2026), neither an internal shared team agent COMPANY CLAIMLogged 18 August 2026, extended 26 and 27 August 2026 · cohort reading dated 18 August 2026, a point-in-time census. Every capability statement is a vendor's own and none is independently audited. Score 0 rather than −1 because the strict count is zero while the direction of travel is unmistakable: six vendors shipped an agent into a shared team surface between 25 Sep 2025 and 1 Jul 2026. Two facts hold the score down — Anthropic, the vendor Thesis 02 is built around, does not clear its own bar at baseline, and OpenAI began winding down consumer group chats on 9 Jul 2026, sixteen days after Claude Tag, so the record shows convergence and one retreat rather than one-way accumulation. Open item at baseline: whether OpenAI's workspace agents run under a distinct agent identity is unresolved from the announcement page, and would move the count to 3 of 5 on the loose reading if resolved yes. Later reading, score unchanged. On 26 August 2026 LangChain's founder stated on X that deepagents “is becoming a multiplayer harness”, carrying auth and memory for multiple users in the same thread. That is stated product direction and not a shipped release, and it is a founder's own claim about his own product — a company claim, admissible as direction and inadmissible as capability. The score is unchanged because this signal reads shipped harness parity, not stated intent. Confirming direction for Thesis 02, and a note candidate if and when a release ships. Wider census, score unchanged. A census of sixteen harnesses — eight vendor, eight prominent open source — read from release notes and product documentation as of 26 August 2026 and sealed on 27 August 2026: thirteen of sixteen have shipped some multiplayer capability on the loosest reading, mostly identity and administration; four of sixteen go beyond identity to strict shared state or cross-user delegation (Devin, Cursor, Dify, n8n); two of sixteen have cross-user delegation at general availability; and two of sixteen have no multiplayer capability at all, deepagents itself among them, alongside goose. The score holds at 0 because this signal reads shipped general availability inside its five-vendor cohort, where Claude Tag is still beta and no cohort member has crossed the strict test. The sharpest fact is the gap between the claim and the documentation: the “multiplayer harness” statement of the day before has no documented multi-user capability behind it, because every auth entry in deepagents-code 0.1.59 to 0.1.62 is model-provider authentication. Both general-availability cross-user-delegation examples, Devin and Cursor, sit outside the cohort, and the cohort is deliberately not widened to take them in — definition discipline, the same rule that keeps this row's strict reading fixed between Scorecards. Whether the census deserves a sibling signal of its own is an open question here, not a finding. | four or more of five at general availability on the strict reading by 31 December 2027 | two or fewer of five at general availability on the strict reading by 31 December 2027 | Thesis 02 |
| Frontier-lab annexation of canonical stateWhether a frontier lab — Anthropic, OpenAI or Google — ships a first-party, general-purpose store of canonical business objects (customers, deals, cases, invoices) with write authority, roles and an audit trail, as a product rather than as a connector into someone else's record. The signal tests whether coordination capital is annexable by the harness or stays rented from the customer's own systems. Sources: vendor newsrooms, product pages and pricing pages for the three named labs — event-driven, reviewed at every Scorecard [12] | Active | −1 · No frontier lab has shipped a first-party canonical-object store. The dated evidence points the other way: Claude for Small Business (13 May 2026) shipped fifteen agentic workflows and fifteen skills connecting to QuickBooks, PayPal, HubSpot, Canva, DocuSign, Google Workspace and Microsoft 365 — connectors into other companies' records rather than a record of its own. Claude Tag's documentation places the agent in an ephemeral vendor-hosted sandbox reaching customer systems through service-account credentials an admin sets per channel, so canonical state stays in the customer's systems while the lab holds the channel memory COMPANY CLAIMLogged 18 August 2026 · reading dated 18 August 2026, against events dated 13 May 2026 and 23 June 2026. Read the sign carefully: the score runs on the confirming axis, so −1 means annexation is not happening, which supports CALL C rather than weakening it. The single most informative fact at baseline is what a lab did when it reached for small-business coordination capital — it shipped connectors and workflow templates into an accounting ledger, a customer record and a signature service instead of building any of the three. The announcement states no price, and a secondary claim that the bundle is included at no extra cost is not supported by the primary. | a frontier lab ships a first-party general-purpose canonical-object store with write authority as a product by 30 June 2028 | labs keep shipping connectors and workflow templates into third-party systems of record instead of building a record of their own | Thesis 02 |
Energy
| Signal | Status | Latest reading | Confirms if | Weakens if | Updated by |
|---|---|---|---|---|---|
| Energy elasticityAI-optimized IaaS spend and the inference share of it, as a test of whether falling unit inference cost raises total consumption. Source: Gartner worldwide AI-optimized IaaS forecast — annual, scored once a year [13] | Active | +1 · $42.3B AI-optimized IaaS spend in 2026, +96% year over year; inference $23.3B overtakes training $19.0B for the first time; inference 55% of the category in 2026, forecast 59% in 2027 FORECASTLogged 17 August 2026 · reading dated 10 August 2026. Annual source: scored once a year, not at every Scorecard. | total spend keeps rising as unit inference cost falls | spend growth decelerates faster than unit cost declines | Thesis 01 |
Supply
| Signal | Status | Latest reading | Confirms if | Weakens if | Updated by |
|---|---|---|---|---|---|
| Salvage lot countUnited States Chapter 11 estates, other than Spirit, that have publicly marketed internal corporate data — communications, code, workflow and business-systems records, not consumer personal information — as a distinct section 363 asset lot. The voluntary-liquidation rail is recorded beside this count and does not score it. Source: free claims-agent dockets and restructuring trade press — monthly, and at every Scorecard [14][15] | Active | −1 · 0 additional estates MEASUREDLogged 24 August 2026 · a review of 15 July to 24 August 2026 found none. The null is search-based rather than a docket-by-docket census, and that scope rides with any use of it. Recorded beside the count and deliberately not scored: roughly 100 voluntary-liquidation transactions at $10,000–$100,000, and no state or federal legislative response to the Spirit sale, against 42 attorneys general in the 23andMe matter. Two arms sit under this one id and must not be blended — the lot count, and the employee-data conditions arm that CALL D (Thesis 03) grades on 30 November 2026. | 3 or more further estates market such a lot by 31 March 2027 | 0 by that date | Thesis 03 |
| Archive amortizationReddit's disclosed remaining performance obligations on contracts with an original duration of more than one year, which the issuer states consist primarily of long-term content licensing, split into the total balance and the portion contracted for calendar 2027. Source: Reddit, Inc. Forms 10-Q and 10-K on SEC EDGAR — quarterly [16] | Active | +1 · $92.1m total, of which $30.1m is contracted for calendar 2027 MEASUREDLogged 24 August 2026 · reading dated at the balance-sheet date of 30 June 2026, from the Form 10-Q filed 31 July 2026. Prior readings $143.7m total with $24.8m for 2027 at 31 December 2025, and $120.6m with $29.0m at 31 March 2026 — the total down 36% in six months while the 2027 tail grew $5.3m. Unit caveat that rides with the figure: the issuer says the balance consists primarily of long-term content licensing, not only. CALL A (Thesis 03) grades this signal on 15 November 2026. | the calendar-2027 portion stays under $45m and the total keeps falling in the Q3 2026 Form 10-Q | the calendar-2027 portion exceeds $45m, or the total rises quarter over quarter | Thesis 03 |
| Realised-payment disclosure gapHow many of six named per-use or revenue-share programmes have published an aggregate payment actually made to publishers, as opposed to a rate, a pool, a split or a participant count. Cohort fixed at first reading. This measures disclosure, not clearing, and it is not R01.1. Source: the six programmes' own announcements and product pages — quarterly [17] | Active | +1 · 0 of 6 MEASUREDLogged 24 August 2026 · a census of the six on that date. Cohort fixed at first reading: the Publisher Content Marketplace, two named pay-per-use partners, ProRata's Gist, TollBit and Comet Plus. What exists instead of a payout: a $42.5m publisher pool at an 80/20 split, a published 50/50 split, a direction statement whose product documentation still reads “closed beta”, and realisations reaching the public only as “hundreds to tens of thousands a month” for roughly 20% of about 7,000 participating sites. Every one of the six sells into the market it describes. | still 0 of 6 at 30 June 2027 | any one of the six publishes a realised aggregate payout figure | Thesis 03 |
| Channel crossingWhether a human-data manufacturer acquires, or is recorded bidding at least $5m for, a non-labour data asset: a corporate corpus, an archive, an estate's records or a licensed content library. Cohort fixed at first reading. Source: court dockets, company announcements and primary reporting naming both sides — event-driven, reviewed at every Scorecard [14][18] | Active | +1 · One court-recorded instance and two productized intake channels MEASUREDLogged 24 August 2026 · measured against a filing of 14 August 2026 and two intake pages read 22–24 August 2026. A human-data manufacturer was designated alternate bidder at $7,500,000 for a corporate corpus, its agreement carrying an exhibit that exists in no other version of the contract and names its own upload facility; a second publishes intake tiers at $100k, $500k and $1m-plus with a $5m referral programme. Deal status at point of use: the sale is announced and contested, not approved, with the hearing set for 9 September 2026. A reported late offer of $12.5m does not feed this baseline — it is single-chain press reporting with no trace in a full count of the case docket. | a second such acquisition, or a qualified bid of $5m or more, by 30 June 2027 | none by that date | Thesis 03 |
| Agent-exhaust disclosureHow many of five frontier labs name first-party agent-product usage data — coding-agent or computer-use sessions — as a training-data category in a published model card, system card or technical report. Read the sign carefully: a low count supports the reading that usage is the specification and not the corpus. Source: published model and system cards — event-driven, reviewed at every Scorecard [19] | Active | −1 · 0 of 5 MEASUREDLogged 24 August 2026 · a card census across the five named labs on that date. The most recent frontier system card names four training-data categories — public internet, public datasets, private datasets, and synthetic data generated by other models — and agent or user data is not among them, although the same vendor's consumer terms have permitted training on assistant sessions since 28 August 2025. The largest disclosed corpus of checked outcomes in that card is lab-built rather than collected. Sign note: this score runs on the confirming axis, so the minus means no lab has named the category, which supports the thesis rather than weakening it. CALL C (Thesis 03) stakes the same proposition. | 1 or more labs name the category by 30 June 2027 | 0 of 5 at that date | Thesis 03 |
| Sell-side productizationWhether any United States restructuring adviser, investment bank or claims agent offers estate sales of corporate data corpora as a distinct public offering — a service page, a sector report, a named conference session or named press comment. Not R01.5, which tests acquisition versus independence in a different layer. Source: adviser and bank websites, restructuring-association conference programmes, named press comment — quarterly [20] | Active | −1 · 0 MEASUREDLogged 24 August 2026 · search-based census on that date, and the scope of the null rides with any use of it. The strongest adjacent evidence runs the other way and is demand-side: a law firm's own published claim of “a genuine buyer market that did not exist five years ago” for accumulated corporate data pools, 7 July 2026, written without reference to any named case — practitioner attention, not an offering. The buy side, by contrast, publishes tiers and referral fees. Sign note: a minus here says the asset class does not exist yet, which is the honest reading and the one CALL B (Thesis 03) stakes. | 1 or more such public offerings by 30 June 2027 | none by that date | Thesis 03 |
Staked calls
Nine dated calls are open. Two were stated in Thesis 01, section 10, three in Thesis 02, section 10 and four in Thesis 03, section 10. All nine are reproduced here word for word, with the citations renumbered to this page's source list.
Thesis 02 and Thesis 03 each lettered their calls A, B and C, and they are different bets on different signals. On this page the letter never travels alone: every lettered call carries the thesis that staked it.
CALL 1 — agentic checkout share exceeds 5% of agentic activity by Q2 2027 (HUMAN series). Confidence ~55%. A bet against my own tracked data: the series is flat to down across four readings while total agent volume grew. I make it because the authorization infrastructure announced between June and August 2026 has not yet had a shopping season to run through. If the share is still under 3% by Q2 2027, the consumer-side machine-transaction thesis is behind schedule and section 4's ranking is wrong — authority-to-act would be binding harder and longer than I assume.
Signal R01.1 · resolution date 30 June 2027 · graded in the Scorecard that follows it.
CALL 2 — the share of AI builders offering outcome-based pricing as their primary model stays under 30% through end-2027 (ICONIQ series, currently 23%). Confidence ~70%. Unpredictable exception costs push vendors toward hybrid pricing — platform access plus usage, with safeguards — already the pattern ICONIQ observes. The unit is ICONIQ's, not mine: no public series measures the share of contracts signed on outcomes, so the call is stated in the vendor unit that is actually published and will be scored against it. The uncomfortable part, on the record: that series has run 2% to 18% to 23% in four quarters, so the call needs a steep climb to flatten roughly where it stands [2]. It is the least comfortable bet here.
Signal R01.2 · resolution date 31 December 2027 · graded in the Scorecard that follows it.
CALL A (Thesis 02) — by 31 December 2027, at least four of the five named harnesses (Anthropic, OpenAI, Google, Microsoft, Meta) will have a generally available shared agent living in a team surface with persistent group state and its own scoped identity. Confidence 75%. Ledger signal R02.1. The baseline makes it demanding: on the strict reading the count today is zero, because Anthropic has not cleared its own bar. Two base rates cut against me — parity in collaboration features has historically taken years rather than quarters, and the convergence was not independent, since a widely read investor essay told the category to build exactly this in December 2025 [21]. July's open licences do not resolve it; none of those parties is in the cohort.
Signal R02.1 · resolution date 31 December 2027 · graded in the Scorecard that follows it.
CALL B (Thesis 02) — through 31 December 2027, no member of the fixed cohort (Salesforce, HubSpot, Atlassian, monday.com, Asana, Smartsheet) will report a separately disclosed non-seat agent revenue line exceeding 10% of total revenue. Confidence 65%. Ledger signal R02.2. The rationale is not that vendors are silent, which would be false [6]. It is that disclosure exists and scale does not: $1.2 billion against roughly $44 billion annualized is about 2.7%. This is a bet on a reporting convention as much as on economics.
Signal R02.2 · resolution date 31 December 2027 · graded in the Scorecard that follows it.
CALL C (Thesis 02) — by 30 June 2028, no frontier lab will have shipped a first-party, general-purpose store of canonical business objects of customer-record or resource-planning class as a product. Confidence 70%. Ledger signal R02.5. The test of whether the harness annexes coordination capital or keeps renting it. Calls are graded in public at their resolution dates, misses included, at equal visual weight.
Signal R02.5 · resolution date 30 June 2028 · graded in the Scorecard that follows it.
CALL A (Thesis 03) — Reddit's contracted licensing revenue for calendar 2027 will still be under $45m in the third-quarter 2026 Form 10-Q. Confidence 80%. Ledger signal R03.2. The filing is expected around 30 October 2026 [16], which falls after the October Scorecard's cutoff, so this call is graded on its own date rather than in a Scorecard. Being wrong would mean the archive is being re-signed at durable term and the amortization reading is too strong.
Signal R03.2 · resolution date 15 November 2026 · graded on its own date, with a dated log entry and an appended ledger reading.
CALL B (Thesis 03) — through 30 June 2027, no United States restructuring adviser, investment bank or claims agent will publish a distinct sell-side offering for estate sales of corporate data corpora. Confidence 70%. Ledger signal R03.6. Graded from firm websites, restructuring-association conference programmes and named press comment [20]. Being wrong would mean the asset class institutionalised a year earlier than this reading expects, and it is the single fastest way Thesis 03 becomes obsolete.
Signal R03.6 · resolution date 30 June 2027 · graded in the Scorecard that follows it.
CALL C (Thesis 03) — through 30 June 2027, no frontier lab will name first-party agent-product usage data as a training-data category in a published model or system card. Confidence 70%. Ledger signal R03.5. Graded from cards published in the window [19]. This one runs against the popular version of its own argument: if a lab discloses it, “usage is the specification, not the corpus” needs rewriting.
Signal R03.5 · resolution date 30 June 2027 · graded in the Scorecard that follows it.
CALL D (Thesis 03) — the Spirit deidentified-data sale will be approved by 30 November 2026 with at least one employee-data condition attached — a carve-out, a review protocol, or a use restriction — that is absent from the sale agreement filed on 14 August 2026. Confidence 60%. Ledger signal R03.1. Graded from the signed sale order on the case's public docket [14]. This bets on the terms, not the outcome: if the sale is approved as filed, or is not approved by that date, it is a miss and will be graded as one.
Signal R03.1 · resolution date 30 November 2026 · graded on its own date, with a dated log entry and an appended ledger reading.
All nine calls are scored publicly in every subsequent publication, including if they are wrong. The first grading date is 15 November 2026.
Registries
Five registries sit behind the ledger. Each was a byproduct of writing a thesis rather than a separate data project, which is why it can be kept honest: the rows accumulate with time, and none of them can be faked retroactively without breaking a dated source link.
-
Outcome price registry10 rows
What vendors charge for a completed outcome — a resolved conversation, a qualified lead, a handled procedure — with each vendor's own definition of “resolved”, and the per-conversation and per-action meters kept alongside as counter-examples.
Published rates and press-reported estimates are marked separately; unverified numbers say so.
-
Pricing model registry38 rows
How agent vendors meter, one row per product: access seats, consumption credits, per action, per conversation, per outcome, per session-hour, per container-hour — and which of those a single vendor runs at the same time. The wider view of the same question the outcome price registry asks in one category. The registry runs across the frontier harnesses, their APIs, two work-management vendors and four open-licence shared-agent projects. Three more were added on 19 August 2026, all from one infrastructure vendor's launch week: a usage-reporting endpoint with no price, agent tracing free in beta with a dated rate behind it, and a retrieval service carrying preview rates.
Every row carries a price-disclosure column: published-primary, press-reported or vendor-undisclosed. The working file also holds a dated re-verification of the Claude Enterprise row against its 17 August seed; the ledger renders the later observation, not both, which is why the table shows 38 rows where the file holds 39.
-
Agent M&A registry11 rows
Acquisitions in the agent stack, tagged by layer — authority, assurance, execution-outcome, execution-context, rail-routing — with announced date, status and status date, so the bundling signal can be read from rows rather than from memory. Five of the eleven rows sit in the authority layer, and between them they hold the registry's whole range of price evidence: CrowdStrike/SGNL, the only row whose price comes from a filing rather than a release; Cisco/WideField Security, whose price no party has ever named and no outlet has ever reported; and Okta/Permiso, the cleanest fit anywhere here to R01.5's own wording. Two rows were added on 25 August 2026: Palo Alto Networks/Portkey, which gives the rail-routing layer a second buyer three months ahead of Stripe/OpenRouter and at a price no party has published; and Dynatrace/Arize, which opens the assurance layer and is deliberately not counted in R01.5, because Dynatrace is neither an IAM nor a hyperscaler incumbent.
Prices are labelled company-announced, press-reported or undisclosed; nothing is stated as a fact the buyer never confirmed.
-
Verdict registry6 rows published
Public claims about this territory, adjudicated with the claim's owner named and quoted: who said it, where, on what date, what the verdict is — yes, no, refine or retired — and the reasoning behind it. Opened by Thesis 02 on 19 August 2026, and live from that date.
A claim cannot be adjudicated here until its owner is quoted, because arguing with an unattributed claim is arguing with a strawman. The working file holds eight rows; two are earlier drafts whose owners could not be established and they are recorded as superseded rather than deleted.
-
Data deals registry5 rows
Transactions in which a body of data changed hands — one row per deal, sorted by channel: acqui-data, salvage, brokerage, licensing. Each row carries what was bought, what was paid, how the price is known, where the transaction stands, and the condition attached to using the data. Opened by Thesis 03 on 24 August 2026.
Every row carries a use restriction, because a price without its use restriction is not a price: the same corpus, offered to the same bidder on different de-identification terms, cleared at different numbers. Status is a column, not a caveat in prose — a contested sale is never rendered as a completed one.
All five are printed below as they currently stand. In the four registries that carry numbers, each row carries a disclosure label saying how the number is known, and one evidence badge that follows from it: MEASURED where the vendor publishes the price itself, COMPANY CLAIM where a company announced a figure it never published as a rate, PRESS-REPORTED where the figure is known only from journalism — the outlet and how it sourced the number sit beside it — and INFERENCE where the number is my own arithmetic or judgement, including a row that records what a vendor has not published rather than a rate. An unpublished price is written as unpublished, not filled in from reporting and left to look like a rate. The verdict registry carries no prices: its rows carry the claim's owner, the evidence class of the claim itself, the verdict and the reasoning.
Outcome price registry
| Vendor · product | Unit | List price (USD) | Pricing model | Disclosure | Source |
|---|---|---|---|---|---|
| Fin (formerly Intercom)Fin AI Agent · renamed from Intercom in May 2026; Salesforce agreed to acquire it for $3.6B, announced 15 June 2026, pending close | Per resolution, procedure handoff or disqualification | $0.99 per resolution · $9.99 per qualification | Pure per-outcome, with a 50-outcome monthly minimum. Only one outcome is billed per conversation even when Fin takes several actions, and a plain handoff is free. Vendor definition of resolved: no further help is requested after Fin's last answer. | Published-primary MEASUREDUnchanged as of August 2026 | fin.ai |
| HubSpotBreeze Customer Agent | Per resolved conversation | $0.50 (50 HubSpot Credits) | Outcome-based; unresolved conversations are free; Pro and Enterprise only. Resolved = the agent shares a source or performs an action with no human handoff within 72 hours, or qualifies a lead. | Published-primary MEASUREDEffective 14 April 2026, cut from $1.00 per conversation | HubSpot |
| HubSpotBreeze Prospecting Agent | Per lead recommended for outreach | $1.00 (100 HubSpot Credits) | Outcome-based. | Published-primary MEASUREDEffective 14 April 2026, in the same announcement as the Customer Agent price | HubSpot |
| SalesforceAgentforce (conversations) · the counter-example row | Per conversation | $2.00 | Per conversation, not per outcome. The largest vendor in the category prices the interaction rather than the result. | Published-primary MEASUREDCurrent as of August 2026 | Salesforce Help |
| SalesforceAgentforce (Flex Credits) | Per action | $0.10 per action (20 credits) · $500 per 100,000 credits · voice action 30 credits = $0.15 | A consumption meter priced per action, not per outcome. Listed for contrast. | Published-primary MEASUREDEffective 15 May 2025 | Salesforce Help |
| GorgiasAI Agent | Per automated resolved conversation | $1.00 on monthly billing · $0.90 annual | Outcome-based add-on to a helpdesk plan, sold in bundles of 30 to 2,500+ a month with overages. Billable when the agent resolves a conversation entirely on its own; the Starter plan is $1.00. | Published-primary MEASUREDPublished in a vendor blog post rather than a rate card; page updated 28 May 2026 | Gorgias |
| ZendeskAI agents / Automated Resolutions · acquired Forethought, completed 26 March 2026 | Per automated resolution | No published rate. Third parties report ~$1.50 committed and ~$2.00 pay-as-you-go, falling toward ~$1.00 at very high volume — unverified. | Outcome-based meter. Since January 2026 overages above committed volume auto-charge and the meter is uncapped. Vendor wording: pricing based on the successful outcomes they deliver, with resolved meaning without escalation to a human. | Vendor-undisclosed INFERENCEThe model is published, the rate is not; the figures are a third-party estimate | Zendesk |
| SierraSierra agents | Per resolved outcome | No published rate. Widely reported at ~$1.50 per successful resolution, with a $1.00–$2.50 range cited and contracts typically from ~$150K a year — unverified. | Outcome-based, with blended per-conversation pricing for low-value interactions. Every contract is negotiated. | Vendor-undisclosed INFERENCEModel verified; the rate rests on secondary reporting only | CloudTalk |
| DecagonDecagon agents | Per resolution, or per conversation | No published rate. One reported enterprise rate of $0.50 per resolution — unverified. | Two models offered: per conversation as the default, and per resolution at a higher unit rate. | Vendor-undisclosed INFERENCESingle secondary source; no pricing page exists | eesel.ai |
| ForethoughtSolve · acquired by Zendesk, completed 26 March 2026; kept as a historical row | Per resolved conversation | No published rate. Reported at ~$0.90 per resolved conversation — unverified. | Platform fee plus usage. | Vendor-undisclosed INFERENCEVendr median contract ~$60–75K a year | eesel.ai |
Two of these ten rows were taken by a larger vendor within five months: Forethought closed into Zendesk on 26 March 2026, and Fin sits under a $3.6B Salesforce agreement announced 15 June 2026 that has not yet closed. The category is being priced and bought at the same time.
Pricing model registry
| Vendor · product | Pricing models | Unit | List price (USD) | Disclosure | Source |
|---|---|---|---|---|---|
| AnthropicClaude Enterprise · re-verified 18 August 2026 | Access + consumption | Seat per month, plus metered API usage | $20 per seat per month (list), plus usage at API rates | Published-primary MEASUREDA pre-research analysis flagged the 17 August row as a probable mislabel. It is not one: the Enterprise card carries “Seat price + usage at API rates” and “$20/seat. Usage cost scales with model and task.” on two independent extractions on 18 August 2026. Enterprise agreements themselves remain negotiated and unpublished. Eight of ten listed Enterprise inclusions are spend limits, role-based access, directory provisioning, audit logs and a compliance interface — the premium is priced on authority infrastructure rather than on model access. | Anthropic |
| OpenAIWorkspace Agents | Consumption (credits) | Credit | No published list rate per agent action; credit-metered. | Vendor-undisclosed INFERENCECredit-based agent pricing began 6 May 2026. The model is public; the per-unit rate is not. | OpenAI |
| MicrosoftCopilot Studio | Consumption (tenant capacity) + pay-as-you-go | Message credit pack (25,000 credits), or PAYG metering | $200 per 25,000 credits, or pay-as-you-go | Published-primary MEASUREDPrepaid tenant capacity rather than per seat or per outcome: the buyer books capacity, not results. | Microsoft |
| SalesforceAgentforce | Consumption (per action) + per conversation + per user + flat platform fee | Action / conversation | $0.10 per action (20 Flex Credits) · $500 per 100,000 credits · $2.00 per conversation | Published-primary MEASUREDFour coexisting meters at the category's largest vendor, and the priced object is the interaction rather than the outcome. | Salesforce Help |
| NotionCustom Agents | Consumption (automation credits) | 1,000 automation credits | $10 per 1,000 credits | Published-primary MEASUREDAutomation credits sold on top of the seat price: a consumption layer bolted onto an access product. | Notion |
| Fin (formerly Intercom)Fin AI Agent | Outcome (pure) | Resolution / procedure handoff / disqualification | $0.99 per resolution · $9.99 per qualification | Published-primary MEASURED50-outcome monthly minimum; one outcome billed per conversation; a plain handoff is free. | fin.ai |
| HubSpotBreeze Customer Agent | Outcome | Resolved conversation | $0.50 (50 HubSpot Credits) | Published-primary MEASUREDEffective 14 April 2026; unresolved conversations are free; Pro and Enterprise only. | HubSpot |
| HubSpotBreeze Prospecting Agent | Outcome | Lead recommended for outreach | $1.00 (100 HubSpot Credits) | Published-primary MEASUREDEffective 14 April 2026, in the same announcement as the Customer Agent price. | HubSpot |
| ZendeskAI agents / Automated Resolutions | Outcome | Automated resolution | No published list rate. Third parties report ~$1.50 committed and ~$2.00 pay-as-you-go, falling toward ~$1.00 at very high volume — unverified. | Vendor-undisclosed INFERENCEModel published, rate not. Since January 2026 overages above committed volume auto-charge and the meter is uncapped. | Zendesk |
| SierraSierra agents | Outcome (stated policy) + blended per conversation | Resolved outcome | No list price. Widely reported at ~$1.50 per successful resolution, $1.00–$2.50 cited, contracts typically from ~$150K a year — unverified. | Press-reported PRESS-REPORTEDOutcome pricing as stated policy with no published rate; every contract negotiated. The model is verified, the number is not. | CloudTalk |
| GorgiasAI Agent | Outcome (add-on to a helpdesk plan) | Automated resolved conversation | $1.00 on monthly billing · $0.90 annual | Published-primary MEASUREDPublished in a vendor blog post rather than a rate card; page updated 28 May 2026. | Gorgias |
| DecagonDecagon agents | Outcome + per conversation | Resolution or conversation | No published rate. One reported enterprise rate of $0.50 per resolution — unverified. | Press-reported PRESS-REPORTEDSingle secondary source; no pricing page exists. | eesel.ai |
| ForethoughtSolve · acquired by Zendesk, completed 26 March 2026 | Outcome + platform fee | Resolved conversation | No published rate. Reported at ~$0.90 per resolved conversation — unverified. | Press-reported PRESS-REPORTEDVendr median contract ~$60–75K a year. | eesel.ai |
| AnthropicClaude Pro | Access | User per month | $20 monthly · $17 per month billed annually ($200 up front) | Published-primary MEASUREDObserved 18 August 2026. The individual tier. $20 is the same number this vendor uses for the standard team annual seat and for the enterprise anchor; the flattening across three very different products is the finding, not a mislabel. | Anthropic |
| AnthropicClaude Max | Access | User per month | From $100 per month (5× and 20× usage tiers) | Published-primary MEASUREDObserved 18 August 2026. The individual power-user ceiling, and the reference point the premium team seat is priced against. The shared-agent surface is not available on individual plans. | Anthropic |
| AnthropicClaude Team | Access (seat) | Seat per month | Standard $20 annual / $25 monthly · premium $100 annual / $125 monthly (5× standard usage) | Published-primary MEASUREDObserved 18 August 2026. The page states “for teams of 2 to 150” and that the plan includes the coding and agent surfaces. A secondary source asserts a five-seat minimum — unverified and not adopted here. The launch promotion separately requires 10+ paid seats, so the seat-minimum question stays unresolved without a checkout flow. | Anthropic |
| AnthropicClaude Tag · the shared-agent surface | Consumption (organization usage balance) | Channel and thread work drawn from an org-funded balance under an admin spend limit | No published per-unit rate · no per-seat charge | Vendor-undisclosed INFERENCEObserved 18 August 2026. Public beta, Slack only, Team and Enterprise plans only. Vendor wording: “Adding Claude to Slack doesn't add a per-seat charge.” Channel work bills to the organization; a direct message runs on the sender's own account and bills to that seat — the cost boundary is drawn along the coordination boundary. The model is published, the rate is not; the vendor's own answer to what it costs is to run a pilot with a spend limit and watch the per-channel breakdown. This is the row R02.3 turns on. | Anthropic |
| AnthropicClaude Tag launch promotion | Promotional credit | One-time credit per organization | $25,000 per Enterprise organization · $2,500 per Team organization with 10+ paid seats | Published-primary MEASUREDObserved 18 August 2026. Credits expire 1 September 2026 at 23:59 Pacific; after depletion usage bills to the organization as normal. Covers public and private Slack channels only, excluding direct messages, the coding surface and the API. Consequence for any adoption figure: usage observed before 1 September 2026 is credit-subsidised and must carry that caveat. | Anthropic |
| AnthropicClaude API — Opus 5 | Consumption (tokens) | Per million tokens | $5 input / $25 output · batch $2.50 / $12.50 · cache read $0.50 · 5-minute cache write $6.25 | Published-primary MEASUREDObserved 18 August 2026. The prior flagship was $15/$75, so the nominal cut is 3×. The vendor's own documentation states that models from Claude 4.7 onward use a tokenizer producing roughly 30% more tokens for the same text, so the realised cut on a fixed workload is nearer 2.3×. Any per-token price chart is misleading without that caveat. | Anthropic |
| AnthropicClaude API — Sonnet 5 | Consumption (tokens) | Per million tokens | $2 input / $10 output · batch $1 / $5 | Published-primary MEASUREDObserved 18 August 2026. The vendor cancelled a pre-announced increase to $3/$15 scheduled for 1 September 2026 and made the introductory price standard. A frontier lab forgoing a 50% list rise thirteen days before it was due is the strongest in-window evidence that API-side price competition is still running downhill. | Anthropic |
| AnthropicClaude Managed Agents | Consumption (tokens + runtime) | Session-hour | $0.08 per session-hour on top of model token rates | Published-primary MEASUREDObserved 18 August 2026. A new meter type for this registry: time. Metered only while a session is running; idle and rescheduling are excluded, and the batch discount does not apply. A worked example in the documentation puts a one-hour flagship session at $0.705 in total, of which $0.08 is runtime. | Anthropic |
| AnthropicClaude API — server-side web search | Consumption (tool calls) | 1,000 searches | $10 per 1,000 searches | Published-primary MEASUREDObserved 18 August 2026. Charged on top of tokens. Failed searches are not billed, and web fetch carries no additional charge. | Anthropic |
| AnthropicClaude API — code execution | Consumption (container time) | Container-hour | $0.05 per hour per container beyond 1,550 free container-hours per organization per month | Published-primary MEASUREDObserved 18 August 2026. Free when combined with web search or web fetch. Five-minute minimum per execution, and files attached to a request bill container time even if the tool is never called. | Anthropic |
| AnthropicClaude API — data residency | Consumption multiplier | Multiplier on all token categories | 1.1× for US-only inference · 10% premium on regional and multi-region endpoints at two cloud marketplaces | Published-primary MEASUREDObserved 18 August 2026. Geography priced as a dimension of consumption, and the line item that lands on any organization holding shared channel state under a residency constraint. | Anthropic |
| OpenAIAPI — GPT-5.6-Sol | Consumption (tokens) | Per million tokens | $5 input / $0.50 cached input / $30 output · batch 50% off | Published-primary MEASUREDObserved 18 August 2026 on the vendor's developer documentation. The flagship tier, with output priced 20% above the comparable Anthropic flagship on list. | OpenAI |
| OpenAIAPI — GPT-5.6-Terra | Consumption (tokens) | Per million tokens | $2 input / $0.20 cached input / $12 output · batch 50% off | Published-primary MEASUREDObserved 18 August 2026. A reported cut of 20% effective 30 July 2026, that figure from a cost-management vendor that sells into this problem. Coverage states that this tier and the cheapest one are not selectable in normal chat and live in the agent surfaces — the cheap tiers are reserved for agent work. | OpenAI |
| OpenAIAPI — GPT-5.6-Luna | Consumption (tokens) | Per million tokens | $0.20 input / $0.02 cached input / $1.20 output · batch 50% off | Published-primary MEASUREDObserved 18 August 2026. A reported cut of 80% effective 30 July 2026; the attribution for the cut is secondary, the rates themselves are from the vendor's own developer documentation. | OpenAI |
| MicrosoftMicrosoft 365 Copilot Business | Access (seat add-on) | Seat per month | $18.00 paid yearly (promotional; standard $21.00) · $25.20 paid monthly | Published-primary MEASUREDObserved 18 August 2026. Bundles pre-built agents and states that use of agents published to Microsoft 365 Copilot is included in the licence — the clearest published statement anywhere in this registry that a seat can absorb agent consumption. For organizations up to 300 users. | Microsoft |
| AsanaAsana (AI credit allowances) | Access (seat) + consumption (AI credits) | Seat per month plus a monthly AI credit allowance | Starter $10.99 annual / $13.49 monthly with 50K credits · Advanced $24.99 annual / $30.49 monthly with 75K · Enterprise contact sales with 200K | Published-primary MEASUREDObserved 18 August 2026. Credits are allocated per billing account per month rather than per seat. The agent-building studio is offered in three options, one included with rate limits and two paid. | Asana |
| AsanaAI Teammates | Access tier and/or consumption — undisclosed | Not published | No published price | Vendor-undisclosed INFERENCEObserved 18 August 2026. Listed as available across four plan tiers with details requiring a sales conversation. The vendor whose chief product officer argues for multiplayer-by-design does not price the multiplayer surface: it prices seats and meters credits beneath them. If the surface were the asset, a price for it would appear here. | Asana |
| Y CombinatorQM (Quartermaster) | Open source (no licence fee); the operator pays its own model and infrastructure costs | Repository licence | $0.00 (MIT licence) | Published-primary MEASUREDOpen-sourced 31 July 2026, observed 18 August 2026. The repository describes itself as a multiplayer agent harness for work, in Slack and on the web, with scoped memory, files, permissions, schedules and a durable sandbox per person and per room, and the same identity carried between Slack and the web app. The row that matters most to R02.3: the capability a frontier lab sells inside team and enterprise seats is available at a licence price of zero. | GitHub |
| BlockBuzz | Open source (no licence fee); self-hosted relay | Repository licence | $0.00 (Apache 2.0 licence) | Published-primary MEASUREDLaunched 21 July 2026, observed 18 August 2026. The repository describes a workspace where humans and agents build together on a relay you own, and states that agents are members rather than bots — added to a channel the same way a person is, holding their own keypair, channel memberships and audit trail. It prices the shared-agent surface and the scoped agent identity at zero. | GitHub |
| Nous ResearchHermes Agent (self-hosted) | Open source (no licence fee); the operator pays its own model and infrastructure costs | Repository licence | $0.00 (MIT licence) | Published-primary MEASUREDObserved 18 August 2026 at 232.5K GitHub stars. Runs across seven messaging surfaces and a command line. A bot mode released 18 August 2026 adds multi-agent rooms of two to six participants with mention handoffs. | GitHub |
| Nous ResearchNous Portal (hosted Hermes Agent credits) | Access (subscription) + consumption (credits) | User per month | Free $0 · Plus $20 for $22 in credits · Super $100 for $110 · Ultra $200 for $220 | Press-reported PRESS-REPORTEDObserved 18 August 2026. Mirrors the $20 / $100 / $200 ladder exactly, but discloses the meter underneath the seat: each tier states the dollar value of credits it buys, so the gross margin on the access layer is visible on the page. No frontier harness publishes this. The vendor's own portal returned HTTP 429 to the fetcher; the figures come from a secondary tutorial published 6 August 2026 by a hosting vendor that sells the infrastructure the self-hosted path runs on — incentive noted, and the row is marked author to verify. | Hostinger |
| xAIGrok Bot | Access bundled into existing subscription tiers; no standalone price published | Seat per month via the host tier | Host tiers reported at $120 per seat per month, $200 per month and $300 per month; no price for the agent itself | Press-reported PRESS-REPORTEDEarly beta from 11 August 2026, observed 18 August 2026. A persistent per-account cloud machine with browser, filesystem and terminal, and a catalogue of 220 plugins with none installed by default. No per-run, per-bot or per-machine meter is published, so the compute sits inside the seat — the same shape as the unpriced shared surface above, resolved the other way. The vendor's site returned HTTP 403 to the fetcher; prices are corroborated across three secondary outlets and the row is marked author to verify. | Unite.AI |
| CloudflareBillable Usage API | No charge published — a read endpoint over the account's own usage meter | One endpoint; one row per charge period per product | No price published for the endpoint itself | Published-primary INFERENCELive 3 August 2026, observed 19 August 2026. Vendor wording: “The endpoint is live today for all self-serve accounts.” One endpoint returns usage and cost for every usage-based product on the account, one row per charge period per product, with fields mapped onto the open FinOps cost and usage specification so the record reads into other vendors' cost tools, and data updated daily. The vendor states no price for the endpoint itself, so the row records an unpriced product rather than a published rate of zero. Cloudflare sells every metered product this endpoint reports on, so the meter and the counter over it belong to the same vendor — though the specification is an open one, which makes the record deliberately portable and cuts against reading meter ownership as a lock. | Cloudflare |
| CloudflareAgents · agent tracing | Consumption (trace events); free during beta, with an included monthly allowance on the paid plan from 1 October 2026 | Million trace events per month | Free while in beta · from 1 October 2026 the paid plan includes 20 million events a month, then $0.60 per additional million · the free plan carries 200,000 events a day | Published-primary MEASUREDLaunched 4 August 2026, observed 19 August 2026. Vendor wording: agent tracing “launches today” and “All tracing is currently free while in beta” — beta is not general availability, and the 1 October 2026 rate is announced rather than charged. Retention runs three days on the free plan and seven on the paid one. Traces add spans for agent invocations, model calls, tool execution, approval events and supported subagent calls on top of the platform spans already captured, and the vendor states the same structured record can also power evaluations, analytics and token-usage reporting. A meter given away in beta with its price already dated, by a vendor that sells the products it meters. | Cloudflare |
| CloudflareAI Search | Consumption (tokens + storage + queries) | Per million tokens ingested, per GB-month stored, per 1,000 queries | Preview pricing: $0.75 per million tokens ingested (plus $0.50 per million tokens for images) · $2.00 per GB-month stored · $0.75 per 1,000 semantic queries · $0.10 per 1,000 full-text queries · embedding and reranking free on the default models | Published-primary MEASUREDPublished 6 August 2026, observed 19 August 2026. Vendor wording: the service is “free” during beta and the pricing is “preview” — a beta carrying preview rates is not general availability, and the rates are not yet charged. Free monthly allotments of 5 million ingestion tokens, 10 GB of storage and 2,000 queries; a worked example in the post puts 20,000 documents, 1,000 images and 30,000 semantic queries at about $35. Retrieval is metered per token and per query while the model layer is zero-rated — vendor wording: “Embedding and reranking are free when you use the default models, so no need to worry about predicting token count.” The vendor sells the retrieval surface and the model layer both, and prices only one of them. | Cloudflare |
Twenty-eight of the thirty-eight rows publish a rate; ten do not. Eleven run two or more meters at once, which is the finding this registry exists to hold: outcome pricing is arriving as an added meter rather than as a replacement for the old ones. Three of the twenty-eight publish a rate of zero — the shared-agent surface under an open licence — and one hosted vendor publishes the credit value sitting under each seat, which no frontier harness does.
Agent M&A registry
| Acquirer → target | Layer | Announced | Status | Price (USD) | Source |
|---|---|---|---|---|---|
| Cisco → Astrix | Authority | 4 May 2026 | Completed 29 June 2026 | ~$400M, press-reported PRESS-REPORTEDReported by Calcalist and not confirmed by either party. Non-human identity and agent authorization folded into a networking and security incumbent. | Cisco |
| Cisco → WideField Security | Authority | 18 June 2026 | Completed 31 July 2026 | Undisclosed COMPANY CLAIMNo price appears in the announcement and none has been reported anywhere — undisclosed, not merely unconfirmed. Both dates are the acquirer's own: intent announced 18 June 2026 and the completion recorded on the same page on 31 July 2026, the same evidence convention as the Cisco/Astrix row above. Cisco's second authority-layer absorption of the year, and Cisco places it in that run itself, “building on the recent additions of Astrix Security and Galileo”. WideField sold identity lifecycle security — discovery of human and non-human identities, exposure mapping across accounts and roles, and live session monitoring — and never published a revenue figure of any size, so the independence side of R01.5 is untouched. The technology is stated as going into Splunk's Agentic SOC and the Cisco Data Fabric: authority telemetry becomes the platform's own control plane rather than an interoperable profile, which is why this row also reads onto R01.4's weakening side. Counted under this registry's operative construction of R01.5 — platform incumbents in identity or security — as Cisco/Astrix and CrowdStrike/SGNL already are. | Cisco |
| SailPoint → Entro | Authority | 15 June 2026 | Completed 29 June 2026 | ~$200M, press-reported PRESS-REPORTEDThe second authority-layer absorption to complete on the same day as Cisco/Astrix, this one by an identity-governance incumbent. | SailPoint |
| CrowdStrike → SGNL | Authority | 8 January 2026 | Completed 20 February 2026 | $637.1M, filed MEASUREDTotal consideration transferred of $637.1M per CrowdStrike's Form 10-Q for the quarter ended 30 April 2026, filed 4 June 2026: $627.9M in cash net of $9.4M of cash and restricted cash acquired, plus $9.2M for the fair value of replacement equity awards covering pre-acquisition service. Preliminary allocation: goodwill $561.1M — 88% of consideration, calculated here — and developed technology $87.9M over a 96-month life. A further ~$82.2M of Class A shares was issued subject to service vesting and sits outside the purchase price as post-combination compensation. The widely quoted $740M headline is a spokesperson's on-the-record statement to SecurityWeek on 8 January 2026, appears in no release and no filing, and must never be blended with the filed figure; the announcement itself stated no number. The filing records the acquisition as immaterial to CrowdStrike's statements. Forty-three days from announcement to close; the technology shipped into Falcon as Continuous Identity for AI Agents on 15 June 2026, 115 days later. The absorbing incumbent is an endpoint and cloud-security platform rather than an IAM vendor, counted under this registry's operative construction of R01.5. | SEC Form 10-Q |
| Okta → Permiso | Authority | 30 July 2026 | Pending close as of 19 August 2026 | No published price. ~$200M press-reported — unverified PRESS-REPORTEDDefinitive agreement. Okta's release states no terms and SecurityWeek confirms terms were not disclosed — a measured negative fact. The ~$200M is a single source with knowledge of the deal, cited by TechCrunch on 30 July 2026, with an Okta spokesperson declining to comment but not disputing it; the figure must never be printed without that qualifier. Permiso is an identity threat detection and response vendor covering human, non-human and agentic identities across multi-cloud, reading Microsoft Entra ID and Active Directory as well as Okta. Expected to close in Okta fiscal Q3 2027 — 1 August to 31 October 2026 on a 31 January fiscal year end — so a purchase-price allocation would land with those results in early December 2026. Okta states the transaction has no impact on the guidance issued 27 May 2026. The cleanest fit in this registry to R01.5's own wording: an independent assurance vendor absorbed by an IAM incumbent. Announced is not absorbed — the close window had not expired as of 19 August 2026. | Okta |
| Zendesk → Forethought | Execution-outcome | 11 March 2026 | Completed 26 March 2026 | Undisclosed COMPANY CLAIMTerms undisclosed; dates from the acquirer's release. Fifteen days from announcement to close, for an outcome-priced vendor absorbed by the helpdesk incumbent whose meter it competed with. | PR Newswire |
| Salesforce → Fin | Execution-outcome | 15 June 2026 | Pending close as of 17 August 2026 | $3.6B, company-announced COMPANY CLAIMAnnounced by the acquirer; expected to close in Salesforce fiscal Q4 2027. The largest disclosed price here, paid for the category's clearest pure-outcome meter. | Salesforce |
| Stripe → OpenRouter | Rail-routing | 19 August 2026 | Announced, 19 August 2026 | More than $7B, press-reported floor PRESS-REPORTEDFirst reported by Bloomberg on 16 August 2026; both companies announced the acquisition on 19 August 2026 — Stripe's newsroom and OpenRouter's blog — with no terms disclosed, so the figure remains a single press report and keeps its floor class. A payments rail buying a model-routing rail is the newest layer in this registry. | Bloomberg |
| Palo Alto Networks → Portkey | Rail-routing | 30 April 2026 | Completed 29 May 2026 | Undisclosed COMPANY CLAIMNeither primary release carries a figure: the intent release of 30 April 2026 discloses no terms and the completion release of 29 May 2026 names none either — a measured negative fact on both dates, and both dates are the acquirer's own, the same evidence convention as the Cisco rows, so this row takes the same undisclosed convention as Cisco/WideField Security above. One outlet has reported a number, and it is recorded as a note rather than as this row's price: a $120M–$140M range from The Economic Times citing unnamed sources — single-outlet, unverified, confirmed or disputed by no party, and never to be printed without those qualifiers. The resolution path is Palo Alto Networks' FY2026 Form 10-K, for the fiscal year ended 31 July 2026, which has not been read — so the price stays open rather than settled. Portkey is an AI gateway and control plane, in the acquirer's own words “the AI Gateway for Prisma AIRS, acting as the central nervous system that can monitor, route, and secure every AI transaction across the enterprise” — the same rail-routing family as Stripe/OpenRouter above, and outside R01.5's two-sided test exactly as that row is, so it adds no scope flag and moves no count. The comparison is what the row is for: the same layer, three months apart, two buyers, and the security incumbent's only reported price is a small fraction of the payments incumbent's press-reported floor. Whether the two bought the same thing is an open question here, not a finding. | Palo Alto Networks |
| Coupa → Rossum | Execution-context | 12 May 2026 | Announced 12 May 2026 | Undisclosed COMPANY CLAIMTerms undisclosed; dates from the acquirer's release. Document understanding bought into a spend-management workflow — the context layer that makes agent execution auditable. | Coupa |
| Dynatrace → Arize | Assurance | 13 August 2026 | Pending close as of 25 August 2026 | $915M, company-announced COMPANY CLAIMFrom the acquirer's own investor-relations release, verbatim: “Dynatrace will acquire Arize for $915 million, subject to customary adjustments, consisting of approximately $815 million in cash as well as replacement equity awards for Arize employees joining Dynatrace.” Recorded as approximate rather than exact because the headline is stated subject to customary adjustments and the cash component is itself stated as approximate; an exact figure would have to come from a purchase-price allocation after close, as the CrowdStrike/SGNL row shows. Definitive agreement of 13 August 2026, with the transaction “expected to close later this quarter or early in Dynatrace's third quarter” — announced is not absorbed, and no close had occurred as of 25 August 2026. The first row here to carry the assurance layer: the release describes Arize as “a unified AI observability and LLM evaluation platform” and its work as helping teams “detect hallucinations, measure output quality, and continuously validate AI behavior”. Explicitly not counted in R01.5, whose test is absorption into IAM and hyperscaler incumbents: Dynatrace is an application-performance-monitoring incumbent and is neither — the same reasoning already recorded for the Cyera/Oasis Security exclusion — so the absorption count stays at seven. The registry row is deliberately broader than the signal, which is why it is written down here and not scored there. Arize has published no revenue figure of any size, so R01.5's independence side cannot be measured from this row either. | Dynatrace |
Six of the eleven are completed; the other five are announced, agreed or pending close. Three carry a price the buyer itself put its name to, and only one of those three comes from a filing rather than a release. Signal R01.5 reads this table, not the other way round — and reads only part of it: the rail-routing, execution-context and assurance rows sit outside its two-sided test, so neither row added on 25 August 2026 moves its absorption count.
Verdict registry
The fourth registry — public claims adjudicated with their named owners, verdict and reasoning — went live with Thesis 02 on 18 August 2026. The rule that kept it unpublished until then still governs every row: a claim cannot be adjudicated here until its owner is quoted, because adjudicating an unattributed claim is arguing with a strawman. Verdicts are yes, no, refine or retired, and a retirement is written down with its date and its reasoning rather than deleted.
| Claim | Owner, where and when | Verdict | Reasoning | Adjudicated in | Source |
|---|---|---|---|---|---|
| “The collaboration layer becomes the moat”Quoted verbatim. The surrounding sentence reads that when value increases from multi-human and multi-agent collaboration, switching costs rise. | Alex Immerman, partner, Andreessen Horowitz (Growth) — a16z, Big Ideas 2026: Part 1, vertical-AI section, 9 December 2025 FORECASTPublished as an explicit prediction for 2026. Incentive at point of use: a16z invests in the application and vertical-AI layer the claim advantages. | Refine | The owner's own stated mechanism is coordination across stakeholders with distinct permissions, workflows and compliance requirements — a description of permissioned canonical state, one layer below the collaboration surface he names as the moat. Six vendors reached the shared-agent product shape between 25 September 2025 and 1 July 2026, and the general manager of the host surface conceded at the launch that a lot of the capabilities did exist and the form factor is what changed. Not a no: no public measured retention or switching evidence attributable to a shared surface exists as of 18 August 2026, so the moat claim is an argument rather than a measurement — and so is the refinement of it. Falsifiers: signal R02.1 and CALL A. | Thesis 02 | a16z |
| “We believe in AI being ‘multiplayer’ by design.”Quoted verbatim, with the causal version from the same interview: the future of the agentic enterprise will only be realized if agents can work independently and with multiple people, versus just a copilot. | Arnab Bose, Chief Product Officer, Asana — Computerworld, interview by Matthew Finnegan, 1 April 2026 COMPANY CLAIMIncentive at point of use: the chief product officer of a work-management vendor arguing that his category is structurally advantaged. | Refine | The defensible asset is the accumulated shared state, roles and conventions a team has invested in, not the multiplayer surface as such — and the owner concedes it in the same interview, saying the benefit accrues through the underlying work graph even where the customer never opens his product's interface. Corroborated from a different category by a storage vendor's chief executive, who defends software on determinism and agent access governance rather than on multiplayer. Because the owner concedes, this row reads as agreement rather than adjudication, which is why it runs second. Counter-datum requiring verification before any further use: this vendor's dollar-based net retention reported at 96% for Q4 FY2026, sourced from search summaries only. | Thesis 02 | Computerworld |
| “Claude Tag is the first multiplayer AI from a frontier lab”A claim in circulation with no locatable owner. Recorded here because the ledger-integrity rule forbids deleting a row quietly. | No owner found — two researchers independently exhausted the owner leads on 18 August 2026 INFERENCEThe vendor's launch post of 23 June 2026 uses the word multiplayer and carries no superlative; the product page, help centre and documentation carry none either. Four outlets covering the launch assert no industry first, and several place the product inside an existing field. | Retired | Retired on 18 August 2026 with the reasoning stated rather than the row deleted. The only first-claim located anywhere is scoped to the vendor's own product line, not to the industry. On prior art the claim would fail regardless: a consumer assistant in group chats from 27 September 2023, a copilot in team group chats generally available from February 2025, consumer group chats from 13 November 2025 and shared workspace agents from 22 April 2026 all predate it. Three article bodies were unread at retirement and are flagged for the author to verify; if any of them carries an industry-first claim by a named writer, this row publishes as a clean no on prior art instead of retiring. Superseded by the first row above, which adjudicates the same underlying question with a named owner. | Thesis 02 | No attributable source |
| “Claude Code, Cowork, and chat are very single-player, whereas Claude Tag is built to be interactive and multiplayer.”Quoted verbatim. Recorded, and used inline in the thesis rather than run as a third verdict block: two blocks is the ceiling, and a third turns the format into a rubric. | Cat Wu, head of product for Claude Code and Cowork, Anthropic — quoted by Beatrice Nolan, Fortune, 23 June 2026 COMPANY CLAIMIncentive at point of use: a vendor characterising its own prior products as deficient in order to position a new one. That is marketing, and it is admissible against interest as to the historical gap. | Yes | The strongest available evidence that the subscription harness had no multiplayer mode, stated on the record by the vendor's own product lead, in a named outlet, by a named journalist. Scope limit that must not be blurred: the sentence covers this vendor's products only. It says nothing about the competitor that shipped shared, permissioned, Slack-deployable workspace agents on 22 April 2026, or about the incumbent whose copilot had been generally available in team group chats since February 2025 — so it supports no industry-first claim. | Thesis 02 | Fortune |
| “The increase in consideration from the $5 million Opening Bid to the $10 million Successful Bid … confirms that the value of the Deidentified Data was tested.”Quoted verbatim from the banker's declaration in support of the sale; adjudicated in Note 02. | Dylan Friesner, PJT Partners, banker to the debtors — declaration in support of the data sale, In re Spirit Aviation Holdings, No. 25-11897 (SHL) SDNY, ECF 1470, filed 17 August 2026 COMPANY CLAIMIncentive at point of use: the estate's own banker attesting that the estate's process was robust, because approval turns on it. Adjectives read as advocacy; the auction numbers read as measurement. | Yes | Three bidders qualified, the $5 million opening doubled inside an afternoon, and the alternate bidder, Mercor, stood at $7.5 million on different deidentification terms — one buyer naming a price is a whim; two qualified bids within a third of each other are price discovery, the first real price range on a company's operational memory. The sale itself remains contested and unapproved, with the hearing adjourned to 9 September 2026; the verdict covers the claim that the value was tested, not the sale's outcome. | Note 02 | SDNY docket (Epiq) |
| “We've achieved peak data and there'll be no more.”Quoted verbatim, with two further sentences from the same talk: “Pre-training as we know it will unquestionably end” and “We have to deal with the data that we have. There's only one internet.” Two other sentences widely attributed to the talk are not verbatim in the report and are not carried here. | Ilya Sutskever, OpenAI cofounder and former chief scientist — talk at the Conference on Neural Information Processing Systems, Vancouver, 13 December 2024, as reported by Kylie Robison for The Verge, 14 December 2024 PRESS-REPORTEDA reporter's transcription of spoken remarks; no published transcript exists. The claim predates the evidence window of the thesis that adjudicates it, and one clause settles why it is adjudicated anyway: a verdict adjudicates a standing public claim rather than an event, and its owner restated it inside the window — “we're moving from the age of scaling to the age of research”, 25 November 2025. | Refine | The stock of text did not run out; it stopped being what buyers pay for, because an archive amortizes into the weights while a checked outcome and a corpus nobody published do not. An exhaustion frame predicts scarcity pricing across text supply, and the filings show the opposite shape: the sellers of archives are contracting — one stock-image issuer's data-access line fell 66.7% year over year in the June 2026 quarter, another's data offering fell 26% in the half beside a $173.7m goodwill impairment, an academic publisher's revenue fell 6.1% because a prior-year non-recurring data contract did not repeat, and one platform's long-duration licensing backlog fell 36% in six months — while a seller of the present added term, its calendar-2027 commitment rising from $27m to $40m over the same six months. That is amortization, not exhaustion. Falsifiers: signals R03.2, R03.3 and R03.5, and CALL A (Thesis 03). | Thesis 03 | The Verge |
Six rows publish; the working file holds eight. The two that do not publish are earlier drafts of the third and second rows above, written before an owner could be established for either — one an ownerless first-claim, the other a constructed composite with no single speaker. Both are recorded as superseded with their dates rather than deleted, which is the same rule that keeps the retired row visible here.
A second candidate for this release cleared its dating condition on 24 August 2026 and was still not run: the published thesis carries one verdict block, so no row is opened for a claim that was not adjudicated in print.
Data deals registry
The fifth registry — transactions in which a body of data changed hands — opens with Thesis 03 on 24 August 2026. It exists because there is no other public record of what a corpus sells for: accounting does not recognise internally generated data, so until a company is sold there is no observed price for the thing it produced while working. Each row carries the channel it came through, the price and how the price is known, where the transaction stands, and the condition attached to using the data. Channels are acqui-data (buying into the manufacturer), salvage (an estate sale), brokerage (buying the intermediary) and licensing (a contract with a living seller).
| Deal, buyer and corpus | Announced | Price | Use restriction | What it establishes | Source |
|---|---|---|---|---|---|
| DD-001 · Meta Platforms ← Scale AIChannel: acqui-data. A non-voting minority of the outstanding equity of a manufacturer of human-generated labeling, expert and preference data for frontier post-training — a position in the producer rather than a purchase of a corpus. The founder moved to the buyer. | 12 June 2025Status: completed · closing month only, no exact date in any primary | $13.79bn MEASUREDThe filed figure is the consideration allocated to non-marketable equity investments in the buyer's own Form 10-Q, which states verbatim that it acquired a “non-voting minority” and booked the stake under the measurement alternative “as we do not have significant influence over Scale AI's operations”. A total consideration of $14.3bn and a 49% stake circulate widely and appear in no primary; the seller's own announcement discloses only a valuation above $29bn and “a minority” of equity. | None disclosed. The buyer records no votes and states it has no significant influence. | The first form of the inversion: a buyer taking a position in the manufacturer rather than buying a corpus. The caveat that matters is that the two figures everyone repeats are not the filed ones. | SEC EDGAR |
| DD-002 · Google ← Spirit Aviation Holdings estateChannel: salvage. The deidentified operational and employment record of a liquidated airline, enumerated system by system in an assets schedule: repositories, pull requests, commits, pipeline logs and test results, revenue transactions from May 2008, booking curves and refund histories. | 17 August 2026Status: contested-court · sale not approved, hearing 9 September 2026 | $10,000,000 MEASUREDThe auction result as filed: $10,000,000 successful and $7,500,000 designated alternate, from the notice of auction results on the public docket. Offers made during the auction and the designated alternate bid are different things and are not collapsed here. | De-identification performed by an agent the buyer selects, “while preserving referential integrity across the data set”, with the buyer bearing that cost and no reduction in price. The identical clause appears in the mirror alternate agreement, so it is two buyers’ revealed preference rather than one seller’s term. | The first arm's-length price for one company's whole operational record, set at auction and filed on the court record. The caveat that must travel with the number: the sale is contested and was not approved, so this is a bid on the record rather than a closed transaction. | SDNY docket (Epiq) |
| DD-003 · TTAM Research Institute ← 23andMe estateChannel: salvage. Consumer genomic and health data together with the operating business — roughly 13 to 15 million customers, a count that varies by source and is carried as approximate. | 4 June 2025Status: completed · approved 27 June 2025, closed 14 July 2025 | $305,000,000 COMPANY CLAIMThe winning bid at the reopened auction, disclosed by the debtor in its own release. The first round had closed at $256m to a different bidder before the court reopened it. | Binding post-closing commitments to state attorneys general: existing deletion and opt-out rights honoured in perpetuity, customer notice before closing, a consumer privacy board within 90 days, new privacy procedures, and annual reports to the states. | The consumer-data precedent, and the comparison that shows how differently the same statute behaves when the payload is personal: a court-appointed privacy ombudsman and binding conditions. Read beside the 2026 breach settlements, the sale realised roughly 4.7 times what the privacy liability cost. | Debtor release |
| DD-004 · Cloudflare ← Human NativeChannel: brokerage. An AI-data marketplace — the intermediary itself rather than a corpus: rights-holder catalogue, deal flow and licensing infrastructure. | 15 January 2026Status: completed | Not disclosed INFERENCENo price was published by either party and none has been reported. The row records an unpublished price as unpublished; the badge marks the absence rather than a figure. | Not applicable — the transaction bought the marketplace, not a licence to a body of data. | The flagship independent AI-data marketplace absorbed inside roughly twenty months by the party that already owned the request path its business depended on. What it establishes is the direction of consolidation in this layer, not a valuation. | Acquirer release |
| DD-005 · Two undisclosed counterparties ← RedditChannel: licensing. Platform-wide content licensing for AI training and grounding, under agreements the issuer describes only in aggregate. | 22 February 2024Status: completed · agreements entered January 2024 | $203.0m MEASUREDAggregate contract value as disclosed in the Form S-1 filed 22 February 2024. The figure sits outside the evidence window of every publication in this series and is restated in no later filing, so it never appears without that date attached. The in-window sentence that does the same work is the issuer’s risk language, that “substantially all of the contract value associated with our licensing revenue is derived from two of our partners”. | Not disclosed. The issuer publishes no counterparty names, no term, no per-unit rate and no use conditions in any filing. | The licensing channel's only aggregate figure disclosed by a seller in a filing — and it is now two years old and has never been restated. The counterparty pairing that circulates is not a company disclosure. | SEC EDGAR |
Five rows publish and the working file holds five: this registry opens with everything it has. Two disciplines govern it. The first is that a price is meaningless without the condition attached to it, which is why the use-restriction column is a column. The second is that status is printed in the table rather than explained in prose, so a contested sale is never rendered as a completed one.
Open core
The current state of this ledger is public and stays public: definitions, thresholds and the latest reading for every signal, free to read and to cite with attribution. That is the core, and the core is never closed.
What may eventually be sold is depth rather than access: the full reading history behind each signal, machine-readable exports of it, a queryable interface over it, alerts when a threshold is crossed, and work applied to one organization's own question. If that layer ever exists, this page keeps working exactly as it does today.
Corrections, better sources and threshold arguments are welcome on LinkedIn.
The Agents & Margins briefing is launching — until then, follow on LinkedIn
Sources
- 1.HUMAN Security — State of Agentic Traffic, June 2026 edition, published 6 July 2026, with the April and May 2026 editions. No July 2026 edition had been published as of 17 August 2026.
- 2.ICONIQ — 2026 State of AI Report: The Builder's Economy, July 2026 (~300 executives), and State of AI: Bi-Annual Snapshot, January 2026 (N=297 for pricing, N=269 for margins).
- 3.Growth Unhinged — The 2026 State of B2B SaaS and AI Monetization Report, published 13 May 2026; more than 230 self-selected B2B software and AI companies, fielded April–May 2026.
- 4.Published vendor pricing pages and product documentation for the five vendors tracked by R02.3, all read 18 August 2026 — Anthropic (Claude Tag documentation) and Anthropic pricing, Asana, Microsoft, plus the Google Workspace and OpenAI pricing pages, which returned a non-USD currency and HTTP 403 respectively to the research workstation and are marked author to verify.
- 5.Bessemer Venture Partners — The State of AI 2025, 13 August 2025.
- 6.Salesforce — Q1 FY2027 results, 27 May 2026, taken as the anchor release for R02.2; the other cohort disclosures behind the reading are dated in the row itself, from 30 April to 10 August 2026.
- 7.NIST NCCoE — concept paper, Accelerating the Adoption of Software and AI Agent Identity and Authorization, posted 5 February 2026; comments closed 2 April 2026.
- 8.Agentic AI Foundation (Linux Foundation) — Model Context Protocol specification 2026-07-28, with authorization hardening; Microsoft Entra Agent ID reached general availability in April 2026 and Agent 365 on 1 May 2026.
- 9.Notion — release notes of 1 July 2026, external agents at general availability, taken as the anchor release for R02.4, with the Microsoft Work IQ general-availability note of 16 June 2026 and the Agent2Agent membership announcement of ~9 April 2026 behind the same reading.
- 10.Zendesk — completed acquisition of Forethought, 26 March 2026, taken as the anchor release for the bundling signal; the other transactions behind the reading are recorded row by row in the agent M&A registry above, each with its own source and disclosure label.
- 11.Anthropic — Claude Tag launch post, 23 June 2026, taken as the anchor release for R02.1; the other four harnesses in the census are read from their own newsrooms, changelogs and product documentation and dated in the row. The two later readings, dated 26 and 27 August 2026, rest on two further primaries: the founder statement posted on X on 26 August 2026, and the deepagents-code release notes, read together with the release notes and product documentation of the other fifteen harnesses in the sixteen-harness census.
- 12.Anthropic — Claude for Small Business, 13 May 2026, taken as the anchor release for R02.5, read together with the Claude Tag documentation on per-channel service accounts and the vendor-hosted sandbox.
- 13.Gartner — worldwide AI-optimized IaaS spending forecast, press release 10 August 2026.
- 14.ECF 1463, Notice of Auction Results for the Deidentified Data, filed 14 August 2026 in In re Spirit Aviation Holdings, Inc., et al., No. 25-11897 (SHL), United States Bankruptcy Court for the Southern District of New York — the results table ($10,000,000 successful, $7,500,000 alternate), the mirror alternate sale agreement carrying the identical referential-integrity clause, and the exhibit naming the alternate bidder's own upload facility. Filings are free at dm.epiq11.com/case/spirit. The sale was not approved; the hearing is set for 9 September 2026.
- 15.SimpleClosure — Asset Hub launch, 16 April 2026, the source of the roughly 100 transactions, the $10,000–$100,000 band and the description of the buyers. The company's H1 2026 shutdown report of 20 August 2026 carries no Asset Hub transaction figures at all, so those three data points remain sourced to April. Company claims.
- 16.Reddit, Inc. — Form 10-Q for the quarter ended 30 June 2026, filed 31 July 2026, and the Form 10-K for FY2025, filed 6 February 2026: the remaining-performance-obligation balances behind R03.2, the note that the balance consists primarily of long-term content licensing, and the renewal risk language.
- 17.The metered and per-use tier, read 24 August 2026 — Cloudflare's pay-per-crawl documentation (“closed beta”, last updated 28 July 2026) beside its pay-per-use direction statement of 1 July 2026; Microsoft's Publisher Content Marketplace announcement of 3 February 2026; ProRata's published Gist split; Perplexity's Comet Plus publisher pool; and TollBit's realisations, which reach the public only through journalism. The cohort of six is fixed at first reading and does not change between Scorecards.
- 18.The buy-side intake pages, read 22–24 August 2026 — micro1's data-partnerships page (tiers at $100k, $500k and $1m-plus, a $5m referral programme paying up to $25,000 per company introduced, and eligibility criteria of 30 or more employees with documentation in English) and Mercor's data page (referral payments up to $100,000). Company claims; both companies buy the supply they describe.
- 19.Anthropic — Claude Opus 5 system card, 24 July 2026, the source of the four named training-data categories and of the roughly 1.5 million reinforcement-learning episodes across thousands of training environments, read together with the consumer-terms update of 28 August 2025 that has permitted training on assistant sessions since. Company claims; the other four cards in the R03.5 census are read from their own publishers.
- 20.Spencer Fane — The New Distressed Asset, 7 July 2026, the strongest adjacent evidence on the sell side and a practitioner claim rather than an offering: “a genuine buyer market that did not exist five years ago” for accumulated corporate data pools, written without reference to any named case. Law-firm publishing is marketing, and the row that cites it says so.
- 21.Andreessen Horowitz — Big Ideas 2026: Part 1, 9 December 2025, vertical-AI section; the source of the claim adjudicated in the verdict registry and of the base rate cited against CALL A.