Answer A-309: a build module's outputs objects live as long as their step keys

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 22:03:26 +01:00
parent 1b9c63e947
commit 383f21ed49
1 changed files with 3 additions and 0 deletions
@@ -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.