Answer the review: mockup data invented throughout, later milestones' scope marked proposed, design 59 says where it is replaced, playbook 10 aligned with 04 and 07

00-META/process/10-visual-design.md

@@ -20,7 +20,8 @@ model from the lead's brief. The operator picks; nobody else does.
 
 ## Steps
 
-1. **Gather what the page must carry.** Read the as-is of what it replaces and the real shape of its data from the
+1. **Gather what the page must carry.** A page whose direction needs research first starts at playbook
+   [01](01-research.md); this playbook then draws it. Read the as-is of what it replaces and the real shape of its data from the
    mesh (how many items, how long a line, what is missing in practice), the operator's complaint in their own
    words, and a short survey of how others solve it (a handful of products, one line each on what changes for
    the person). Write it into the work folder; nothing goes on the mesh.
@@ -33,13 +34,14 @@ model from the lead's brief. The operator picks; nobody else does.
    two, or a change; the next round draws only that. Three rounds without a pick mean something the operator wants
    is missing: ask what, before drawing again.
 4. **Make the pick the reference.** Copy it into the design's `NN-mockup/`, with every name, address, employer,
-   mail address and amount of the operator's own replaced by invented ones: hq is public. Say in the design that
+   mail address, domain, provider and amount of the operator's own replaced by invented ones: hq is public. Say in the design that
    the reference is a direction, and link it.
 5. **Write what is new as decisions,** each with the operator's Approve where it changes what they see, then the
    design and its milestones. The design's acceptance tests end with the operator using the page live.
-6. **Hold the build to it.** Playbook [07](07-feature-branches.md)'s review reads the built page against the
-   reference (a screenshot at each width beside the mockup), and the milestone is done only when the operator has
-   used the page.
+6. **Hold the build to it.** The lead gives playbook [07](07-feature-branches.md)'s reviewer the reference with
+   the built page, at a phone's and a desktop's width, as part of what the review reads against the issue. The
+   operator using the page is the milestone's live proof, made before the next milestone starts (playbook
+   [04](04-build-handoff.md)).
 
 ## Bounds
 
@@ -58,7 +60,7 @@ model from the lead's brief. The operator picks; nobody else does.
 ## How it is checked
 
 - A to-be design of a page the operator uses links its reference mockup in `NN-mockup/`, and that mockup holds
-  none of the operator's own names, addresses or amounts (read by the reviewer of the design's pull request).
-- The milestone's review report shows the built page beside the reference at a phone's and a desktop's width.
-- The design's last acceptance test is the operator using the page, and it is proven before the milestone's
-  issues are resolved.
+  none of the operator's own names, addresses, domains, providers or amounts (read by the reviewer of the design's pull request).
+- The milestone's review read the built page beside the reference at a phone's and a desktop's width (its
+  report says so).
+- The design's last acceptance test is the operator using the page, proven before the next milestone starts.