8 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	80b647a2ed	Name the acceptance tests in the milestone table and say what the review returns (review round 2)	2026-10-16 02:12:17 +02:00
jschoubben	a4c5ef69bb	Give the build's acceptance tests a home in the design and milestones, and answer review round 1 ... The research playbook named acceptance tests the milestones carry, which playbooks 02 and 04 did not know; its pre-check also disagreed with the knowledge base's deferral rule.	2026-10-16 02:11:27 +02:00
jschoubben	2a61c57258	Settle research decisions before proposing versions, and test on the cheapest bed (playbook 01) ... Research 053's identity part took six versions and about two hours: options that broke the mesh's own rules were offered and argued back, a version was proposed after every answer, and reviews returned findings a pre-check would have caught. A lab run was planned where an in-process test answered.	2026-10-16 02:09:22 +02:00
jschoubben	99243ec47e	Confirm milestones before opening their issues, name issue 845 for the check, keep 01's withdrawal and history lines	2026-10-15 21:19:01 +02:00
jschoubben	0d66edb24c	Make playbooks 01, 02 and 04 one cycle from idea to delivered milestones ... The operator found 04 odd on 2026-10-15: it went from a settled design straight to building, with no work breakdown, and contradicted playbook 07 on pull requests. 01 now starts from the operator's idea with setup questions, findings and a direction the operator confirms; 02 graduates that direction into one record per reversible choice and hands the design on; 04 breaks it into milestones usable on their own, one issue per repository part, each milestone one feature step of 07. 01 notes the knowledge base's insight-only rule for an active effort until issue 844 is delivered.	2026-10-15 21:18:15 +02:00
jschoubben	0afc8cc5f8	Name the commit the knowledge base's records now come from, and link research with touches and decisions with rests-on (review of #312)	2026-10-11 13:25:21 +02:00
jschoubben	418261213c	Remove the decision records and research efforts, which the knowledge base now holds whole (issue 426) ... ADR 0290 rule 9: once the import is checked record by record, hq keeps no copy. The records and efforts are removed; every link or path to them reads "ADR NNNN" or "research NNN"; a design's decisions: lists "ADR NNNN". 02-DECISIONS keeps a pointer README with the reading order's six topics, which the knowledge base reads through the records module; 01-RESEARCH keeps a pointer README. The checks drop the rules that judged records (the knowledge base holds each at propose; checks/README.md says where) and refuse a record written here again. Playbooks 01 and 02 and the skills write and read records with the knowledge base's verbs.	2026-10-11 12:56:09 +02:00
jschoubben	c0b35652d0	The numbering is the flow: decisions are 02, design is 03 ... papa-hq reads 01 research -> 03 decision -> 02 design. The order is a scar, not a choice: 02-DESIGN existed from its initial commit, and when adr/ was finally promoted on 2026-07-13 it took the next free number rather than its place in the sequence. By then design was too settled to renumber. hal-hq was three commits old, so it is not. adr/ becomes 02-DECISIONS and 02-DESIGN becomes 03-DESIGN, and following the folder numbers now walks the process in the order it happens: research produces a decision, the decision authorises a design. 00-GENESIS becomes 00-META, matching papa's rename from the same restructure. Every path reference rewritten across documents, frontmatter, playbooks and skills. All links resolve; all 58 frontmatter blocks parse and their path fields still point at files that exist.	2026-08-23 18:05:11 +02:00