From 01fdde3701b8d45863a56f3929e6854b9b61e267 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 18:48:19 +0100 Subject: [PATCH] Answer A-297: the runner's step ask id takes the usual form, repeatable per placement 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 1fb772fd..9c33975e 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 @@ -455,3 +455,7 @@ the principle that settles it, cited as "design 47 G A-n". manifest takes the seat forms in the same change (`seat:.views.` for a consume, the seat's verb for an invoke), and a part names its own buckets from its credential's module, never from a constant. Which seat a module that holds none (the delivery view) or several (the assigner) is found by is a design line (ยง717). +- **A-297** (A-232, A-111; principle 7, one form per fact) The pipeline runner's step ask id takes the usual ask id + form: base 36 of the pipeline's start time in milliseconds, then six hex digits of the sha256 of the pipeline, the + artifact and the step, so the same placement makes the same id at every start (and the bus dedupes on it); a rerun + uses its own start time.