Provenance Glossary: The Key Terms Behind AI Content Marking
By the Ingenious AI team · Published: November 14, 2026 · Reviewed: November 14, 2026 · 8 min read
The short answer
Use the words as the product uses them: an assertion is the signed statement; an exhibit is the registry record's public identity; a fingerprint is a hash of bytes or of pixels; survival is measured persistence through transforms; lineage is the hash-linked chain of stages; conformance is measured marking under a battery of transforms. Consistent vocabulary is not pedantry, it is what lets a record be read by a stranger without translation.
Teams argue about provenance most when they are using the same words for different things; a glossary is a cheap ceasefire.
The practical problem is distribution. An image is rarely published once, in one place, in its original form. It is uploaded to platforms that resize and re-encode it, forwarded by partners, saved and reposted by audiences, and archived by people who strip whatever context surrounded it. Each step is normal and usually innocent, yet together they separate the image from anything that said how it was made. Planning for that separation, rather than hoping it will not happen, is the whole discipline this guide is about.
What is provenance vocabulary? the working set of terms used across provenance tooling, assertion, exhibit, fingerprint, registry, survival, lineage, conformance, each defined by what the software actually measures or stores.
The problem behind the provenance glossary
No single layer does this job alone, and honest tooling says so. Embedded metadata can be stripped. A visible label can be cropped. A fingerprint can drift if an image is edited heavily. A registry entry proves registration, not authorship in a legal sense. Used together, though, the layers cover each other's failures: when the metadata is gone the fingerprint can still find the registry record, and when a copy is too altered to match, the labelled version and the evidence pack still tell the story.
ProvenanceGuard is built around those layers, and its wording is deliberately narrow. The free job inspects one JPEG or PNG, embeds a signed ProvenanceGuard assertion in XMP, produces a visibly labelled copy, registers the SHA-256 and perceptual fingerprints, and gives the asset a public verification page. The assertion is HMAC-signed and labelled accurately everywhere as ProvenanceGuard's own assertion; it is not a C2PA manifest and is never described as one.
How ProvenanceGuard handles it
Provenance is the record of where a piece of content came from and what has happened to it since: who or what created it, when it was registered, and which copies descend from the original. For an AI-generated image that record matters because the file itself is easy to copy, rename, crop and re-upload, and none of those actions leaves a reliable trace inside a filename. A provenance record kept outside the file, in a registry keyed to the file's fingerprints, survives exactly the handling that erases the signals embedded in the file.
Two kinds of fingerprint do two kinds of work. The SHA-256 is exact: change one byte and it changes completely, which makes it perfect for proving a copy is bit-for-bit the registered file and useless for recognising a resized repost. The perceptual fingerprints, computed from the pixels rather than the bytes, are approximate on purpose: they stay close when a copy is resized, re-encoded or lightly edited, and drift as edits accumulate. A good registry stores both and is honest about which kind of match it is reporting.
What survives distribution, and what does not
The registry model also disciplines what a match means. A fingerprint match says this image is the registered image or a close descendant of it; it does not say the person showing it to you owns it, and it does not say the disclosure attached to it was correct. Those judgements stay human. What the registry removes is the argument about identity and timing: which file, registered when, carrying which declaration. Most real disputes shrink considerably once those three facts stop being contestable.
The registry is the part that survives distribution. At sealing, the asset's SHA-256, its sealed copy's SHA-256, and its perceptual fingerprints are stored against a public exhibit ID. Anyone with that ID, or with the file's hash, can open the public verification page or query the verification API and confirm that this exact file, or a near copy of it, was registered, when, and with what declared creator and disclosure. Verification pages are public by design: a record only a vendor can check would not settle disputes.
A routine that survives busy weeks
Used inside those limits, the record is strong. Used outside them, by claiming a seal proves authorship in law, or that a simulation proves a platform's behaviour, or that a registry match proves ownership, the same record becomes a liability, because the first competent challenge will find the overclaim. The teams that get the most from provenance tooling are the ones whose public language is as precise as the tool's own: sealed, registered, verifiable, with the dates and hashes to show it.
The limits deserve the same prominence as the features. ProvenanceGuard does not detect deepfakes, does not judge whether an image is harmful, and does not verify that a creator's declared disclosure is true; it records declarations, binds them to fingerprints, and makes them checkable. Its signed assertion is its own XMP-embedded, HMAC-signed statement, explicitly not a C2PA manifest and not a certification by any standards body. Survival re-checks are local simulations of documented platform transforms, not actual uploads, and they are labelled that way in every result.
Five actions to take
- Adopt one glossary for the whole team and link it in your handbook
- Correct drifting terms in documents before they reach clients
- Download and keep both copies the seal produces: the sealed copy as the record, the labelled copy for publication
- File the exhibit's verification URL beside the asset wherever your team keeps campaign or client records
- Run check-a-copy on the version you actually published, and note which checks held: hash, signature, fingerprint
A worked example: A consultancy onboarding three new hires to its AI practice
The glossary became the first reading in its handbook; its effect showed a month later when a client call used VERIFIED, UNKNOWN and MISMATCH exactly as the lineage tool means them, and no time was spent translating statuses.
The lesson generalises beyond this case. Records made at publication time are cheap, calm and complete; records reconstructed under pressure are expensive, partial and contested. Everything in this guide is in service of moving work from the second category into the first.
FAQ
Why do definitions here differ slightly from other vendors'?
Because each is tied to what this product measures: its thresholds, its states, its formats. Where a term is a standard, like C2PA, the definition follows the standard; where it is a product feature, honesty requires the product's own meaning.
What formats and sizes are supported?
JPEG and PNG, up to 25 MB per file. Those are the formats the inspection, XMP embedding and fingerprinting are built and tested against; other formats are refused rather than approximated.
What does the free tier actually do?
The complete job on an asset: byte-level inspection, a signed assertion embedded as XMP, a visibly labelled copy, SHA-256 and perceptual fingerprints registered, and a public verification page. Paid plans add survival re-checks, evidence packs and bulk verification.
What do Pro and Team cost?
Pro is $29 a month and Team is $79 a month, as shown on the pricing page. Paid depth means per-platform survival re-checks, evidence pack export with EU, California and New York wording, and the bulk hash-verification API.