Evidence
Evidence is what a run leaves you so you can judge the work.
Evidence is what a run leaves you so you can judge the work.
What it is
Evidence is what a run leaves you so you can judge it. It is not the product in git. It is the trail: logs from steps, artifacts those steps wrote, the output of Verification, and SUMMARY.md when delivery ran. You read that trail to decide whether to merge, requeue, or dismiss.
Logs are the step's own output — what it printed while it worked. Artifacts are files a step attached: a summary, a report, a finding list. Verification output is the result of the commands in the task: tests, a build, a script. SUMMARY.md is the delivery note for the change-set, one file for the whole run, including when some repositories failed.
The factory does not merge on the strength of this trail. It leaves the trail so you can.
What you see
On the run detail page you open the run and read what each step left. Failed steps keep their logs. A verify failure shows the command output that did not pass. A review shows findings. Delivery, when it ran, points at SUMMARY.md.
SUMMARY.md lives with the run. It names the task, the branch, which repos were delivered, and which were not. For a delivered repo it includes the commit. For a failed repo it includes why. That file is the one delivery note; you do not get a separate summary per checkout.
You can open logs and artifacts as files. You do not need the database for that. The Dashboard is the usual way to find them; the run's files are there if you prefer to read them in the editor.
When a run needs attention, the evidence is still there. Out of tries, a rejected gate, or a partial delivery all leave the last findings for you. Requeue uses your note and those findings as feedback for the next run. Dismiss keeps the branch and drops the copy of the repo; the history of the run remains.
What you decide
You decide whether the trail is enough. Green verification and a SUMMARY.md you agree with is a candidate to merge. A pass you do not trust — the wrong command, an empty check — is a reason to fix the task, not a reason to land the commit.
You decide what to do with a failure. The log tells you whether to requeue with a sharper note, resume only the failed repos, or take over. You decide whether a partial delivery is useful as-is: the delivered commits stay, and you should not push them without a plan for the rest.
You do not decide the shape of SUMMARY.md. You decide whether to believe it. You do not have to keep the worktree in order to keep the trail; logs, artifacts, and the summary remain with the run.
Where to go next
Meet evidence on the run detail page, as files on the run, and as SUMMARY.md after delivery.
- Run — the work the trail belongs to
- Delivery — the commit and the summary
- Task — Verification, which produces part of the trail
- Multi-repo runs — one summary for several repos
- Measure and improve — metrics after runs finish