Evidence Bundle V1

Team / pilot path. Evidence bundles are how workflow cases become checkable packages. Free one-off secrets use Vault V2 only.

What it is

Schema QEV-EVIDENCE-BUNDLE-V1: a structured evidence package for a case (job, change, investigation). It records events, a summary with answerable questions, known gaps, artifacts, and integrity fields. A vault envelope can wrap this plaintext when you need at-rest encryption.

Required ideas (from the public schema)

package_id, tenant_id, flow_id, case_id, created_at
events[] — normalized workflow events
summary — outcome, questions, what evidence can answer
known_gaps — honesty about missing pieces
integrity — digests / binding for verification

What verification establishes

Package digests match declared integrity
Signatures valid when present
Required evidence present or listed as gaps

What it does not establish

That source systems told the truth
Legal outcomes or workmanship quality
Company-wide “we are secure” claims

How you produce one

Run a capture gateway (pilot or your deploy).
Ingest events via API, SDK, or connectors.
Complete the flow → package sealed.
Verify with gateway verify endpoints or offline tooling.

Schema source: schemas/qev.evidence-bundle.v1.schema.json in qev-platform.

Field service example · Trust program · Gateway