 jschoubben
|
7bbbfb158a
|
ADR 0103: a unit is found when an administrator installed it or the machine uses it
|
2026-09-22 20:02:18 +02:00 |
|
|
jschoubben
|
87ae893407
|
Issue 087: the controller cannot tell that a node's host is too old for what it sends
|
2026-09-22 19:43:01 +02:00 |
|
|
jschoubben
|
c74ea2a4a8
|
Records say what the build does: 0101 names only measured daemons; 0102 adds to lists and keeps what it writes over; 0103 names every held kind, the found-service rule, conflicting found rules, guards, and what of 0100 it replaces; designs 05, 09 and 17 in step; issue 084's diagnosis in its own file
|
2026-09-22 19:38:16 +02:00 |
|
|
jschoubben
|
ca1f648973
|
Issue 086: taking a module narrows a port the predecessor served, without saying so
|
2026-09-22 19:00:59 +02:00 |
|
|
jschoubben
|
019184ec0f
|
Issue 085: the packages port given at genesis is not a setting, and a later module can undo it
|
2026-09-22 18:17:21 +02:00 |
|
|
jschoubben
|
213ab898d6
|
ADR 0103: what an adopted node holds and what its guard refuses; the node host and connectivity designs name 0102 and 0103
|
2026-09-22 17:52:58 +02:00 |
|
|
jschoubben
|
84761f0600
|
ADR 0102: the mesh writes into a shared file, never over it; issue 084 located
|
2026-09-22 17:46:06 +02:00 |
|
|
jschoubben
|
1901a90d68
|
ADR 0101 accepted; raising a mesh names it
|
2026-09-22 17:43:13 +02:00 |
|
|
jschoubben
|
347bbce633
|
ADR 0101 proposed: a machine's own resolver does not make it in use, as measured on a fresh machine
|
2026-09-22 17:38:44 +02:00 |
|
|
jschoubben
|
6165a7ae02
|
Issue 084: taking networking on an adopted node restarts every container, and the held runtime file blocks pulling
|
2026-09-22 17:09:21 +02:00 |
|