Answer A-232: the validation run rides the check queue with the usual id

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 09:41:28 +01:00
parent 1c29c4bc56
commit f8986a5541
1 changed files with 4 additions and 0 deletions
@@ -205,3 +205,7 @@ the principle that settles it, cited as "design 47 G A-n".
  as `seat:<seat>.accept.<queue>`, read by one mesh-sdk `catalogue` helper that the validator, the indexer's kind-6
  edge and the grants part share; every asker of a build seat gains that entry in G, so the named workers stand from
  G's delivery and the purge finds nothing to remove.
+- **A-232** (§712 with §600, A-163, A-170; principle 7) The validation run rides `accept.check.<asker>` with its kind
+  `run` in the body and the asker the indexer's seat name `mesh-catalog`, as every ask does; its id is the usual
+  form (`NewID`), and the revision's sequence and try number are kept in the pending value's `validation`. §712's
+  subject and id are read so.