---
name: tbt-image-content-credentials
description: "Distinguish recorded editing history from accurate depiction or likeness approval for Read Content Credentials without mistaking provenance for truth. Use permitted source material; this kit does not authorise external actions."
---

# Read Content Credentials without mistaking provenance for truth

Distinguish recorded editing history from accurate depiction or likeness approval.

Use the supplied source as authority. Check the account supports the actual file or image operation before attempting it.

## Task instruction

Summarise this permitted image's supplied source log and credential
viewer report. Separate: recorded creation/editing history, the viewer's
actual validation result, claims about the depicted scene or person,
appearance review and permission for the intended use.
Quote supplied status wording accurately. Mark missing evidence as
Not supplied or Unverified. Do not infer signed credentials from a
filename, watermark or screenshot, and do not call a generated scene
a factual photograph merely because provenance information exists.

## Source boundaries

- Issuer and actions if available
- Metadata may be removed
- Pixels still need review

## Review and correction

Content Credentials describe provenance where supported. They do not certify that a scene is true or an edit is faithful.

Your summary says [unsupported verification or truth claim]. The
supplied evidence establishes only [recorded fact/status]. Correct
that statement and keep credential validation, depiction accuracy,
appearance approval and usage permission separate. Preserve unknowns.
List the exact additional evidence needed for the unresolved question.

Use references/practice-source.json for the labelled example. The practice HTML is a local teaching tool; it does not call an AI service. Apply this method to the user's supplied facts rather than copying fictional example values. Do not infer approval or permission to publish.