diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 95462252..38b54407 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -1464,3 +1464,10 @@ Where two preparers disagreed, the chosen one is named. (pages in sequence order with an opaque cursor, a contract change in the SDK and its callers) is H2; in H1 the tool runner's page read stays as it is and nothing of H1 reads a large state in pages. P-NATS-native (a view followed, not a state replayed), P7. +- **H-A-256 (the assigner writes a pipeline's wants on its pipeline-ended event, 11:57)** Met live: the seat + mesh-wants' holder runs its pass (the assignment graph, the tiers' judgement, the wants written) only when a + catalog revision arrives, so a pipeline that passed waited five minutes for an unrelated merge's take-in before its + wants were written (proof 1's second run), and twelve minutes for an earlier one. The holder runs its pass on the + pipeline-ended event too (the event it already consumes for its records), and on the node-engine's running event + where a tier's judgement waits on a machine (ADR 0682: wants by the newest passed release, at once). P-NATS-native + (the event that changes the answer drives the pass), ADR 0282 (five minutes from merge to running).