From f8986a5541a90582f02a80139d330880e7fe84ac Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 06:15:59 +0100 Subject: [PATCH] Answer A-232: the validation run rides the check queue with the usual id Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 65a60099..2be73c6a 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -205,3 +205,7 @@ the principle that settles it, cited as "design 47 G A-n". as `seat:.accept.`, 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.` 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.