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 d47b6e9f..061babe1 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 @@ -2397,3 +2397,11 @@ Where two preparers disagreed, the chosen one is named. minutes (the largest caller's bound, the runner's ask-unanswered-bound), declared in the registry's and the forge module's manifests; the node-engine keeps compose-ask-bound as H-A-364 (a) decided. §775's "the ask's bound" reads so. P3, ADR 0668 §2, principle 11. +- **H-A-382 (a page by cursor: seen-again and each kept message, 00:16)** §779, T1. (1) The runner keeps nothing per + read and a bucket keeps no trace of a key's removed older message, so seen-again marks every message written after + the read's first page (the cursor carries that page's stream sequence), a key first created after the read began + included: no state per read in the runner's memory (the mesh owns the truth, P-NATS-native), and a reader replacing a + value it does not hold loses nothing. (2) A page hands each kept message in sequence order, a key's older kept + revisions included, each later revision of a key already handed marked seen-again by (1); only the first page may + ask last-per-key, and it does not: one way for every page (P3), as §779's acceptance says ("delivers each kept + message once"). P3, P-NATS-native, H-A-227.