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
parent ca1f648973
commit c74ea2a4a8
8 changed files with 74 additions and 38 deletions
@@ -300,8 +300,12 @@ cutover. The firewall found there stays in force and the mesh opens what it need
 ([08-connectivity](08-connectivity.md)). **Converging is one act per node, previewed**: it refuses
 while an assigned module still holds a found container; otherwise it lists what is reachable on the
 machine now — listening sockets and published ports — whether an assigned module declares each or
-it will close, and which modules it will take, then takes them, loads the mesh's own filter in place
-of its refusal-only table and disables the found firewall without flushing it. Returning a
+it will close, which modules it will take and every held thing each will replace, and ends with a
+short digest of all of that. **The flip is made only with that digest** — the operator confirms
+the preview they read, and a preview that has changed since, or whose account of the machine is
+more than fifteen minutes old, is refused. It then takes the modules, loads the mesh's own filter
+in place of its refusal-only table and disables the found firewall without flushing it, putting
+back the forwarding policy the found firewall had set. Returning a
 converged node to adopted unloads the derived filter, restores the refusal-only table, enables the
 found firewall again and converges the openings through it; what was taken stays taken. *How it is checked:* a lab bed prepares a machine the way
 a predecessor leaves one and asserts nothing that serves changes until a module is taken or the