6 Commits

Include renames

Author	SHA1	Message	Date
jochen	6d1310f1ea	An issue's status lives in the issue tracker: playbook 03, cycle.py and the notes slice 3 of ADR 0275 asked for	2026-10-10 15:54:32 +02:00
jochen	beaeedca79	Playbook 03 takes an issue's number from the issue tracker ... Issue numbers collided while each author read main and the open pull requests; since 2026-10-10 the tracker (ADR 0275) hands them out. The playbook and the hq-new-issue skill now open every issue there, keep a folder only for a design or governance issue, and say where its status lives until slice 3. Research 042's finding that the SDK had no compare-and-set is corrected, and to-be 53 names the module's code.	2026-10-10 13:06:13 +02:00
jochen	a28da1734b	Graduate research 034: the mesh in domains, one word per thing, checked ... ADR 0244 sorts the mesh's concepts into ten domains (ADR 0006's contexts carry over as domains), keeps machine and node as distinct words, and makes the glossary the authority with every retired word on its replacement's Not: line. To-be 49 draws the domains; the glossary is reorganised by them, its two contradictions removed and the missing words added. words.py now fails on a retired word in running prose and on a word defined twice, so the rule is enforced rather than believed; the 63 documents it failed on are reworded here, and research 034 is kept as the record of the words it studied.	2026-10-07 19:58:39 +02:00
jochen	d245df7dea	ADR 0237, to-be 45 Phase 5: a change is judged against the mesh that runs before it merges ... The operator approved Phase 5. Decides what the design left open: the build seat runs the merge check, the facts live in the artifact store, the merge gate composes the mesh as it is and with the change and judges only what the change adds, a replay lives where its incident is, and the controller's tests run a bus of their own at the mesh's release. A core issue now resolves only with a replay or a stated reason, checked by cycle.py.	2026-10-06 21:10:54 +02:00
jschoubben	47909c6b71	The records pointed at branches that no longer exist, and two fixes had no sequel ... Three issues named the branch that fixed them, and a branch is deleted when it merges — so every `fixed-by:` was a pointer that resolved to nothing by the time anyone followed it. They name commits and pull requests now, and playbook 03 says to. Two records were missing the thing a reader arrives for. 146 did not say that one of its fixes crash-looped the control plane on a running mesh, which is the whole reason the delivery subject carries the stream and the raise path was the only one exercised. 151 did not say that 152 removed the false reasons its roster moved, or that it stays open for the real ones. ADR 0080 enumerates what cycle.py enforces and named four things; it enforces five. A progressive insight names the fifth — the decision stands, the list had gone stale. The checks README and playbook 03 gained the same rule, and 155 points at all three.	2026-09-30 00:28:35 +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