Keep today's module mesh-delivery in the catalogue, unchanged: its removal follows the handover as a pull request of its own

2026-10-20 06:41:48 +00:00
parent cf5c02737b
commit 41f18b2452
70 changed files with 21205 additions and 0 deletions
@@ -0,0 +1,19 @@
+# mesh-delivery
+
+The `mesh-delivery` module of the mesh catalogue: claims the seat `mesh-delivery`.
+
+## Files it does not know
+
+Each directory or archive this module declares says how it treats a file it did not write (ADR 0422, ADR 0416).
+
+- `${dir:state}`: everything in it is the program's; the mesh moves nothing out (ADR 0422 §2).
+
+## A backup that failed before the send
+
+The controller backs up the data of the modules a delivery moves before it asks or sends anything (ADR 0404). When its
+walk's record, in `plan-moved`, names a backup that failed or stayed silent and nothing of the plan was sent, the
+delivery goes from delivering to held (the observed row `backup failed`); the held reason names the machine, the
+module and the backup's words, and the pull request's comment shows it. The hold does not lift by itself. `release`
+of such a delivery asks the controller (`delivery-backups-again`) to take the backups again and the delivery goes on
+delivering; a record from before the controller cleared the failure does not hold it again. A held delivery already
+ends as covered or delivered when a later merge covers it.