From bdd86986dec95682a4066ea2b6892ce79c6b72f1 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 19 Nov 2026 17:11:38 +0100 Subject: [PATCH] Answer A-490f: the tag floor filled at start and at every revision meets A-490d Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 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 6b2ab375..bf6482b2 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 @@ -2078,3 +2078,6 @@ the principle that settles it, cited as "design 47 G A-n". 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. +- **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. -- 2.54.0