Answer A-297: the runner's step ask id takes the usual form, repeatable per placement

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 18:54:41 +01:00
parent ef76908e0d
commit 01fdde3701
1 changed files with 4 additions and 0 deletions
@@ -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:<seat>.views.<state>` 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.