Answer A-314: the build modules' steps state moves into requires

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
2026-11-12 22:28:07 +01:00
parent a6d455f59c
commit 3acb50433a
1 changed files with 4 additions and 0 deletions
@@ -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 `<state>-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 `<module>_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.