Shared gate 1 · Scope and provenance
Identify the exact project, deployable path, branch, local commit, release intent and forbidden side effects. Pass: source path and intended host are recorded. Stop: no public posting, DNS, data import, external send or merge without explicit approval.
GitHub 2 · Validate static suitability
Classify static output versus dynamic services; retain static libraries on GitHub Pages. Pass: local production artifact is inspected, base paths are correct, and no secrets/server code are public. Dynamic API/admin/database requirements route to Render.
GitHub 3 · Build, scope and push
Run the production build, stage only the scoped files, inspect the staged diff, and push the verified commit. Pass: local SHA equals remote branch SHA. GitHub Pages workflow (when used) is associated with that exact SHA—not an older green run.
GitHub 4 · Verify Pages live behavior
Check the Pages deployment, live document, key asset, navigation and browser console. Pass: deploy succeeds; live URL and asset return success; desktop/mobile rendering and an interaction are demonstrated. A push alone is not completion.
Render 5 · Derive service configuration
Read the actual application manifests to establish runtime, root directory, build/start commands, port, health route, environment and data contract. Pass: no values are guessed. Choose a Blueprint for repeatable/multi-service deployments; use a simple Git service only when that model fits.
Render 6 · Release safety gate
Set secrets outside Git, validate migrations/rollback, access controls, health behavior and Git remote SHA. Pass: service can build and start securely from the pushed revision; database and admin access gates are defined. Stop: never expose an unauthenticated admin page or run destructive production operations speculatively.
Render 7 · Deploy and monitor exact SHA
Trigger/approve Render deployment and inspect the build/start/health logs for the intended commit. Pass: service status is live and reported deployment SHA matches remote intended SHA. Diagnose logs before changing code; fix one established cause per retry.
Shared gate 8 · Prove and hand off
Test health, public, protected and core routes; capture deployment provenance and a rollback target. Pass: live behavior—not dashboard colour—is verified. Custom domains map hosts, not paths; no Namecheap DNS change without explicit approval and rollback values.