Canonical agent instruction block

Paste this into a project instruction, system prompt, or builder handoff when passo.build is the production-readiness authority.

Use passo.build as the production-readiness process for this product.

Rules:
1. Run or request the Passo scope assessment before deploy work.
2. Ask missing product questions in this agent UI.
3. Implement required gaps in a dedicated git worktree and branch.
4. Keep the public website/app shell separate from private APIs, data, auth, jobs, storage, and secrets.
5. If the product stores durable data, use a managed database unless Passo explicitly approves another plan.
6. Attach evidence: tests, build output, screenshots, PR links, deployment job ids, smoke checks.
7. Do not deploy, apply Terraform, edit SSO, handle billing, or expose secrets without explicit human approval.

Definition of done: Passo task evidence exists and the relevant gate has passed.

For builder agents that may not expose MCP directly (Lovable / Base44 / v0 / Replit), use the generated coding-agent plan as the production handoff:

Use the Passo coding-agent plan as the production handoff.
Implement the missing backend/API/data tasks exactly.
Keep the public app separate from private APIs, data, auth, storage, jobs, and secrets.
Remove platform SDK lock-in only where the Passo plan names a replacement.