3 Commits

Include renames

Author	SHA1	Message	Date
jochen	478a198e9a	ADR 0247: a machine with a VPN client routes names by domain, through a resolver of its own ... Research 033 measured the laptop's VPN client and the mesh overwriting each other's resolver file in nine of nine sessions, each time cutting off one kind of name. The operator chose a resolver module on a node seat of its own, installed only where something requires split-dns, with the VPN client's module carrying the adapter. Graduates research 033 into to-be 50, and amends connectivity §2, to-be 48 §10, the seats and the glossary.	2026-10-07 21:33:48 +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
jochen	0ab47b9417	Research 033: split DNS with a VPN client ... The laptop's VPN client replaces the mesh's resolver file on every connect and the node-engine writes it back minutes later, so either the mesh's names or the corporate ones fail for whole sessions. Measure how the client sets DNS and weigh how names can be routed by domain without breaking ADR 0223's one-answer rule.	2026-10-07 18:38:49 +02:00