Answer A-170: an ask's kind is in its body, the subject names queue and asker

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent a2f2e5b98d
commit 17f8ec2fbb
1 changed files with 4 additions and 0 deletions
@@ -639,3 +639,7 @@ names the principle that settles it, and is cited as "design 47 G A-n".
  `trunk.<n>`, the indexer's `<branch>.<revision>`), value `{records, missing?}`, and holds two more keys in the same
  form in every holder of pins: `made`, written once by create-only when the state is first used, and
  `pins-stated`, the `at` of the applied event; pins count only once a `pins-stated` later than `made` is applied.
+- **A-170** (§600, §481, §415, A-163; principles 7 and 8) Every ask to a build seat rides `accept.<queue>.<asker>`;
+  its kind is in its body only, as §600 says. A build seat definition's `stream` names only the queue, and the
+  generated accept subjects follow; the kind in the subject goes. §543's main subject takes `build` and `run` as
+  written, the checker's asks riding it until it goes.