From 383f21ed4906798818f0cadbc795003e99c2fb92 Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 22:03:26 +0100 Subject: [PATCH] Answer A-309: a build module's outputs objects live as long as their step keys Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 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 0e128a54..c59be226 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 @@ -502,3 +502,6 @@ the principle that settles it, cited as "design 47 G A-n". whole: `candidates`, `manifests` and `verdicts`, for compose-candidate alone. Its watch of the indexer's `modules` (selfcompose shadow.go) goes; what it took from a module's record it reads from the catalog half's entry the want names (ยง421). +- **A-309** (A-290, A-254, research 071; principles 7 and 2) A build module's `outputs` objects live as long as the + step key that names them: the store's age is the steps state's time to live (two days), its cap 256 MiB, and the + bus's own age removes an object; nothing else deletes one. The milestone's lifetime list gains this line.