Design 47 G: lead answer A-313, over-bound step answers in the steps state's own objects store #593

Merged
mesh-tools merged 3 commits from design/47-G-lead-answers-21 into main 2026-11-12 21:41:15 +00:00
Showing only changes of commit a6d455f59c - Show all commits
@@ -520,3 +520,8 @@ the principle that settles it, cited as "design 47 G A-n".
held, the verb's reason named.
- **A-310's shape:** `composer.Manifest` is `{Raw, Digest, Fingerprint}` (wire `fingerprint`), and `composer.Fill`'s
getter takes the `Manifest`.
- **A-313** (corrects A-309 and A-290's "outputs store"; §58, §547, ADR 0666 §16; principle 7) A step answer over the
steps state's bound is kept in the steps state's own objects store, `steps-objects`, which the build module's
`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.