4 Commits

Include renames

Author	SHA1	Message	Date
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
jochen	daa9f171ae	Issue reports carry only opened: the tracker holds every status, so no copy can drift ... The import of slice 3 (ADR 0275) was checked against every folder: no report changed since the commit it read, and the tracker holds each report's status, owner, fix, design amendment, replay and closing day. The keys are removed from all 361 reports, cycle.py refuses them in any report, and the playbooks, skills and READMEs that still pointed at them name the tracker instead.	2026-10-10 17:44:18 +02:00
jschoubben	2b5119ecd2	Issue 114 is answered: the controller is a process, by ADR 0142 ... It asked a question rather than reporting a defect, and the question was taken five days later — the mesh's own components are binaries on the machine, and third-party software stays a container because an image is the right way to carry somebody else's build. The delivery of them is issue 142.	2026-09-29 22:38:11 +02:00
jochen	82a6badc7c	Issue 114: land the controller's container-or-process question, renumbered ... Filed 2026-09-24 on a branch of its own and never merged, numbered 113, which is taken. 114 is free because a sibling branch folded it, so it takes that number and keeps its commit. Kept separate from issue 117 rather than folded into it. 117 asks the same question of every module and locates the missing decision; this asks it of the controller, where `network: host` means container network isolation — the property that resource type usually buys — is not in use. That observation is this report's own and is nowhere in 117, and folding would lose it. Its first open question is answered by 117's diagnosis and now says so: the host's `process` shape is built, applied and tested, restart and run-to-completion semantics included, so deciding this does not wait on host-side work.	2026-09-25 16:16:21 +02:00