4 Commits

Include renames

Author	SHA1	Message	Date
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
jochen	55637ecb95	ADR 0248: the decision index is generated when it is read, so two open decisions no longer conflict	2026-10-07 23:38:34 +02:00
jschoubben	b4607dfc03	Numbers are identity; the reading order is a generated, checked index ... Decided after measuring what renumbering actually costs: 96 references in code comments across two repositories, none of which would have failed to compile. They would have pointed at the wrong reasoning, which is worse than a broken link because nothing reports it. So a number identifies a record and never changes. It cannot also be a position -- a position moves when the set changes, and an identity that moves is not one. The reading order moves into an index generated from each record's `topic:`. Six topics, in the order somebody learns the system. The index is WRITTEN rather than only generated on demand, which reverses what this repository previously said. The reason it said otherwise is that a hand-written index drifts -- but a reader looking at the folder on a forge sees the folder, not a command, and the drift objection is answered by checking rather than by refusing to write one. That is §5's own rule: a rule states how it is checked. Two checks, both confirmed to bite. index.py fails when the written order no longer matches the records. records.py fails when a record has no topic or one nobody defined -- the quiet failure being a record that vanishes from the order rather than appearing in the wrong place.	2026-08-28 23:39:18 +02:00