Use the web console
The console follows the same three outcomes as passo.build: Connect → Review → Ship. It shows the current project evidence, the decisions that need you, and the next available action. A heading or an outcome label does not authorize a release: the server checks each action and its prerequisites.
| Outcome | Console steps |
|---|---|
| Connect | Sources, analysis, documentation and implementation work on the Board |
| Review | Security check, architecture, cloud selection and Environment setup |
| Ship | Delivery bundle, authorized deployment, release history and available live evidence |
Connect: understand the product and finish the work
Connect the sources for your product, then run the analysis. Documentation is produced from that analysis. Read the current book and review readiness to create or review the work on the Board. Complete the implementation and verify the work using the available execution and review actions. A saved task, an execution result and a verification record are different pieces of evidence.
Your coding agent can work with the project, but handing it a task does not mean the implementation has finished. The console keeps the actual task status and recorded evidence visible. If a source or the documentation is missing, use the specific recovery action shown by the console.
Review: freeze a version and review its release choices
Use Run security check on the Board to save the finished work as a new Version when its prerequisites are met. The security check starts automatically for that version. Once a version is live, Run a new check on the Security page checks it again; what it finds applies to the next deploy, and the live version keeps running. Open its scan or security report to inspect progress, findings, recorded decisions and limits. Only the actions supplied for each finding are available; accepting a risk does not certify that the application is secure. A blocking finding must be resolved or receive a permitted decision before the server allows the next action.
Review the architecture, then compare the available cloud providers and regions. An architecture selection is a recorded choice; confirmation and delivery are separate steps. A cloud selection likewise does not mean the release is ready to deploy.
Environment setup follows the cloud choice. Complete the available settings, validate the environment revision, select it, and generate the delivery bundle. The console exposes account, configuration and secret requirements when they are available. Follow the server's next action if any required evidence is missing.
Ship: authorize the deployment and inspect what actually ran
Review the delivery bundle and deployment prerequisites before authorizing the release. Follow the real deployment steps and result. Release history records reported deployments; a failed history read is an unavailable result, rather than proof that no release exists. Retry the read when offered.
After deployment, inspect the available live evidence for health, errors, usage and cost. Missing telemetry stays unknown. Rollback and account-management actions depend on the capabilities available for that project; this guide does not imply a control exists when the console has no corresponding action.
Provider portability, including migration without starting the product over, is part of the roadmap. Use the actual supported provider choices and migration capabilities shown for your project today.
Read the status before the next step
- Missing means the required evidence or configuration has not been supplied.
- Unknown or unavailable means the console cannot establish the result; it is not the same as missing configuration or an empty history.
- Partial or not checked means a check did not cover the whole planned surface. Completed scanning does not imply that every possible check ran.
- Stale means an earlier result may no longer describe the current sources.
- Blocked means the server requires a prerequisite or decision. Read its reason and use the available recovery action.
Stop and resume
Project state lives on the project, not in your browser tab. Return to the latest confirmed evidence and the current next action. The connected coding agent works on the same project state; neither the agent nor the browser can bypass a server prerequisite by changing a presentation label.