Protocol

Bind the review to the content it actually covered

A review of a filename can outlive the file it described. Save an exact version reference, and state what that reference covers.

A situation to tryIllustrative example

Attach the review to this exact thing.

A review approved a particular document. The file is edited afterward. What does the old review cover?

A working desk with a laptop, external drive, disconnected cable, papers and a coffee mug
Drive and cableThe reports

What would you try?

Two ways to look at it
Reviewed editionThe exact content covered by the review.
Current editionA changed file.

Try either move. Compare what it can tell you.

What if a credential excludes part of the file?

Keep its actual binding scope. Do not describe it as a whole-file check.

Some credentials bind selected bytes with exclusions. A matching identity does not establish truth, permission or approval beyond the stated scope.

Read the complete idea VedokrokSee a situation. Try a different move.

Before you use it

Use when
  • A claim says a document or file was verified but the artifact can later change under the same name or URL.

Keep this limit in mind

  • A hash proves content identity, not that the content is trustworthy or authorized.

Current editorial reading

Make the review recoverable

Record the artifact, its full-file hash and algorithm or immutable version, the review date, and the conclusion’s scope. Keep an authorized copy or a working route to that version. For example, a reviewed supplier specification can retain the same download link after replacement; compare the saved identity before carrying its review forward.

Check the binding’s scope

A signed credential is not automatically a whole-file fingerprint. C2PA content bindings can cover selected bytes and exclude others. If the review concerns the entire file, record its complete byte identity separately. If it concerns a defined portion, name that portion and the comparison method. A matching identity still says nothing by itself about factual accuracy or permission to use the content.

Take it with you

Before reusing a review, recover or compare the exact content it covered. A changed identity needs a new review decision; a familiar filename or valid signature is insufficient.

Sources and evidence (1)

What we checked

Limits

C2PA hard bindings can hash only part of an asset, with explicit excluded byte ranges.

Selected passages inspected on 2026-10-04. Recording a separate whole-file identity and a recoverable review copy is an editorial workflow recommendation, not a requirement imposed on every C2PA asset.

Content Credentials Specification 2.4 · Sections 4.2.1 and 11.5.1: byte-range hashing and data-hash exclusions

Editorial sources (1)

Editorial version 1.0.0 · Evidence checked 2026-10-04

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingBind the review to the content it actually covered

Original edition evidence and sources

These records belong to the original released edition. The current editorial reading has its own evidence above; neither set silently replaces the other.

Supports

C2PA assertions can record declarations about how an asset originated or was transformed and can be cryptographically bound to the relevant asset.

A cryptographically bound assertion establishes integrity of that assertion-to-asset relationship, not the truth of every declared fact.

Content Credentials Specification 2.4 · Assertions and content bindings

All sources (1)
Original edition, downloads and provenance

The reading above is editorial version 1.0.0, bound to this exact source edition. The original data and saved downloads retain that edition and the separate editorial layer. They may contain earlier wording; use the current reading above when interpreting it.

Version 0.1.0

No review details are supplied for this edition.

Read the original edition and overlay as JSON · Release details