The Build Understanding
The editable middle step between analysis and generation. You approve a description of the product you intend to build — then everything else is derived from that approval.
What it contains
The Build Understanding is a structured description of the product assembled from the public-page analysis: the intended customer (ICP), the jobs the product does for them, the core flows a user moves through, and a feature map. Every feature in the map is classified for your chosen niche and USP as retain, modify, remove, or add — so the document describes your version, not a clone of the source.
Evidence and uncertainty
Analysis is bounded to public pages and every material claim links back to the evidence it came from. Where the public surface does not support a confident claim, the understanding says so explicitly instead of inventing detail. Treat marked uncertainty as an editing prompt: you know your product intent better than any public page does.
Editing and rethinking
Each section is editable in the workspace. Rewrite text directly when you know what it should say, or request a rethink of a section when you want the analysis reconsidered rather than hand-corrected. Iterate freely — nothing downstream exists yet, so edits at this stage are cheap. This is the highest-leverage step in the product: a sharper understanding produces a sharper Build Sequence.
Why approval is immutable
Approving the understanding creates an immutable snapshot, and that snapshot becomes the sole source for the generated Build Sequence. Immutability is what makes the sequence trustworthy: every prompt can cite exactly which approved feature it implements, and the document cannot shift underneath a half-finished build. If your scope changes after approval, the prior approval is invalidated and the sequence regenerates from a newly approved version — the prompts and the understanding never disagree.
What happens after approval
Generation reads only the approved snapshot, your niche and USP, and your chosen build target, then produces the base prompt and ordered follow-ups described in Build Sequences. If you have not started yet, Getting started walks the full path from URL to sequence.