A creator can explain where an image came from.
They can name the model, the prompt, the edit, and the person who approved it.
That account may be entirely honest.
It is still not something a client, a platform, or a later recipient can inspect.
A claim lives in conversation.
A record lives with the file.
That distinction starts before the upload.
Content Credentials place a signed manifest beside an asset. It can hold the generating model, a timestamp, and an editing history.
The manifest doesn’t ask the next person to remember what was said.
It gives the next system something to read.
That is provenance.
A platform label is something else — a decision one intake point made, displayed after the fact.
Labels can be useful.
They are not the record that made the decision possible.
One tells a recipient what an originating platform chose to show.
The other can show a receiving system what tool and which edits are on file for this exact asset.
So don’t treat the checkbox as a chain of custody.
Because the binding is exact, and exactness is the whole point.
A manifest is tied cryptographically to one file. Not to your account, not to your caption, not to a copy that looks the same.
Take a screenshot and you have pixels with no signed relationship to anything.
Export to PDF and back, re-encode the image, or paste text through a field that rewrites it, and the binding breaks for the same reason.
The new asset needs its own inspectable record, or it has none.
This is also where provenance gets confused with watermarking.
A watermark hides an imperceptible pattern in the pixels or the audio samples, and a matching detector can find it again after ordinary handling.
A manifest carries a creation and edit history.
One is the record.
The other is what you have left when the record is gone.
Keep both straight, because a handoff usually needs more than an explanation.
Then give the asset its administrative record.
When was it created. Who last changed it. Who sent it, to whom, and when.
A hash can show whether the file changed between sending and review.
That establishes integrity.
It says nothing about permission.
Rights metadata answers what use is allowed.
Authorship answers who supplied the human creative control the work rests on — and in the United States, material generated without meaningful human creative control isn’t registrable, while human selection, arrangement, or substantial editing of generated elements can be.
An origin claim is not a rights clearance.
A hash is not an authorship claim.
Put each answer in the record that can actually carry it.
There is one more relationship worth writing down, and it is the one most often left to memory.
What is this version related to?
The crop, the translation, the revised export, the client delivery: each needs a plain pointer back to the source it came from.
Without it, a recipient gets two files and has to reconstruct the lineage from filenames, folders, and guesswork.
That is not a small inconvenience. It is how a corrected version and a superseded one end up looking equally authoritative.
So the useful handoff isn’t a larger pile of fields.
It is the small set a receiving system can read: the signed record, the integrity hash, the rights answer, and the source relationship.
Don’t make the recipient guess at any of the four.
Keep the source asset.
Keep the signed file when its record matters.
Keep the fields that say when it was made, who changed it, and whether it is still the same file.
Keep the rights answer separate from the authorship claim.
Keep the pointer from every version back to what it came from.
Then decide what may travel publicly.
Embedded camera data can carry precise coordinates and device serial numbers, and a public release can turn a useful internal detail into a location problem.
Preserve what a recipient needs in order to trust the work.
Strip what a recipient has no reason to know.
The account on the original platform may be complete.
The post may carry exactly the right label.
The asset can still arrive somewhere else alone.
Trust travels farther when the record travels with the work.