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 1930b40c..70a9c313 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 @@ -640,3 +640,12 @@ Where two preparers disagreed, the chosen one is named. the manager marks it) replaces it; a lease older than the login it would replace is never written, whether the login was handed or not. The apply says so in the journal ("login kept") and reports it, so the manager's failed refresh is a finding on the manager, never a lost login on the node. P3. +- **H-A-139 (how the node tells the handed login's successor from an older lease, 14:26)** Met in the review of + H-A-138's build against the manager's holdings: the manager's refresh keeps a licence's refresh-token expiry (a + licence adopted on 2026-10-27 and rotated on 2026-11-20 still expires on 2026-11-24), so "a newer lineage" alone + never names the successor of the login the node handed, and the node would keep the login, with its refresh token, + for good (against design 14). A grant replaces a login the file holds when its lineage is newer (H-A-138), or when it + is of the same lineage (two refresh-token expiries within a day, as DecideApply reads one generation) and its access + token expires later than the login's: only the manager's refresh of that login yields such a grant. A grant of the + same lineage whose access token expires no later than the login's, or of an older lineage, or with no lineage mark + at all, is the older lease, kept out with "login kept". P3.