provin

USE CASE 05

Sensor aggregation · features · analytics

Verify the inputs behind an aggregate,
not only the final value

Commit to the input set used by an aggregation and later check whether a particular input was included.

What happens

The aggregate remains, but its inputs are unclear

A daily aggregate was produced from sensors at several sites. Months later, a calibration issue is found in one sensor and the team needs to know whether its value was used.

The aggregate alone cannot show which inputs were selected at the time. The team wants to check the set and one input’s membership without copying every source value into the result.

The flow in this scenario

01 Send several inputs to aggregation Use sensors A, B, and C in one process 02 Commit to the input set Fix the declared set in a signed record 03 Produce the aggregate Connect the set record to the result 04 Check one input later Verify membership by full-set recomputation 01 Send several inputs to aggregation Use sensors A, B, and C in one process 02 Commit to the input set Fix the declared set in a signed record 03 Produce the aggregate Connect the set record to the result 04 Check one input later Verify membership by full-set recomputation
Committing to several source inputs and checking one input after aggregation

01 — Where provin fits

Where provin fits

The aggregation process creates a commitment to its declared input set and links it to the output record. A verifier later recomputes the commitment from the full declared set to confirm a specific input was included.

02 — What a verifier can check

What a verifier can check

  • Confirm that the declared input-set commitment has not changed.
  • Check whether a particular input belongs to that committed set.
  • Connect the input-set record to the resulting aggregate.

Public E2E coverage

Public E2E: sensoraggregate and aggregatebundle confirm a signed input-set commitment and membership checking by full-set recomputation.

How to read the evidence

The check covers the recorded input set. Completeness and semantic correctness require separate controls.

Place verifiable evidence at the data handoff

provin puts receive, verify, process, sign, and emit in the same data flow. The architecture and specifications describe today’s interfaces and implementation boundary.

View architecture View specifications