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	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
jschoubben	1111bd84d7	Establish the repo for the completed Phase 0-3 build ... Settles the design repository now that the self-upgrade build is on main: - Records the two decisions that shipped without a record — ADR 0077 (the controller/foundation/node vocabulary) and ADR 0078 (the store and broker are ordinary modules); accepts ADR 0075 and 0076, which shipped work rests on. - Fills issue 051's amended-design and wires ADR 0078 into 07-the-foundation. - Sweeps the repo rename (mesh-control -> mesh-controller) into the mutable docs now that the forge repo is renamed; updates the glossary note and repos.md. - Fixes the six broken links from the design-doc renames, indexes the glossary, regenerates the decisions reading order. Both checks (records.py, index.py) are green. Statuses stay honest: the build is on main and lab-proven but not deployed as the production mesh, so the to-be docs remain in-progress and the as-is layer (the hal mesh) is unchanged — graduation to implemented + as-is belongs to deployment, not merge. https://claude.ai/code/session_01D6qtiYU3P9jk3pnAXyAFyx	2026-09-17 00:04:58 +02:00
jschoubben	9073d3f2df	Say plainly that env-file never points at a sealed secret ... The playbook offered `env-file` and `${secret:name}` as alternatives, and that reading is what produced the bug every example module shipped with: own-secrets pointing at a path named `.env`, mounted as env-file, holding a bare password. The container starts with no password set — which is a service running on the wrong credential, not a failure. They are not alternatives. A sealed file holds a password and nothing else, so env-file points at a file the module declares whose content leaves a hole, and the host fills it on the machine. A provisioner is the exception, because it reads a password file. Written out as the three lines a module needs, with the failure it prevents named, since the abstract version was already there and was read the other way.	2026-09-01 02:52:55 +02:00
jschoubben	1ee62392b9	Playbook 06 — writing a module, from doing it once ... Written after porting the first real workload end to end. Every step exists because skipping it cost something, and the ratio is recorded because it is the lesson: six attempts, one real bug, and the mesh was right every time. The rule worth carrying out of it: read the host's log before theorising. A declaration that was sent and not applied says so there and nowhere else — it took an hour to look, and the answer was one line.	2026-09-01 01:46:46 +02:00