Answer A-261 to A-263: a request's seats by digest, the step's beat, a Go bundle's package

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:44:29 +01:00
parent 5b39ffcfd0
commit 9de6b0fb15
1 changed files with 9 additions and 0 deletions
@@ -312,3 +312,12 @@ the principle that settles it, cited as "design 47 G A-n".
  `take-in.taken` of the trunk branch with `source` at or above it is heard. The assigner consumes
  `mesh-delivery-indexer.take-in.taken` (a `consumes` entry), heard as it hears `build.ended`; a wait still held
  after a restart is said again as `wait-held` and ends at the next such take-in.
+- **A-261** (A-252, A-234; principles 2 and 3) A composition request's `Seats` carry, for each (seat, digest) of the
+  step's catalog revision, the definition whose digest it is: from the revision's `definitions` once A-234 fills
+  them, until then from mesh-catalog's `seat-definitions` where the trunk's digest matches; a digest neither holds
+  ends the step `could not run`, naming the seat and the digest.
+- **A-262** (§496; principles 1 and 7) The assigner says a running composition step's progress once a minute with a
+  ticker inside the running step, stopped at its end, as mesh-delivery-sdk's `steprun` says its own beat (pull.go);
+  no bound key and no new key form.
+- **A-263** (§712, §676; principles 7 and 8) §676 writes `package` (the Go module its `go.mod` names) for every Go
+  artifact, a `bundle` too, since a bundle is built from that Go module; §712 reads it there.