2026-11-12 14:04:49 +00:00
1 changed files with 12 additions and 0 deletions
@@ -384,3 +384,15 @@ the principle that settles it, cited as "design 47 G A-n".
  membership that carries it (`node-tools` `bus.eventSubject`). The grants part lists a module's required
  `finding-events` stream in its membership with that subject and the finding events, so a bundle's findings land
  under its binding as a process's do; with no such stream they stay on EVENTS.
+- **A-281** (§156, §716; principles 2 and 7) The switch runs once, as §156 says: after it has carried today's state in,
+  the gate writes the key `switch.done` (the gate's fingerprint and the time) in the state that holds its records, and a
+  later start that finds it runs no switch, so the deliveries §716 writes never become records at a start. A revert's
+  restore brings back the state from before G without the key, so delivering G again switches again, still safe to run
+  twice by the record's key.
+- **A-282** (A-115, §544, issue 1930; principles 3 and 7; corrected once) An ask's step bound key is never deleted
+  to be made again. `stepBounds.Arm` creates it if absent; when the step moves, the waiter writes it again by an update
+  against the revision it read, so the bound still counts from the step's last movement (issue 1930); a waiter whose
+  update loses to another's reads the key again and takes the newer bound as armed.
+- **A-283** (A-277, ADR 0595; principle 7) The holder of the seat `mesh-broker` makes a template `state` bucket with
+  the `max-mib` its requirement declares, the default cap where none is declared, as the grants part does for a
+  state section; one cap rule for every state bucket.