Design 47 H: H-A-383, the node-engine's taken state names its cap; the baseline gains state.max-mib

This commit is contained in:
2026-11-22 00:04:26 +01:00
parent e6c7bc1d06
commit b6d44d1bd6
@@ -2405,3 +2405,12 @@ Where two preparers disagreed, the chosen one is named.
revisions included, each later revision of a key already handed marked seen-again by (1); only the first page may
ask last-per-key, and it does not: one way for every page (P3), as §779's acceptance says ("delivers each kept
message once"). P3, P-NATS-native, H-A-227.
- **H-A-383 (the node-engine's taken state names its cap; the baseline gains the word, 00:20)** E2. §820 gives every
holder's `taken` 8 MiB, and every kept store names its cap (§812, ADR 0595); the node-engine is no exception. Its
manifest declares taken {history 1, key-ttl, max-mib 8}. The word `state.max-mib` is one the engine reads already
(it writes every module's bucket cap from it), so mesh-sdk's baseline manifest reads (ADR 0614 §4) were incomplete:
the baseline gains `word:state.max-mib`, in the same group, and packaging/operator_keys_test.go follows the baseline.
The running engine on each node holds the new engine's build for a yes once, at this delivery, because its baseline
lacks the word: that hold is said to the operator before the delivery starts and answered then; it is the delivery
system doing what ADR 0614 asks, not a reason to leave the store uncapped (design-it-as-it-should-be).
P-failure-loud, §812, ADR 0614 §4.