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 ac2ff55b..bb91c106 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 @@ -658,3 +658,15 @@ Where two preparers disagreed, the chosen one is named. same lineage with a later access expiry, or a newer lineage) replaces it, said as "login superseded" with the lease's licence and generation. A login to another account than the lease's licence is always kept until the manager adopts it (ADR 0209: a login re-binds its node), whatever the lease's age. P3. +- **H-A-141 (a reader whose picture holds a revision above the ones it hears, 15:00)** Met live twice at the clean + state: the runner's view said "528 heard, picture holds 3" at 12:30 and was restarted by hand; the builder's view of + main's catalog revisions held 528 from its first view at 09:14, skipped revisions 1 to 7 in silence (the catalog + client drops an event at or below the held revision), built every step since as a candidate's build with no version, + and so no pipeline released anything and no want moved (§750, §754). H-A-135 said the stale readers' first views + "then agree" and named no way for a running reader to learn that a numbering started again. The catalog client + (mesh-delivery-contracts, the views reader of the seat `mesh-catalog`) treats an event whose revision is below the one + its picture holds as the state made again: it says so in the journal (the held and the heard revision) and asks its + first view again, so the picture follows the new numbering; an event equal to the held revision is still dropped. + At this clean state the hand act stands in once: the builder's first view asked again (15:00). A build step asked + before the builder's view took in that revision's event, and a passed pipeline whose mover released nothing, are + findings for H2 (§756, §754). P3 (failure must be loud), P7.