Confirm milestones before opening their issues, name issue 845 for the check, keep 01's withdrawal and history lines

00-META/process/01-research.md

@@ -31,7 +31,8 @@ An idea arrives in one of two forms, and the first step differs:
    carrying a recommendation: what comes first, what is out of scope, which options must be tried, what
    done looks like. Three to five questions is usual; the answers are the effort's first findings.
 3. **Take a number.** `knowledge-base.reserve` with `kind: research` and `for`: the effort's title. The number
-   is spent whether or not the effort is ever proposed; never pick one by hand.
+   is spent whether or not the effort is ever proposed; one never proposed is withdrawn after a week. Never
+   pick one by hand.
 4. **Propose it.** `knowledge-base.propose` with `kind: research`, the `number`, a one-line `title`,
    `status: active`, `date` (the day it began), and `sections`, each a `name` and its markdown `text`:
    - `00-overview.md`: the idea in the operator's words, what exists, the operator's answers (dated), and the
@@ -43,7 +44,8 @@ An idea arrives in one of two forms, and the first step differs:
    design's path), and what it names for another reason as `cites`.
 5. **Do the research.** Try, measure and read, smallest question first. Each finding goes into
    `04-findings.md`: what was tried, what it showed (with numbers), what it means. Each change of the effort
-   is `knowledge-base.propose` again, whole, with `why`. Until issue 844 is delivered, the knowledge base
+   is `knowledge-base.propose` again, whole, with `why`; every version is kept, and `knowledge-base.history`
+   lists them and gives the difference between two. Until issue 844 is delivered, the knowledge base
    takes a new version of an accepted, active effort only as a progressive insight: give `insight`, saying
    what the effort held before the new finding, and mark the finding in the text with its date.
 6. **Settle the direction with the operator.** When the questions are answered, write `05-direction.md`:

00-META/process/04-build-handoff.md

@@ -30,12 +30,12 @@ A design becomes **milestones**, and each milestone becomes **issues**:
 4. **Break it into milestones.** Write them into the design, in a section *Milestones*: for each, its number,
    its one-sentence outcome, the repositories it touches, and what it depends on. Order them so each is
    usable as soon as it is delivered, the smallest useful one first.
-5. **Open the issues.** For each milestone, `issue-tracker.open` one issue per repository part, its title the
-   symptom or capability in plain words, its report naming the design, the milestone and the decisions it
-   builds with; link the order with `depends-on`. Write the issue numbers into the milestone's entry in the
-   design.
-6. **Ask the operator to confirm the milestones**, in a short table: number, outcome, repositories, issues.
-   Change what they change.
+5. **Ask the operator to confirm the milestones**, in a short table: number, outcome, repositories, the
+   parts each repository builds. Change what they change.
+6. **Open the issues.** For each confirmed milestone, `issue-tracker.open` one issue per repository part, its
+   title the symptom or capability in plain words, its report naming the design, the milestone and the
+   decisions it builds with; link the order with `depends-on`. Write the issue numbers into the milestone's
+   entry in the design.
 7. **Flip the status.** `status: in-progress`, `updated:` today; the design change goes through playbook
    [08](08-small-fixes.md) (one hq pull request).
 8. **Hand each milestone to playbook 07, one at a time.** The milestone is the feature step; its issues are the
@@ -55,6 +55,8 @@ A design becomes **milestones**, and each milestone becomes **issues**:
 
 ## How it is checked
 
+Read by the lead and the reviewer today; a check in hq's merge-check is tracked by issue 845.
+
 - A design in `status: in-progress` has a *Milestones* section, each milestone with its outcome and its
   issues; an in-progress design without one is the smell of building without a breakdown.
 - Every issue a milestone names exists in the tracker (`issue-tracker.get`), and an issue in `fixing` names