Evidence batches, signed loss adjustment reports, locked reinsurance submissions, inspection evidence, SIU outcomes, salvage disposals and reporting artifacts. Each record's SHA-256 fingerprint becomes a leaf in a merkle batch; the batch root is written to the hub-anchor program on RoxChain as a small program-derived account holding the authority, the batch reference, the root, the leaf count and the slot time.
Re-anchoring the same root is a harmless no-op; writing a different root for the same batch is refused by the program. Anchors never move value.
Drop a file on the verify page: your browser computes the fingerprint locally (the file is never uploaded), the registry finds the leaf, recomputes the root from the inclusion proof, and compares it with the live on-chain account. Match means this exact file existed, byte for byte, when the batch was anchored.
A one-byte change produces a completely different fingerprint, so a "not anchored" answer on a document that claims to be sealed is a warning sign.
The registry shows fingerprints, masked references (like CLM-2026-••847) and the anchoring insurer's display name. Claim numbers, policyholder names, amounts, medical and financial details are never published, a fingerprint reveals nothing about the file it seals.
During development and demos, some anchors were produced by a deterministic mock ledger or inserted by the demonstration seed. Those rows are labeled Mock ledger (RoxChain pending, D-018) or Seeded demo anchor on every surface and are never presented as chain proof. Only rows labeled RoxChain with a confirmed transaction are proven on-chain.