diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index bf6482b2..9a48e1a7 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -2081,3 +2081,13 @@ the principle that settles it, cited as "design 47 G A-n". - **A-490f** (A-490d; principle 7) A-490d's "before it answers a reservation's read" is met by the indexer program filling the tag floor at its start and after every catalog revision it keeps: a module enters `versions`' reach only through a revision, so the tools process that answers `versions` reads the state and triggers no fill of its own. +- **A-490g** (ยง412, A-490e; principles 2 and 9) A module's floor is the highest version among every package its + catalog entry names, in each ecosystem: its Go tags (A-490e) and the versions each package holder answers for its + package through its seat's verb `versions` (`npm-package-registry`, `go-package-registry`). A version a holder + already holds is never reserved again. (Review round 1 of the tag-floor fix: the npm holder holds `@novox/mesh-sdk` + up to 0.1.18 while its Go tags end at 0.1.16.) +- **A-490h** (A-490d, A-487a; principle 3) A floor read the forge or a holder does not answer is asked again on a + growing pause, as A-487a has a node-engine ask a missing trunk build again, until it answers; `call-unanswered` is + raised five minutes after the first unanswered read and cleared when it answers. A floor entry holds no artifacts: + a `package-published` heard later at the same version is recorded as that version's release, never dropped as + released already.