1497 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
mesh-admin	879b183268	Merge pull request 'Issue 305: a recheck left the old verdict standing' (#190) from issues/305-a-recheck-left-the-old-verdict-standing into main	2026-10-08 08:34:30 +00:00
mesh-admin	57b24738f3	Merge pull request 'Issue 146: the enrolment-time consumer is answered by issue 208; design 08 names the join's code' (#189) from issues/146-the-enrolment-consumer-and-the-tunnel-join into main	2026-10-08 08:24:28 +00:00
jochen	573a44a33d	Issue 305: a recheck must put the merge check back to pending, or the old verdict merges	2026-10-08 10:12:52 +02:00
mesh-admin	0abca926ea	Merge pull request 'ADR 0217, to-be 44: no change to a machine takes effect unseen' (#97) from feat/no-change-takes-effect-unseen into main	2026-10-08 00:06:01 +00:00
mesh-admin	af398aef7b	Merge pull request 'Issues 303, 304; 240 resolved, 242 located' (#94) from issues/245-246 into main	2026-10-07 23:55:47 +00:00
jochen	43bffdc0c3	Issue 146: the enrolment-time consumer is answered by issue 208's assertion; design 08 names the join's code ... The branch building ADR 0169 carried a fix making a node's declaration consumer as it enrols. The controller already asserts every node's consumer before each send, and the self-check's healer asserts a missing one again, so the fix is dropped rather than merged and the record says why. The installer now places the bus's accounts at genesis.	2026-10-08 01:53:07 +02:00
jochen	e3caa4e1d4	ADR 0217, to-be 44: no change to a machine takes effect unseen ... Two incidents in two days had one shape: a change took effect that nobody saw first (issues 241 and 304). Three guards where the change is made — a settings layer read before it is replaced, a push that says what it will change, a running module's data move acknowledged — each silent when nothing is at stake. Accepted by the operator on 2026-10-08. To-be 44 is in progress in mesh-controller (feat/no-change-takes-effect-unseen), migration 0078, fitted onto what the controller does since: a whole-mesh push that says so and leaves a machine waiting for a gate, a person's push that says what it recreates (ADR 0242), a named push's cascade. The decision index is generated (ADR 0248), so no line is added to its README.	2026-10-08 01:45:49 +02:00
jschoubben	67599df951	Issues 303, 304; 240 resolved, 242 located ... 303: a media server's previews were reached through a link its container never mounted — fixed by mounting them. 304: settings set replaces the whole layer with nothing to read it first and no history. 240 is fixed by mesh-controller#47; 242 has backups running and records what the rollout taught. (First opened as 245 and 246; main has since taken both numbers, and 302 was the last.)	2026-10-08 01:45:39 +02:00
mesh-admin	08a874b55f	Merge pull request 'Triage issues 279-298: resolve the fixed, with replays R292 and R298' (#188) from issues/triage-279-298 into main	2026-10-07 23:41:52 +00:00
mesh-admin	78fd323df3	Merge pull request 'Triage issues 228-278: close the fixed, re-check the rest' (#187) from issues/triage-228-278 into main	2026-10-07 23:41:48 +00:00
mesh-admin	ed24d950db	Merge pull request 'Issues 092–208 triaged on 2026-10-08: 13 resolved, 1 wontfix, the rest re-checked' (#186) from issues/triage-092-208 into main	2026-10-07 23:41:45 +00:00
jochen	64e97d0de1	Triage issues 279-298: resolve the fixed with replays R292 and R298 ... 292 and 298 resolve with replays now registered in mesh-lab. The other fixed core issues say why no replay can be laid over the commit before their fix. The rest are re-checked against main.	2026-10-08 01:31:13 +02:00
jochen	2d18fa3380	Triage issues 228-278: close the fixed, re-check the rest ... Each issue is resolved with its fix and a replay or the reason none exists, or re-checked against main and the live mesh on 2026-10-08.	2026-10-08 01:31:10 +02:00
jochen	623fccee23	Triage issues 092-208: close the fixed and the obsolete, re-check the rest ... The operator asked on 2026-10-08 for the deprecated issues to be gone. In hq an issue is closed, never deleted, so each one is resolved with its fix, closed wontfix with a reason, or re-checked against main and the live mesh.	2026-10-08 01:31:06 +02:00
mesh-admin	990414c9b8	Merge pull request 'Ignore Python's cache folder' (#185) from chore/ignore-python-cache into main	2026-10-07 23:05:54 +00:00
jochen	5d4e427117	Ignore Python's cache: running the checks wrote it, and one file had been committed by mistake	2026-10-08 01:04:03 +02:00
mesh-admin	c6ff3b65b6	Merge pull request 'Issues 301, 302: a push of recorded builds is no repair; the lab's Go replays are checked in Go' (#184) from issues/301-302-a-push-of-recorded-builds-and-the-labs-go into main	2026-10-07 22:26:27 +00:00
jochen	7fde8f4bbe	Issues 301 and 302: a push of recorded builds is no repair, and the lab's Go is checked in Go ... 301: S15 counted the operator's pushes of recorded builds, the word ADR 0242 asks for, as repairs and wanted a healer for three causes. 302: the lab's replays register was never compiled before a merge, because its check ran in the TypeScript toolchain. To-be 45 §7 and §9 say how each is now decided and checked.	2026-10-08 00:17:14 +02:00
mesh-admin	69ab2fd7f7	Merge pull request 'Issues 296, 299, 300: resolved, each with its replay' (#183) from issues/296-299-300-resolved into main	2026-10-07 21:55:20 +00:00
jochen	787f428e7e	Issues 296, 299, 300: resolved, each with its replay proved to fail before its fix	2026-10-07 23:44:47 +02:00
mesh-admin	ded2173308	Merge pull request 'ADR 0248: the decision index is generated when it is read, and never stored (issue 297)' (#182) from decision/generated-decisions-index into main	2026-10-07 21:44:14 +00:00
jochen	f4a76ca291	Issue 297: resolved by hq PR #182 and mesh-catalog PR #115	2026-10-07 23:39:30 +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
mesh-admin	eb54474519	Merge pull request 'Issue 300: a new module is not built at its merge' (#181) from issues/300-a-new-module-is-not-built-at-its-merge into main	2026-10-07 21:01:41 +00:00
mesh-admin	2adbfed90f	Merge pull request 'Issue 299: an optional verb makes a holder look silent' (#180) from issues/299-an-optional-verb-makes-a-holder-look-silent into main	2026-10-07 21:01:34 +00:00
jochen	aaaef91b7b	Issue 300: say delivery plan, the glossary's word	2026-10-07 22:40:17 +02:00
jochen	9b573f4ca0	Issue 300: a new module is not built at its merge ... The change plan said a merge adding a module builds it; the merge built nothing, so the module stayed unregistered until a hand build.	2026-10-07 22:39:56 +02:00
jochen	6006754172	Issue 299: an optional verb makes a holder look silent ... D3 raised node-uplink silent on every machine once the seat gained verbs its holders are not yet required to serve, against ADR 0246's step 1.	2026-10-07 22:29:04 +02:00
mesh-admin	dda850863f	Merge pull request 'ADR 0247: a machine with a VPN client routes names by domain, through a resolver of its own' (#179) from decision/0247-split-dns-on-a-machine-with-a-vpn-client into main	2026-10-07 19:46:08 +00:00
jochen	6373ca815b	ADR 0247: say exactly where the VPN's domains go and do not	2026-10-07 21:35:40 +02:00
jochen	7e9d0dfe7b	ADR 0247: say what is to confirm live about resolved and the resolver file, not a guess	2026-10-07 21:35:21 +02:00
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
mesh-admin	9b6479f78f	Merge pull request 'Issue 297: two open decisions always conflict' (#177) from issues/297-two-open-decisions-always-conflict into main	2026-10-07 19:21:55 +00:00
mesh-admin	0bd12fc777	Merge pull request 'Issue 298 and ADR 0246: a seat's new verb is promised before it is required' (#178) from issues/298-a-new-seat-verb-deadlocks into main	2026-10-07 19:21:52 +00:00
mesh-admin	3083283e17	Merge pull request 'words.py: a retired word's plural is the word' (#176) from fix/words-match-plurals into main	2026-10-07 19:21:34 +00:00
jochen	91daabaa97	Say the uplink verbs shipped optional, not staged: a progressive insight in ADR 0241, corrected in to-be 48 ... The controller that merged (mesh-controller #116) dropped the staged seat and marked both verbs optional, stored in the seat's row and read back optional.	2026-10-07 21:18:11 +02:00
jochen	4b36234c9b	Reword the hosts file in to-be 36, found by the plural on the rebase onto main	2026-10-07 21:14:43 +02:00
jochen	350f7dcdc2	Hold a retired word's plural to the word, so alerts and rollouts no longer pass ... words.py matched a retired word only when nothing followed it, so the plural of every retired word passed. The pattern now takes s or es on the last word; 14 uses in 9 documents are reworded, two of them 'the hosts' for the node-engines.	2026-10-07 21:14:36 +02:00
jochen	e6a17b8bf6	Issue 298 and ADR 0246: a seat's new verb is promised before it is required ... Design 33 said a seat's verbs change additively, and section 3 made each one a condition of holding, so a verb added in the controller and served from the catalogue could land in neither order. It happened three times on 2026-10-07. Section 7 now says the three steps and how each is checked.	2026-10-07 21:14:20 +02:00
jochen	57f95fc6bb	Issue 297: every open decision conflicts with the next one to merge ... The written decision index is the one file every decision PR edits, at the end of its topic, so on 2026-10-07 each merge forced the others to rebase and be checked again. The diagnosis weighs four fixes and recommends generating the index on read.	2026-10-07 21:11:42 +02:00
mesh-admin	921ff3e6c4	Merge pull request 'ADR 0245: a verb says what it replaces, and the agent is guarded from working round the mesh' (#173) from decision/0242-a-verb-says-what-it-replaces into main	2026-10-07 19:10:00 +00:00
mesh-admin	52ecd8bfd5	Merge pull request 'Issue 296: a plan's clock restarted at every save' (#175) from issues/296-a-plans-clock-restarted-at-every-save into main	2026-10-07 19:04:58 +00:00
jochen	6cacf772dc	ADR 0245: a verb says what it replaces, and the agent is guarded from working round the mesh ... The agent reached machines over ssh because search never found the verbs by the commands it knew. Records the three rules (generated instead-of table, search by replaced command, the shell guard with the operator's recorded override) and how each is checked; to-be 36 names it.	2026-10-07 21:04:24 +02:00
mesh-admin	ede4b29cd1	Merge pull request 'ADR 0241 and to-be 48 §10: a machine says how its network is, and an outside writer of a mesh file is a finding' (#168) from decision/0241-a-machine-says-how-its-network-is into main	2026-10-07 19:04:09 +00:00
jochen	6caa471ed0	Issue 296: the refused step logged and saved on every tick	2026-10-07 20:47:09 +02:00
jochen	c462837ff2	ADR 0241's design: name the node-engine's repository as code (ADR 0244)	2026-10-07 20:33:23 +02:00
jochen	fe232388a0	ADR 0241 rule 8: the uplink seat answers what the machine resolves through ... A finding about a machine's names needs a way to look further that is not a terminal on the machine; the uplink seat's holders are where that is.	2026-10-07 20:33:23 +02:00
jochen	a22a1661e1	ADR 0241 and to-be 48 §10: a machine says how its network is, and an outside writer of a mesh file is a finding ... A VPN client rewrote the laptop's resolver file and every mesh name failed while each module read healthy: nothing judged the machine under them.	2026-10-07 20:33:23 +02:00
mesh-admin	f6aa1ced5e	Merge pull request 'Issue 295 and ADR 0242 (proposed): a recorded build moves only by a person's push, and a send says what it recreates' (#171) from issues/295-a-recorded-build-was-carried-by-a-plans-send into main	2026-10-07 18:33:14 +00:00
jochen	998980bbda	Issue 295: use the glossary's words (ADR 0244)	2026-10-07 20:24:59 +02:00