Write the claim people are making
The claims file contains only a subject and plain-language claims, each with an id and text. “The customer-status repair was verified” is a review claim, not a verdict created by dbcli.
Review handoff
Compliance needs proof, not a database export.
A release review normally needs to know which claim points to which verification. Attaching SQL, rows, and credentials makes the review riskier and harder to read. An Evidence Pack is a verifiable index, not a copy of the source data.
The handoff: A reviewer asks whether the customer-status correction was verified. They should not receive SQL, rows, credentials, or the full audit. The team needs a durable summary with clear boundaries.
Turn scattered evidence into one review artifact
Reference existing evidence to compose a new pack
The pack refers to existing verification, audit, and receipt evidence. Its output stays in the workspace and will not overwrite an existing file, so the reviewer can trace references without receiving their contents.
dbcli evidence compose --claims ./claims.json --verification ver_abcd --audit 1a2b --receipt .dbcli/evidence/verify-receipt.json --output .dbcli/evidence/review.jsonValidate integrity before sharing it
Validate checks the SHA-256 digest and source availability; render creates the review view under the current blacklist policy. If a source expires later, the retained pack remains readable and says so.
dbcli evidence validate --file .dbcli/evidence/review.json --format json
dbcli evidence render --file .dbcli/evidence/review.json