From 4ac1cfb0b12254c562e8ad32833f42c9d58ce7af Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 19 Nov 2026 17:05:38 +0100 Subject: [PATCH] Answer A-490c..A-490e: the catalog's tag floor reads every tag of a module's form, per module with no version, in its own repository Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 11 +++++++++++ 1 file changed, 11 insertions(+) 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 c14b7aaa..6b2ab375 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 @@ -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. -- 2.54.0