From 3acb50433aafb648074f6ac250c42692f2d944ea Mon Sep 17 00:00:00 2001 From: jochen Date: Thu, 12 Nov 2026 22:28:07 +0100 Subject: [PATCH] Answer A-314: the build modules' steps state moves into requires Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 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 6062a4f1..2ffb7fa7 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 @@ -525,3 +525,7 @@ the principle that settles it, cited as "design 47 G A-n". `requires` sizes with the state option `objects-max-mib: 256`; it lives as every `-objects` does (removed on replace, an object whose key is gone kept for the drop tool), so no `outputs` require and no age option for the objects template are added. A-309's lifetime line is withdrawn. +- **A-314** (A-313, §58, §547; principle 7) The three build modules' `steps` moves from the old `state` section into + `requires` as a state with `ttl-seconds: 172800` and `objects-max-mib: 256`; its bucket stays `_steps`, so + the seat's `steps` state is served from it as before. The step runner names the store through + `catalogue.StateObjectsName("steps")`, and the manifest validator accepts `objects-max-mib` on the state template.