🔒All inputs are processed locally in your browser. Nothing is transmitted, stored, or logged. Inputs disappear when you close the tab.

OCG-Industries Showcase · Cluster ⑬ Machine, AI and Software Integrity

Cross-Vendor Provenance
Interoperability

Enter the same asset's asset id, issuer, and creation day from two vendor provenance records, plus each record's source format. This tool checks how many of those three core fields agree, names the ones that don't, and tells you whether the pair maps cleanly onto a common join key. Vendors format their manifests differently, but if the core facts about the asset agree, the graph can still carry the lineage across formats. The core field set here is this demo's own minimal join key, not a ratified cross-vendor profile.

Data: C2PA Specification 2.1 · in-toto attestation framework · SLSA v1.0

Vendor Records STEP 1

Record A

Record B

Status
Interoperable, partial mapping, or unmappable
Fields Agree
Of 3 core fields
Format Pair
Source format A joined to B
Detail
Field agreement count
Disagreeing fields
Mappable
Format pair
Normalized digest (mutation detector, not a cryptographic digest)
Status
Policy Mandate v2.0 · what is this?