Separate the release paragraph from the execute bullet, and say the third call asks again

2026-10-10 22:00:27 +02:00
parent 1d6ee8885a
commit 8060c20fda
2 changed files with 2 additions and 1 deletions
@@ -239,6 +239,7 @@ The controller serves its own verbs and enforces the same mark on them, with the
  node, tracked by issue 418 (owner: mesh-tools, or the module that owns each area). Until then the control-node keeps withholding it and the others serve it unmarked,
  as ADR 0268 has it. Whether the control-node then serves it again, under the mark, stays the operator's
  setting.
+
 `mesh-delivery.release`, the glossary's "a person letting a held delivery go on", is not marked first. The
 controller's Release on a condition is already an ask, and the controller then calls `release` on its warrant;
 marked as it stands, that call would ask the operator a second time for the same act. How a warrant the