Answer A-64: the bus module's wire forms, as built, and its finding's scope

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-11 22:56:41 +01:00
parent a062015501
commit c1d331da40
1 changed files with 5 additions and 0 deletions
@@ -249,3 +249,8 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  failing check's time, also when it first rests on `conditions-unread`; while the keeper has not answered, a first
  failing check holds as the settle and becomes `conditions-unread` only after it, and a standing wait keeps its cause
  while a new read is out.
+- **A-64** (§681, A-45; principles 7 and 8) As built in mesh-catalog 47aaee12: a chunk's body is `{n, of, data}`; a
+  restore's act id is the id of the request the bundle hands the keeper; `verify` answers `accepted` with that id and
+  says no event; an unprotected snapshot's restore refuses nothing further; each chunk is acknowledged by a request,
+  since the runtime answers only calls with a reply. One change: `snapshots-filling` takes an existing scope word,
+  scope `module`, id `nats.snapshots`.