diff --git a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md index f0191864..12b5a0d8 100644 --- a/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md @@ -535,3 +535,11 @@ The lead's one-line answers to the questions H2's develop and review raise (impl cannot read one, and a reader the SDK's Pruner would need for an age rule is a read §812 forbids); §812's "performed-keep (default 3 days)" reads so. Confirmed: performed, heads and owed-asks at `max-mib` 8; the tools named `mesh-delivery-forge-bridge_state_prune_now` and `_state_keep`. P-NATS-native, P3. +- **H-A-434 (the objects template gains max-age-days, 01:34)** §820, §791, BM4. ADR 0595 §3 fixed the objects template + as kept for good and refusing when full; §820 gives `outputs` a max-age of 7 days the bus applies, no sweep (P-NATS- + native: the bus deletes, nobody polls). The template gains the option `max-age-days` (optional; absent keeps for good + as today): mesh-sdk's `catalogue` package accepts it (a one-line commit in the mesh-sdk worktree by the build modules' developer, + citing this answer), the bus module's keeper applies it as the object store's stream MaxAge (modules/nats + internal/keeper/plan.go, the same developer, a row in the keeper's tests), and the validator accepts it on objects + (the indexer's developer, I6). The three build modules declare `outputs` {max-mib 1024, max-age-days 7}. A progressive + insight on ADR 0595 §3 is proposed with H2's record (the option, not the decision, changes). P-NATS-native, P3.