Merge pull request 'Research writes its requirements from the operator's answers before any option' (#529) from docs/research-requirements into main

00-META/process/01-research.md

@@ -39,6 +39,12 @@ An idea arrives in one of two forms, and the first step differs:
    - **Explain each question with a concrete picture** in the operator's words: what they would see, do or
      lose under each option. No internal names (a record number, a verb, a word the glossary lacks) without
      what it is beside it.
+   - **Write the requirements from the answers, before the options.** Each one line, numbered, saying what
+     the result must hold and how it is checked (for example "R5. A change across repositories is
+     delivered whole or not at all; check: a change over three repositories"). The requirements shape the
+     effort: every option is weighed against them, and the operator corrects them before any option is
+     worked out (the operator, 2026-11-09: "coming up with a list of requirements can also be an important
+     part, it actually shapes the research").
 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; one never proposed is withdrawn after a week. Never
    pick one by hand.
@@ -52,6 +58,7 @@ An idea arrives in one of two forms, and the first step differs:
    in a local draft. The first sections:
    - **Overview**: the idea in the operator's words, what exists, the operator's answers (dated), and the
      words the effort uses that the glossary lacks, each defined in one line;
+   - **Requirements**: the numbered requirements of step 2, each with its check;
    - **Questions**: the questions to answer, the first ones first;
    - **Method**: what will be tried and measured, and on what.
 

00-META/process/playbooks.html

@@ -416,7 +416,7 @@ const P = [
  {n:"01",name:"Research",kind:"idea",c:"--idea",
   trig:"An idea worth investigating before it is committed to design. A symptom is not research.",
   who:"The session that heard the idea leads.",
-  steps:["Read what is known: ask, get, the tracker's list.","Ask 3 to 5 setup questions, one at a time, each with a recommendation.","Check every option against the mission and how-we-build first.","Reserve a number (kind research), never pick one by hand.","Propose the effort: Overview, Questions, Method, sections named by title, no file references.","Research; findings in the section Findings, one version per settled set.","Try at the cheapest level that answers the question.","Write the Domains: modules, seats, glossary words added or retired.","Write the Direction: decisions, rejected options, acceptance tests.","Ask the operator to confirm the direction, one point at a time.","Review the direction by architectural domain: security, seams, running qualities, health, events and logs, testing, upgrade, tools.","If the review asks changes: propose again, at most three times."],
+  steps:["Read what is known: ask, get, the tracker's list.","Ask 3 to 5 setup questions, one at a time, each with a recommendation.","Check every option against the mission and how-we-build first.","Write the numbered requirements from the answers, each with its check, before any option.","Reserve a number (kind research), never pick one by hand.","Propose the effort: Overview, Requirements, Questions, Method, sections named by title, no file references.","Research; findings in the section Findings, one version per settled set.","Try at the cheapest level that answers the question.","Write the Domains: modules, seats, glossary words added or retired.","Write the Direction: decisions, rejected options, acceptance tests.","Ask the operator to confirm the direction, one point at a time.","Review the direction by architectural domain: security, seams, running qualities, health, events and logs, testing, upgrade, tools.","If the review asks changes: propose again, at most three times."],
   prod:"A research effort in the knowledge base, status active, every version kept. Nothing in hq.",
   next:"02",bounds:"Setup 30 min · proposing 15 min · each experiment 30 min · direction 30 min · review by architectural domain 20 min · report every 10 min",
   prev:["Research that measured nothing","A recommendation the operator must argue back","Efforts copied into hq"],