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 70f2e95e..1930b40c 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 @@ -633,3 +633,10 @@ Where two preparers disagreed, the chosen one is named. the `seats/` directory the generator reads and the paths of every artifact of the module that names `generated-from` (the generator's check reads every generated package, and one left out counts as missing). Nothing else of the root. A module in its own directory keeps that directory, as H-A-136 says. P7, P3. +- **H-A-138 (a handed login whose successor never comes, 14:02)** Met in the build of the licence fault of this + morning (a login made on a node was overwritten by the next apply of the binding's older grant, five times): once + the node has handed a login to the licence manager and the manager's refresh of it fails, may any grant replace + it? Only a grant of a newer lineage than the handed login (its refresh token's expiry later than the login's, as + 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.