Answer A-281: the switch runs once and marks it, so §716's deliveries never become records at a start

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 14:36:17 +01:00
parent a412c0760b
commit 14f908926e
1 changed files with 5 additions and 0 deletions
@@ -384,3 +384,8 @@ 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.