Merge pull request 'Design 47 G: the lead's answers A-490c..A-490e (the catalog's tag floor)' (#728) from design/47-G-lead-answers-137 into main

This commit was merged in pull request #728.
This commit is contained in:
2026-11-19 16:05:50 +00:00
@@ -2067,3 +2067,14 @@ the principle that settles it, cited as "design 47 G A-n".
first fill had not yet read the forge's tags (§412) does not outlive it. A trunk build whose reservation cannot be made
fails, and builds nothing. (Live 2026-11-19: the sdk reserved 0.1.0 while the forge holds `go/v0.1.16`, because the
catalog's `versions` answers no version for any module.)
- **A-490c** (§412; principles 6 and 7) The first fill reads every tag of the module's form from the seat `git`'s verb
`tags`, protected or not: inside the mesh every agent is trusted, so a tag's protection carries no need, and no verb or
field is added to read it. This amends §412's "only tags the forge protects".
- **A-490d** (§412, A-490b; principles 2 and 3) The tag floor is filled per module, for every module the catalog's
`versions` holds no version of, whenever the indexer starts and before it answers a reservation's read, not once: the
state key `versions-filled` closes the builder's half of the fill only. A module whose tags cannot be read (the
forge does not answer) is not filled and is said, `call-unanswered` after five minutes, as §412 has.
- **A-490e** (§412; principles 7 and 10) A module's tags are read in the repository its catalog entry was taken in
from, with the prefix Go itself gives a module's tags: the Go package's directory in that repository followed by
`/v` (`go/v` for the sdk, whose Go module lives in `go/`; `v` for a module at the repository's root). A module with no
Go package has no tag floor.