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 70a9c313..ac2ff55b 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 @@ -649,3 +649,12 @@ Where two preparers disagreed, the chosen one is named. 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. +- **H-A-140 (a login not handed, met by a newer lease of its own account, 14:47)** Met live at the first start of the + fixed node side on the desktop: its file held a login of 13:51 to the gmail account, not handed; the manager had + adopted a later login to the same account from the laptop at 14:43 and handed its lease; the node side kept the older + login ("login kept: not handed"), so the desktop would keep a stale login, with its refresh token, for good. The latest + login wins (design 39 ยง6): a login not handed is kept only against a lease that does not succeed it; a lease of the + same account (the identity the login's account file names is the lease's licence) that succeeds it (H-A-139: the + 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.