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 a3353d25..407f0365 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 @@ -705,3 +705,9 @@ The lead's one-line answers to the questions H2's develop and review raise (impl measures mover entries only): a write over it raises record-too-large and the record's end clears it, whichever entry it was (P-failure-loud). GT1's whole step stands as written: 126 movers write 127 entries plus the acts of the moment, none over 64 KiB. P3, P-failure-loud. +- **H-A-456 (RG3 is proven where each act lives, 03:25)** ยง813 (8). The chunk's delete is distribution's act and the + purge is the tool runner's (the runtime's answer to the objects delete): distribution proves it asks the purge for a + deleted chunk (bounded_test.go's unit test stands as RG3's), and the purge of an object's leftovers is proven in the + tool runner's own tests of the objects delete, where it already is or where it is next touched (noted for H2b if it is + not there); no new whole test of distribution-tools, and mesh-tools, approved tonight, is not reopened for it + (rules-are-weighed, said here). H-A-453 (3)'s RG3 line is amended so. P3.