ProvenanceGuard
← Go back

§ ASSET TRANSFORMATION LINEAGE · AI IMAGE PROVENANCE STRIPPED BY INSTAGRAM

Every step of an asset's life — what's verified, and what is honestly unknown.

Open a lineage for an image: the origin entry records its real SHA-256, its source reference and ProvenanceGuard's signed assertion. Each transformation appends a link (before hash → after hash, kind, actor, time). Links whose bytes ProvenanceGuard holds are verified by recomputing the hash. A step that happened outside — a platform stripping metadata on upload, an edit in another tool — is recorded as unknown: stated as unknown, never upgraded to verified.

§ Open a lineage — free, no account

Honest limits: the signed assertion is a ProvenanceGuard XMP assertion (HMAC-signed), not a C2PA manifest. Declared external steps are recorded exactly as declared — ProvenanceGuard cannot verify what it did not execute and does not hold.

§ What a lineage looks like (example — illustrative, not a real asset)

StepHash chainStatusWhy
0 · Origin — asset registered— → a1b2c3…VerifiedSHA-256 recomputed from the held origin file matches the record; signed assertion valid.
1 · Strip metadata (local, real)a1b2c3… → d4e5f6…VerifiedExecuted here on the held bytes; output held and re-hashed.
2 · Published to Instagram (declared)d4e5f6… → —UnknownThe platform stripped the metadata and no output file was returned — nothing can be recomputed, so this link is stated as unknown.

That third row is the point: after metadata is stripped by an outside platform, provenance tools usually go silent or guess. A ProvenanceGuard lineage keeps the chain readable and labels the gap as a gap.