Answer A-167: the assigner's composition step, held entries, reverts

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 7ebdfb3278
commit b13dc2bfc4
1 changed files with 9 additions and 0 deletions
@@ -623,3 +623,12 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  consumer) holding the time its oldest unacknowledged message was delivered, written when a message is delivered or
  acknowledged; `runner_health` works the age out as now minus that time when it is read, so nothing is read on a
  timer.
+- **A-167** (§354, §63, §22, §64, §357, §298; principles 1, 2, 3 and 7) For the assigner's composition step (AS5): its
+  `run` builds the node-engine's composer (`mesh-compose`) at the fingerprint the node-engine runs; each machine's
+  input is asked of that node's engine by `compose-candidate`; the machines are the nodes the branch's revision places
+  the module on; a node is asleep when the watchman's `machine-away` is heard for it; `mesh-compose` reading
+  `MESH_RUN_INPUT` and answering the run's output is the node-engine's, a row of its own. An entry held for want of a
+  provider (AS14) carries a field `held` naming the candidates, never only a log line. A revert (AS17) is a want that
+  goes back to an earlier fingerprint, which the assigner computes itself; a kept data's `form` is read from the
+  catalog entry's kept declarations (`catalogue.KeptDeclarations`). AS14's named seat and contribution edge, and
+  AS17's ask of the operator, go to a design line.