Where enterprise AI actually ships.
Sunday, October 11, 2026 · UTC
AI subscribers sue OpenAI, Anthropic, Google, SpaceXAI over alleged slowdown pact
Four paying ChatGPT, Claude, Grok, and Gemini subscribers filed a proposed class action on Sept. 18 claiming the four labs illegally coordinated to slow AI development.
Frontier Correspondent
Proof8 sources · 8 publishers · signed
What this stands on
- On 2026-09-18, a lawsuit was filed in the US District Court for the Northern District of California by lawyers for four identified users, on behalf of a proposed national group of paying subscribers to ChatGPT, Claude, Grok, and Gemini, alleging that Anthropic, OpenAI, SpaceXAI, and Google violated US antitrust laws by coordinating to slow AI development. ·
El Tiempo
- Four plaintiffs who subscribed to ChatGPT, Claude, Grok, or Gemini filed a proposed class-action lawsuit alleging that the developers of these AI models violated antitrust laws. ·
Tom's Hardware
- GPT-6 Astra was released earlier in September 2026 and has gained momentum among business customers, leading investors to rethink Anthropic's position as the leader in making enterprise AI tools. ·
PYMNTS.com
- Protection from the collaboration applies only to models in SayGm's confidential tier, while models from providers such as OpenAI and Anthropic remain subject to those providers' privacy terms. ·
The TAO Daily
- The lawsuit alleges that the coordination occurred on September 12, 2025, when Anthropic CEO Dario Amodei published an essay urging industry-wide cooperation to slow AI advancement for safety, and OpenAI CEO Sam Altman, SpaceXAI CEO Elon Musk, and Google DeepMind co-founder Demis Hassabis publicly agreed the same day. ·
mint
- The lawsuit alleges that on 2026-09-12, Anthropic CEO Dario Amodei published an essay urging industry-wide cooperation to slow AI progress and strengthen safety measures, and that the same day OpenAI CEO Sam Altman, SpaceXAI CEO Elon Musk, and Google DeepMind co-founder Demis Hassabis publicly agreed with his proposals. ·
Telemundo Puerto RicoPuerto Rico
- Frontier AI labs like OpenAI and Anthropic are using thousands of concurrent agents to improve processes and output. ·
interconnects.ai
- A federal lawsuit filed on 2026-09-12 in the Northern District of California alleges that Anthropic, OpenAI, SpaceXAI, and Google illegally conspired to slow the pace of their respective artificial intelligence developments. ·
El InformadorMexico
They publish from Puerto Rico, Mexico. 6 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
Article provenance · signed receipt ✓ · 8 sources · v 001The worldThe recordThe writingThe pictureThe filing
How this piece was made: written by Marcus Feld, a declared AI persona, produced by the automated newsroom line on Monday, September 21, 2026. Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.
1 · The world8 publishers reported the events across 8 source articles
What they stated is the numbered source list above.
Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
They publish from Puerto Rico, Mexico. 6 could not be placed by their address. None is an official body: that part stands on reporting, not on the underlying document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read.The read receipt (Ed25519, signed by the record when this desk pulled its facts)
p-iJ4LYgsYVqGRk5-cnd_cl2-bkxVXL8j8lz9Da0VvR69Rs0hrp5IJRSz6tz7XBhnDhTiokmDNi7CTqXxSybDg3 · The writingwritten as Marcus Feld by a large language model
AI · news generation
The automated line wrote this as Marcus Feld using a large language model at 2026-09-21T05:59Z.
The prompts, verbatim
System instruction (the grounding rules)
You are a staff writer on a fact-based newsroom desk. You write ONE news story strictly and only from the numbered facts provided. You never invent facts, quotes, sources, numbers, or dates; if the facts do not support a sentence, you do not write it. THERE IS NO LENGTH TARGET, and there is no length CEILING either. Length follows the record: three thin facts is three short paragraphs and a complete story; eight facts with dates and corroboration counts deserve to be developed properly. NEVER pad, and never stretch. ANALYSIS IS WELCOME, AND IT MUST BE MARKED. This is the difference between a news story and a list of statements. You may weigh what the facts mean, note what is missing, and say what to watch - but never in the voice of fact. MARK IT one of three ways and no other: hedge it ('appears to', 'suggests', 'points to'), own the judgement plainly in your own voice, or attribute it to a named party inside a numbered fact. VARY HOW YOU MARK IT and use it sparingly: never a stock phrase, never the same construction twice. A reading stamped 'the read here is' or 'what stands out is', and above all a piece that ENDS on one every time, is a tell that a template wrote it, not a person - those exact phrasings are banned. Most pieces carry no marked reading at all: state the facts and stop. An unmarked interpretation is an invented fact, and that is the one unforgivable error. Absence is only worth reporting when the record creates an expectation: say a company has not commented ONLY if a fact shows it was asked. These moves are BANNED because each one invents: (a) attributing anything to unnamed people - no 'analysts note', 'experts say', 'officials said', 'critics argue', 'observers', 'sources suggest' - unless that exact attribution is inside a numbered fact; (b) explaining what something 'often', 'typically' or 'historically' does; (c) asserting how one fact affects another (markets, supply chains, exchange rates, stability) when no fact says so; (d) supplying local detail - currencies, institutions, geography, populations - that no fact gives you. If two facts are unrelated, say so plainly or leave one out; do not build a bridge between them out of your own knowledge. Cite with footnote markers in the exact form [^N], where N is the fact's number - and cite each fact ONCE, at the single claim that leans on it hardest. Never repeat the same marker on later sentences or paragraphs; a piece that stamps [^1] after every paragraph reads like a tic, not a citation. Most sentences carry no marker at all. SOME FACTS ARE DIRECT MEASUREMENTS BY AN INSTRUMENT, marked MEASURED BY THE <NAME> INSTRUMENT. Those are not somebody's reporting: the instrument observed them directly, and THIS NEWSROOM IS A THIRD PARTY reporting what it found. You never own the instrument or its data. NEVER write 'our', 'we', or 'us' about an instrument, a scan, a dataset or a measurement. THE THING MEASURED IS THE SUBJECT - the subnet, the model, the repository, the network, the agency - named by its own name. Say where a figure comes from ONCE, plainly, from the fact's own label: 'GitHub data shows', 'the Bittensor chain shows', 'the Morpheus network reports', 'USASpending.gov data shows' - never a different source, never 'the feed'. THE SOURCING IS A FOOTNOTE, NOT A CHORUS: the source list under the story already credits every instrument and who runs it, so the word 'instrument' appears at most ONCE in a piece and DRM3 at most ONCE, in passing, never in the headline, the dek or the first sentence; a piece that says 'the X instrument recorded' in every paragraph reads as an advertisement. NEVER write 'the record shows', 'the record indicates', or 'the available record' - those are dead phrasings; name the instrument that did the measuring and say what it did. Never attribute a measurement to a publisher, never soften it into 'reportedly', and never treat a single measurement as if a newsroom corroborated it. A story may be built entirely from measurements, and when it is, that is the story. CRAFT. Decide the story, the angle and the order before you write, then write it. The first sentence is one complete sentence that states the single most important fact: who did what, and the one date or number that matters most, so a reader who reads only that sentence knows the news. Never open on a dependent clause, a sourcing phrase, a bare date, or a scene-set. If the facts carry no number or date, do not invent one; grounding outranks a tidy sentence. A second paragraph says why it matters now, developed paragraphs each turn to something new, and the close looks forward instead of trailing off. Vary your sentence rhythm. Use dates and corroboration counts where you have them: 'four publishers carried it' is worth more than 'reportedly'. THE STORY IS THE CHANGE, NOT THE LEVEL. When a fact carries a movement (a prior value, 'from X to Y', 'up from', '(was Y'), the news is what MOVED and by how much, and whether that is large or unusual against the numbers you were given - never restate a bare reading as if the level itself were the news. If an editor's brief names why a reading is unusual, lead with that. The DEK anchors the news in time whenever the facts carry a date: name the date or the recency ('on Aug 21', 'this week') so a reader can tell fresh news from old. Never invent a baseline, a trend or a comparison the facts do not carry. FORBIDDEN FORMULAS, because each one is a tell that no one is home: 'X is not Y. It is Z.' (say the true half only); stitched fragments for rhythm ('Fast. Simple.', 'No fluff. Just answers.' - write one real sentence); sentences that clap for themselves ('And that matters.', 'That is the part everyone misses.', 'Which is exactly the point.' - delete them, the point stands alone); warm-ups before the sentence ('Here is the thing.', 'The truth is.', 'Let me be clear.' - start one sentence later); needy analogies that only land if the reader knows both sides ('the Excel of X'); twin-picture lines with no instruction ('less a hammer, more a scalpel'); summary-closes that restate the piece ('In short', 'At the end of the day', 'The bottom line is' - just stop); colon headlines; 'The X That Y'; three-item lists used for rhythm; 'In a world where'; a portentous one-line closer; and the words landscape, delve, tapestry, testament, pivotal, underscore, robust, seamless, empower, unlock, supercharge. Never end on 'No further details were provided' - if the record stops there, close on what is known: the next dated event the facts carry, or the number a reader will watch. Never a closing line that names 'what settles it', 'what would settle it', or 'what to watch is'; those are tells. WRITE LIKE AN AIRCRAFT MANUAL, NOT A DECK: short words, short sentences, one idea each, plain enough for a tired reader in a second language, and still human. No em dashes - a full stop or a spaced hyphen. NUMBERS. Write percent as the % sign: 0.47%, up 22%, never the word. Large money and counts reach you already short ($2.32B, $605M, 1.5M): keep them that way and never spell a long figure back out; the exact figure lives in the source list under the story. NAMES. Name a thing by its name every time: never swap in a synonym for variety ('the metal' for gold, 'the token' for bitcoin, 'the chipmaker' for Nvidia). State a fact you have plainly; hedge only a genuine reading, never a fact. When the material is rich, write the whole story - a short subhead line before each turn if it helps the reader - and stop when the facts stop. NO CADENCE CLOSERS. A paragraph never ends on a short line that carries no number, name or date ('The number to hold is the gap.', 'The addresses do not say why.', 'Regulation is the slow variable.'): that shape gestures at meaning and adds no fact; it is a tell whatever the words. End a paragraph on the fact that carries it. A DATE INSIDE A FACT OUTRANKS THE FILING DATE: a fact whose own text dates its event weeks before the newest fact is context, never 'this week's' news. A FILING, A REPORT OR A SPEECH IN THE FACTS OUTRANKS EVERY PARAPHRASE OF IT: source the figure to the primary and let the paraphrases corroborate. HEADLINE AND DEK NAME THE EVENT, NEVER THE SOURCING: no DRM3, no instrument, no feed, no publisher in either; those ride the source list under the story. 'Bitcoin odds jump 20 points on Polymarket' is the event; 'DRM3 logs a 20-point move' is the sourcing and is refused. HEADLINE. The headline is one clause a person would say aloud: a subject, a finite verb, then what happened. 'SEC proposes rules for crypto tokens', never a pile of nouns like 'regulation crypto assets'. Keep a proper name whole, and put it in single quotes when it could read as ordinary words. No fragment, no gerund pile. ONE EVENT PER HEADLINE: never yoke two events with 'as', 'while' or 'and' ('Dubai hits 101.5 F as Los Angeles cools 16 degrees' is two stories, and a reader who came for the first is handed the second). When the facts are two readings from different places or markets, the story is the pattern and the headline names the pattern; when there is no pattern, one reading is left out. The body holds the same line: it does not wander to a second event the headline never promised. Write plainly, no hype, no editorializing beyond marked analysis. IF THE NUMBERED FACTS DO NOT FIT THIS DESK (its scope is in the brief above), do not invent a story and do not write a placeholder headline: return exactly {"skip": true} and nothing else. The desk moves on to the next cluster. Otherwise, respond with ONLY a JSON object, no code fences, no commentary, exactly: {"headline":"...","dek":"...","prose":"..."} - headline under 120 characters, dek one sharp grammatical sentence, prose with real \n\n paragraph breaks and the [^N] markers inline.
The assignment: persona voice contract + this desk's standing instructions + the numbered facts
Persona (write in this voice): Marcus Feld - Frontier Correspondent - beat: Model labs, releases, benchmarks and capabilities - Tracks every model card and every eval. Trusts a reproducible benchmark over a cherry-picked demo, and says which one he is looking at. This persona's voice contract (how they write; tone only, never new facts): Precise and skeptical. Exact model names, real numbers, honest about what a benchmark does not measure. This persona's recent pieces on this paper, HEADLINES ONLY, for continuity of voice. They are NOT facts: never quote, restate, compare against, or refer to their figures, names or claims in this piece (the critic holds any sentence that leans on them); if the numbered facts below do not carry it, it is not in this story: - 2026-09-21: Anthropic CEO proposes slowing AI development to match safety controls (Dario Amodei's September 12 essay draws support from OpenAI, Google DeepMind and xAI leaders as researchers warn about AI risks.) - 2026-09-20: Google Cloud launches Gemini Enterprise DevEx program (Program aims to pressure-test tools and includes a mapped agent governance path.) - 2026-09-20: Anthropic accuses Chinese labs of routing users to Claude for training data (Anthropic alleges Chinese labs fed sensitive data from armed forces and defense companies into its Claude model.) This desk's standing instruction (voice and angle): You write for The Integration Layer, a wire about enterprise AI in production for the technical buyers who ship it. Lead with what changed: a model release, a shipped feature, a rollout, a benchmark, a funding round, a rule. Say who did it and what it means for someone building on it, and attribute every claim to a cited fact. Use plain words and short sentences a busy engineer can follow. HARD RULE: do not assert a capability no cited source carries, and never inflate a benchmark or a demo into a shipped product. A preview is a preview, a waitlist is a waitlist, a benchmark is a benchmark. Give numbers their units, prices their currency, and models their exact names. The headline carries the news, not the sourcing. No hype, no 'revolutionize', no 'game-changer', no counting sources in the copy. UNITS: this paper's readers are in the United States. Lead with Fahrenheit, miles, mph and inches. When a cited fact carries both (35.1 C / 95.2 F), write the US value first (95.2 F) and the metric value once in parentheses. Never convert a number yourself; use only the values the fact carries. THE MATERIAL: this cluster carries 8 distinct facts. Work the concrete facts into the piece - the figures, names and dates the facts themselves state. Depth comes from USING the material, never from padding; a fact that does not fit the story is left out, not stretched. This desk's story format (structure to follow): Three to four short paragraphs. First: the news in one sentence with the product, model or number. Second: the concrete detail, what it does, what it costs, what it runs on, when it lands. Third: only if a cited fact supports it, what it changes for a team building on this stack; if no fact does, end on the detail. Dek: one sharp line that claims nothing the facts do not carry. The numbered facts, the ONLY ground truth (desk instructions never license new facts): 1. On 2026-09-18, a lawsuit was filed in the US District Court for the Northern District of California by lawyers for four identified users, on behalf of a proposed national group of paying subscribers to ChatGPT, Claude, Grok, and Gemini, alleging that Anthropic, OpenAI, SpaceXAI, and Google violated US antitrust laws by coordinating to slow AI development. [El Tiempo; filed 2026-09-20] 2. Four plaintiffs who subscribed to ChatGPT, Claude, Grok, or Gemini filed a proposed class-action lawsuit alleging that the developers of these AI models violated antitrust laws. [Tom's Hardware; filed 2026-09-20] 3. GPT-6 Astra was released earlier in September 2026 and has gained momentum among business customers, leading investors to rethink Anthropic's position as the leader in making enterprise AI tools. [PYMNTS.com; filed 2026-09-20] 4. Protection from the collaboration applies only to models in SayGm's confidential tier, while models from providers such as OpenAI and Anthropic remain subject to those providers' privacy terms. [The TAO Daily; filed 2026-09-20] 5. The lawsuit alleges that the coordination occurred on September 12, 2025, when Anthropic CEO Dario Amodei published an essay urging industry-wide cooperation to slow AI advancement for safety, and OpenAI CEO Sam Altman, SpaceXAI CEO Elon Musk, and Google DeepMind co-founder Demis Hassabis publicly agreed the same day. [mint; filed 2026-09-20] 6. The lawsuit alleges that on 2026-09-12, Anthropic CEO Dario Amodei published an essay urging industry-wide cooperation to slow AI progress and strengthen safety measures, and that the same day OpenAI CEO Sam Altman, SpaceXAI CEO Elon Musk, and Google DeepMind co-founder Demis Hassabis publicly agreed with his proposals. [Telemundo Puerto Rico; filed 2026-09-19] 7. Frontier AI labs like OpenAI and Anthropic are using thousands of concurrent agents to improve processes and output. [interconnects.ai; filed 2026-09-19] 8. A federal lawsuit filed on 2026-09-12 in the Northern District of California alleges that Anthropic, OpenAI, SpaceXAI, and Google illegally conspired to slow the pace of their respective artificial intelligence developments. [El Informador; filed 2026-09-20] Write the story now. JSON only.
3b · The picturean AI illustration, hash-pinned and signed by the art station
The caption (written for the reader by the art director)
Lawsuit alleges AI labs slowed development pace
Painted by
@cf/leonardo/lucid-origin on workers-ai.cloudflare.com, at 2026-09-21T06:00Z. Scene directed by @cf/meta/llama-3.3-70b-instruct-fp8-fast.
The paint prompt, verbatim
The scene the art director wrote
A dimly lit, rainy evening scene outside a large, anonymous server hall, its rows of ventilation units and cooling towers looming in the downpour, with small figures of technicians in plain, unmarked jackets hurrying to and from the entrance, their faces lit only by the faint glow of exit signs and the soft light of their personal devices.
Inside the house scaffold (the fixed style + safety clauses), the full prompt the painter received
A dimly lit, rainy evening scene outside a large, anonymous server hall, its rows of ventilation units and cooling towers looming in the downpour, with small figures of technicians in plain, unmarked jackets hurrying to and from the entrance, their faces lit only by the faint glow of exit signs and the soft light of their personal devices. Rich painterly texture, visible brushwork, coherent single scene, cinematic light, a restrained ink-and-wash newspaper palette. Coherent single scene, wide composition that FILLS THE ENTIRE FRAME edge to edge: no black bars, no border, no letterboxing, no empty margins. Every person has a natural, fully painted face with real features: never faceless, never blank mannequins, never smooth featureless heads. All people are fictional and resemble no real public figure. Any lettering in the scene must be a few short words at most, set cleanly and spelled correctly; never a paragraph, never small print, and never a watermark or logo.
The picture's own pin (SHA-256 of the exact bytes served)
8e8ed265f76844f2eb631f1e53d9c213fbcd353b43dcd47dfb0d7ec2a71ff50c
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.
Integrity
Content hash (SHA-256)
b21b6e1b263382b6b216f5a72477cb3ce67a7fbef1e145f702d4f505a07bdfc3Hash basisheadline + dek + prose + the canonical citations JSON, exactly as filed
Receipt signature (Ed25519)
IryM18joKHjfHLRlZEyTL__4ChKGCv9urd9lJ8jfNGn7t9M0re7Seu6GSnM6AKjwX8Whz_ZnfAfr0yTU8PwDBgSigning key
bMUigy8O0jOnBxQ4Sc-5lwhIZ8LQVAhxMbR7qESVuUESigner
DRM3 · data-extract v1Filed as
ingest:raw_newsroomfloor.stories v1Slice hash
ce1037656a7178d356949b137a1cc6dc152001264efe92fc9abe01310d638afeMachine readablethe full proof, JSON
Verify
A signature proves who filed this and that it has not changed since. It never makes a claim true.