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 e88f7fe2..ea645643 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 @@ -881,3 +881,10 @@ Where two preparers disagreed, the chosen one is named. the event hub tells a hook of each unhandled subject, the process reader wires it where it holds a findings writer and clears the finding at its start, since a new build may handle the event; without a findings writer the journal line stands alone, as today. P3, P9, P7. +- **H-A-170 (the release pin's record and what frees it, 17:42)** Met in the build of H-A-168: the assigner's + `written` is its own state, written before any want, and no event says it. The indexer pins on a passed + pipeline-ended under a record `release..`, one per mover of that pipeline, on the pipeline's kept + revision; it frees that record from every revision below a newer pipeline's on `pipeline-wanted..` + (the seat mesh-wants' event, said once when a pipeline's wants are written to the end, tier-late included), for + each module the newer revision's movers name. The indexer consumes that event (its manifest says so). A revision a + release pin holds keeps its entries as today. P1, P2, P7.