Software verification evidence
Keep a reviewable record of what was checked, what ran and what remains unknown, and connect it to the release decision it supports.
For release owners, QA leads and security reviewers who need more than a green status. Evidence should connect a specific change to checks, results and the limits of those results.
What Zof does
Evidence bundles
Zof organizes verification results, supporting records and authorization decisions into evidence bundles for review. The Control Plane uses this evidence when evaluating whether an action can proceed.
Reports from your tools
Existing test suites and CI results count as evidence. Keep the original reports and artifacts available for inspection alongside the records that reference them.
Platform evidence review
The evaluation should establish how evidence connects to change records, approvals and control decisions in your deployment.
From a change to a review decision
- 01
Collect the inputs
Keep the source revision, runner details, tool versions and original reports. Identify which checks ran, which were skipped and which failed to complete.
- 02
Attach and check
Attach each report to the change it describes and check that it is complete. Keep the original reports and artifacts available for inspection.
- 03
Review and retain
Compare the evidence with the release criteria, record approval separately, and retain the records under your organization’s access and retention rules.
What evidence you get
Results with scope
Records should distinguish static analysis from test execution. A static pass is not evidence of passing runtime tests.
Incomplete work stays visible
Partial evidence can be well formed and still incomplete. A valid record is not a release verdict.
Artifact references
A path and digest help identify an artifact you retained. They do not upload it, preserve it indefinitely, prove its origin or make a record tamper-proof.
Prerequisites and limits
- Retain original producer output to investigate gaps between a report and the evidence that references it.
- Confirm which report formats your deployment accepts. For Playwright, preserve traces and HTML reports alongside the evidence.
- Hosted acceptance, signatures, identity verification, approval enforcement and retention must be verified separately for your deployment.
- Evidence can support a compliance review, but it does not by itself provide a certification, prove compliance or establish software correctness.
In practice
Make the release record useful to the next reviewer
Evidence should let someone understand a decision without reconstructing a conversation. Keep the question asked, the execution performed, its result and the decision based on it connected. Separate what was observed from what a reviewer inferred.
01
Identify the change and target
Keep the repository or application identity, revision and tested environment with the result. Record when the checks ran so reviewers can distinguish current evidence from historical context.
02
Keep the supporting detail
Preserve the relevant assertions, findings and original artifacts. A summary is an entry point; the reviewer should be able to inspect the detail behind a failure or a passing result. Confirm supported exports during evaluation.
03
Record the decision separately
Describe which requirements were met, what remained unresolved and who accepted the next action. Agree on access and retention with the people who will revisit the record.
Illustrative scenario · not a customer result
Revisiting a release after an incident
A support issue appears after deployment. A useful release record identifies the revision tested, the scenarios executed and any gaps accepted during review. That lets the team ask whether the failed behavior was covered, whether the environment differed, or whether the change happened after verification.
Questions to resolve before you begin
Is a green dashboard enough?
A dashboard summarizes results. For a consequential decision, inspect the test scope, execution status and original output as well. A green summary cannot establish behavior that was never tested.
Does an evidence record establish compliance?
It can support a review of your controls. Your organization still determines applicable obligations, required records and whether the evidence satisfies them. A test report is not a certification.
Decide what evidence you need
Bring your release criteria and sample reports to an evaluation. Decide what evidence your release policy needs before adding a gate.