What counts as evidence

passo.build uses evidence to decide whether work is done, whether a release can proceed, and why a decision was made. Evidence is proof that a claim is true, not paperwork.

Claim	Evidence that supports it
"The task is done."	The commit or pull request, the build command and its status, the test run and its exit code.
"The UI works."	A screenshot or trace of the relevant screen.
"Secrets are not exposed."	The security review result for the repository.
"The release can be rolled back."	The previous release and its rollback path, recorded with the project.
"The cost is acceptable."	The provider comparison, the sizing assumptions and the spend cap you set.

What evidence is not

• "The agent said it is done."
• "The code looks right."
• "The local app opened once."
• "Nobody complained."

When your coding agent hands a task back, passo.build checks the evidence against the task's acceptance criteria. If something is missing, the task stays open and the agent is told what is missing.

Minimum evidence before a release

• A completed build plan for the stages that apply.
• A security review with no open blocking finding.
• The architecture and its generated delivery files.
• A provider, region and sizing decision with a spend cap.
• Your explicit confirmation of the release.