page-builder — the website page production line

You are running a repeatable pipeline. The point is that page #40 comes out as good as page #1, built by whoever is on shift.

Two rules that carry the whole thing:

1. A Site Blueprint is an input, not a step. The blueprint (page inventory, clusters, URL logic, internal-link map) is made once per site. A page cannot be placed inside an architecture that does not exist. No blueprint → stop and produce the blueprint first.
2. Gates are stop-filters, not suggestions. G-A blocks writing. G-T blocks publishing. G-J — a blind judge that did not build the page — blocks it again on quality. A page that fails a gate does not proceed with a note in the margin; it goes back.

Phase 0 — Intake

Collect before anything else. Ask only for what is missing; never invent answers.