8 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
jochen	858e5413fa	Issue 356: the operator's command ran a stale engine, and a hand-over had no channel ... The engine on every node's PATH was the one a person copied at installation, a build behind every delivery; and the way out of issue 339 was a terminal act at the machine, which ADR 0272 and the operator's rule of the same day make impossible to type. The record, located in the engine, the controller and the catalogue's check, with the fixes' pull requests; ADR 0272 gains the rule as a dated insight: the operator types one command, nox, and every text addressed to the operator names a nox line. words.py now refuses a daemon's line, with --list lines for the catalogue's copy; the lifecycle and the operator's-machine designs and issue 343's quotations are reworded.	2026-10-09 18:36:58 +02:00
jochen	d3cb9fedf4	ADR 0272 accepted (the operator, 2026-10-09)	2026-10-09 13:02:45 +02:00
jochen	e143f6b193	Issue 343: name the node-engine's repository as an identifier	2026-10-09 12:12:34 +02:00
jochen	57bb4dab74	Issue 343: phase 1 of ADR 0272 is open as four pull requests	2026-10-09 12:12:23 +02:00
jochen	1ad9959b16	ADR 0272: say how the socket keeps ADR 0004, answer the operator and agent accounts only, and keep the bus request out of the SDK (ADR 0039)	2026-10-09 12:01:45 +02:00
jochen	95d78f7011	ADR 0272 (proposed) and issue 343: the controller's terminal has no command ... The records send the operator to "the controller's terminal", and on the control-node `mesh-controller` is not a command: the controller is a mesh process with its own account and environment, and nothing puts anything on PATH. The record proposes mesh-cli, a module on every node whose program asks the node-engine over a local socket; the node-engine vouches for the account from the kernel and asks the controller on its node's own subject; the controller runs the line as the terminal only for the operator's account where no agent can be that account. The glossary gains mesh-cli, nox (its zsh alias) and the controller's terminal.	2026-10-09 11:59:34 +02:00