Process
Discovery -> build -> review -> test -> ship. The same Universal Build & Ship SOP that produced this site.
- 01
Planner
Gate: CEO approves stack, scope, and checklist
Inspect the problem, confirm tier (e.g. static vs app), propose stack and sitemap/build plan. Batch real questions. Do not build until the gate clears.
- 02
Developer
Gate: Report what was built
Implement the product. Secrets via env + .env.example. Commit in logical chunks. Stay inside the approved plan.
- 03
Reviewer
Gate: Review report - defects fixed
Senior critical pass: accessibility, contrast, responsive behaviour, broken links, semantic HTML, no fabricated content, no committed secrets. Fix, then re-review.
- 04
Tester
Gate: Test report + placeholder list
End-to-end as a real visitor. Every page, nav, forms, mobile, Lighthouse. Log by severity; fix blockers and majors. List every {{PLACEHOLDER}} still needed from the client/CEO.
- 05
Deploy
Gate: CEO chooses host + domain
Ship to static or app hosting as tiered. HTTPS. One-line redeploy command documented.
Why gates exist
Gates keep speed from becoming sloppiness. The CEO is interrupted only for real decisions - stack, paid services, domain and hosting - not for routine design or implementation choices.