Separate provenance, integrity, authenticity, attribution, and truth while examining manifests, signatures, Content Credentials, fingerprints, and watermarks.
Content provenance records an asset’s claimed origin and transformation history; integrity shows whether protected bytes changed; authenticity and attribution bind claims to an identity; none of those properties alone proves that the depicted or stated content is true.
The submitted report remains byte-identical. This separate review, checked 2026-08-26, narrows implementation claims and gives visitors a decision path before they generalize from a local result.
Output produced deterministically by the local runtime.
Useful model or subset that must not be mistaken for full conformance.
Conclusion that needs an exact implementation, trust system, model, parser, or human review.
| Question | What the local page can answer | What it does not establish | Next evidence step |
|---|---|---|---|
| Does the file contain selected provenance-related strings? | Yes — the byte scan reports exact occurrences. | A valid C2PA manifest or signature. | Use a conforming verifier and record its policy and trust inputs. |
| Is the signer trusted? | No trust evaluation is performed. | Identity, chain validity, revocation, timestamp, or trust-list acceptance. | Run an approved verifier with current trust data. |
| Is the media true? | No provenance mechanism can answer this alone. | Physical or semantic truth. | Corroborate with independent contextual and forensic evidence. |
Demonstrates structural metadata versus cryptographic verification and truth boundaries.
Expected boundary: The lab reports exact bytes and selected markers while refusing a validity verdict.
Open prepared laboratoryNo single view is automatically authoritative. Preserve the source, identify each parser or receiver, and compare their outputs before authorizing a consequential decision.
The exact file digest and detected media structure.
Claims, assertions, ingredients, actions, and bindings when structurally present.
Algorithm, certificate, and timestamp claims requiring cryptographic validation.
Watermarks or perceptual fingerprints designed to survive selected transforms.
Accepted issuers, identities, revocation, and verification time.
Separate contextual investigation outside the cryptographic claim.
The workflow preserves evidence before transformation and keeps structural inspection separate from execution, remote verification, or model behavior.
These controls are contextual. They reduce a defined risk; they do not guarantee safety, truth, attribution, or resistance to every adaptive attack.
Display structural, cryptographic, trust, and semantic states separately.
Avoid UI language that turns a valid signature into a “true” badge.
Minimize privacy-sensitive provenance assertions.
Preserve manifests through platform transforms where policy permits.
Use multiple validators and record version, trust list, and revocation behavior.
Definitions are linked into the site-wide glossary and back to the full report.
An auditable record of an asset’s claimed origin and transformations.
A structured container of claims, assertions, ingredients, and a signature.
A specific statement recorded inside a provenance manifest.
A source asset incorporated into a derived asset.
A root identity or authority accepted by a verification policy.
A cryptographic binding between data and a private-key holder.
A similarity-preserving descriptor used to associate transformed content with known records.
A hidden signal designed to survive specified transformations.
A signal designed to break when content changes.
These links are provided for visitors who want the governing specification, paper, framework, or implementation documentation. Links open in a new tab; the site does not fetch them during runtime analysis.
Organization and ecosystem overview.
First-party guidance, framework, registry, or standards-program material.Versioned technical specifications.
First-party guidance, framework, registry, or standards-program material.Provenance, watermarking, and detection taxonomy.
First-party guidance, framework, registry, or standards-program material.Public verification interface; use with stated trust and privacy limits.
Tool, vendor, or implementation documentation; behavior is version-specific.Publisher and tool integration guidance.
Tool, vendor, or implementation documentation; behavior is version-specific.Vendor description of cross-modal watermarking.
Tool, vendor, or implementation documentation; behavior is version-specific.Implementation and user-experience guidance.
Useful supporting material that does not replace the governing specification or original study.The full submitted report is preserved byte-for-byte in the governed research library and in durable repository documentation. The laboratory turns selected concepts into deterministic local output without external calls or hidden persistence.
A detailed separation of provenance, integrity, authenticity, attribution, truth, manifests, C2PA claims, trust models, editing chains, watermarking, fingerprints, synthetic-content detection, privacy, and verification limits.
Read governed reportInspect a bounded PNG or JPEG for digests, metadata, textual provenance markers, JUMBF/C2PA-like structures, and structural claims without performing cryptographic trust validation.
Open bounded laboratory