diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index 0f92e3c8..69244112 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -813,3 +813,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl answers them (step, seat, node, outcome, started, ended, why). (3) A delivery links to its pipeline by its source revision: the pipeline whose source equals the delivery's (list's `source` field); where several share it, the newest. The page refreshes on the events it hears, never on a timer. P-NATS-native, P3, P11. +- **H-A-467 (addendum, 11:15)** The runner's list row gains `source`, `revision` and `steps` (a map of counts per step + outcome) in the same change (the seat's form raised once, regenerated, read.go's row writer), so a page's list is one + read of the short form (one-question-one-tool, P3); the full form stays as it is. The view's developer makes the + runner's change in the same branch, since the view is its first reader. P3.