5 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	ec8676c225	Issue 140 is resolved, and was resolved before it was read again ... Written 2026-09-28, answered the same week by mesh-controller bdf965d and c68d3a7, and never closed — so the mesh's own account said reach was declared nowhere while three readers were reading it: the filter, the proxy's names, and each authority's host policy. The resolution names them and what checks each. What is left is retiring the older per-port keys the block replaces, which is not a gap in what reach can say.	2026-09-29 22:19:24 +02:00
jschoubben	14ff89fa40	ADRs 0138 and 0139: an assignment binds an endpoint and says how far it reaches, and a network is forwarded because a module declared it ... Both follow from the same rule the mesh is built on — a node's configuration is composed from the modules assigned to it. Reach was settled separately by the filter, the proxy's names and the certificate authority, so "this must not be public" could not be written; it becomes one value on the assignment that all three read. And the forward chain consulted two constants plus a typed list although modules already declare their networks; it now forwards what they declared, with the host rendering the addresses it allocated.	2026-09-28 23:03:32 +02:00
jschoubben	dcdfcf104e	Issues 140 and 141: an endpoint's reach is declared nowhere, and the forward chain follows constants instead of the modules ... Found preparing the control-node's convergence. Reach is settled independently by the filter, the proxy's names and the certificate authority, so "this must not be public" cannot be written and a public certificate is obtained regardless. And the forward chain allows two hardcoded ranges plus a typed list, though the mesh already knows which networks exist because its own modules declared them — a range wide enough to keep four of them would have forwarded two predecessor leftovers too.	2026-09-28 22:57:38 +02:00