01 — Where provin fits
Where provin fits
Each organization signs the predecessor and input-output relationship at handoff. The recipient receives that record with the data and verifies the signatures and continuity locally.
USE CASE 02
Supply chains · data spaces · inter-company APIs
Without relying on the sender’s dashboard or database, verify who declared each input, output, and handoff.
What happens
A supplier registers data, a processing partner transforms it, and a seller receives the result. Each organization runs a separate system and they do not share one logging backend.
At receipt, the seller wants to inspect more than the last sender. It needs to see which organization declared each input and output along the handoff path.
The flow in this scenario
01 — Where provin fits
Each organization signs the predecessor and input-output relationship at handoff. The recipient receives that record with the data and verifies the signatures and continuity locally.
02 — What a verifier can check
Public E2E coverage
Public E2E: supplychain confirms signatures and predecessor continuity across registries and handoffs modeled on three organizations.
How to read the evidence
provin supplies evidence for the handoff. Commercial terms and responsibility remain in the existing contract and operating rules.
provin puts receive, verify, process, sign, and emit in the same data flow. The architecture and specifications describe today’s interfaces and implementation boundary.