‹ Journal

Artificial identities · Lyfera · 2026-11-03

What an image can tell you about its own history

What a signed provenance record can establish about an image, what it cannot prove and why creative context remains an editorial responsibility.

Kwesi Boateng leaning on an escalator handrail in a monochrome imagined scene.

A file can travel farther than the explanation that first accompanied it. A fashion image leaves a studio, appears in a presentation, is cropped for a social feed and later turns up in an archive. Each version may look familiar, even when the person receiving it can no longer tell which work was approved, which details changed, or what the image was intended to show.

For an artificial talent, that uncertainty is not merely a question of whether a face is recognisable. A continuing identity appears across images, edits and formats. People working with it need to distinguish a dependable record of a particular file from a broader editorial account of the character and the decisions surrounding it. A digital signature can help with the first task; it cannot do the second on its own.

A record travels with an image

Content Credentials are one approach to making parts of a file's history inspectable. The C2PA explainer describes a manifest containing assertions about an asset and a signature that allows a compatible validator to check whether the declared information is associated with that asset and has been altered. Depending on what was recorded, the assertions may describe creation, edits, ingredients or the use of generative tools. What is present depends on the tools and choices involved; it is not a complete account automatically guaranteed for every file.

Imagine a fictional campaign portrait of an artificial talent standing inside a room whose wall blends into a shoreline. The image is an invented scene, not a photograph of a documented location. A production team prepares a version for a website and another for a presentation. If their workflow records the relevant actions, a compatible reader may be able to show a signed history associated with a particular version. That can help the recipient ask better questions about the file in front of them. It does not establish that the shoreline exists or that the character visited it.

Integrity is not the same as truth

The distinction is easy to miss because a successful verification can feel like an editorial verdict. The C2PA technical specification is explicit that validation concerns the association, structure and integrity of assertions; it does not judge whether their content is good or bad. A signed statement remains a statement. Its signer, the trust policy used by the viewer and the scope of the recorded steps matter.

The reverse is equally important. A file with no visible credential is not thereby proven false or human-made. The US Office of Research Integrity notes that an absent signal does not establish authenticity: files can come from tools that do not provide that signal, and a particular checker may examine only certain kinds of provenance. Absence should lead to a narrower conclusion: this check did not provide the information, so another source of context is needed.

The missing context is an editorial responsibility

A team can keep an internal record alongside any technical credential. For the fictional shoreline portrait, that might include the approved talent identity, the purpose of the image, the reference and wardrobe decisions, the version selected for the campaign and the fact that the room is imagined. The record can distinguish an approved image from an abandoned candidate without claiming that every creative decision is embedded in the public file.

Such a record also has boundaries. References may be private; people depicted or represented may have rights and expectations that a visible metadata field cannot resolve. A signature is not a substitute for permission, and a familiar face is not permission to invent a testimony. Lyfera's earlier discussion of the authority a portrait seems to carry considers what an audience may infer from an image. Provenance asks a related but separate question: what can be substantiated about the file and the way it was prepared?

Preserve the distinction when the file changes

Cropping, recompression and delivery through another platform can change a file. Whether its provenance remains available or verifiable depends on the software and implementation, so a team should inspect the delivered version rather than assuming a signal survived. Keep the approved source and an account of meaningful edits; when a delivery copy no longer exposes the information, say what is known instead of filling the gap with a claim of certainty.

For the imagined portrait, an editor might compare the source and website version, check the signed information if available and keep the approval record separately. The outcome may be useful even when no credential is visible: the team still knows which version it approved and can explain that the scene is constructed. Our essay on what a collector should be able to keep looks at preservation over time; the immediate decision here is what a recipient can reliably learn from a particular image today.

A responsible visual identity needs both kinds of attention. A record can make an image's declared history easier to inspect. Human editorial judgment still decides what the image implies, what the audience needs to know and which claims the available evidence can actually support.

Từ chối các công cụ tùy chọn không giới hạn quyền truy cập Lyfera. Google Tag Manager chỉ tải sau khi có sự đồng ý tùy chọn.

Lựa chọn của bạn được lưu trong sáu tháng dương lịch. Mục đích mới hoặc thay đổi đáng kể cần có lựa chọn mới. Đọc thêm.