Answer A-313: over-bound step answers live in the steps state's own objects store
mesh/delivery closed: a newer head of the same pull request
mesh/check checking a6d455f59cfb on 0bf9465cbab6
mesh/delivery closed: a newer head of the same pull request
mesh/check checking a6d455f59cfb on 0bf9465cbab6
A-309 named an age option the objects template does not have. Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
@@ -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.
|
||||
|
||||
Reference in New Issue
Block a user