diff --git a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md index 1ea40645..5ecea169 100644 --- a/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/H-lead-answers.md @@ -2362,3 +2362,10 @@ Where two preparers disagreed, the chosen one is named. seconds" is the rendering, never the setting's form. The runner reads drain-bound with stdio.SettingDuration, 30 s default; no seconds reader is added to mesh-sdk. The node-engine's developer changes drainBoundOf (E3's counterpart), the tool runner's developer reads it. P9 (one reader, one form), H-A-370. +- **H-A-378 (S8 changes no mesh-sdk code, 00:02)** §783's finding events (the events template, 8 MiB drop-oldest, + findings-max-age) are each module's manifest entry; the writer already says its events under the finding-events + binding when bound. S8 in mesh-sdk is done by what exists: no refusal in the writer, no exported constants (a + manifest is text the SDK's constants cannot reach). The one place that holds the numbers is §814's manifest + validator in mesh-catalog (the finding-events binding's cap 8 MiB, drop-oldest, the setting findings-max-age with + its 7-day default), and the catalogue's module.json rows carry them. The mesh-catalog developer builds the validator + rule with the rows; the mesh-sdk developer closes S8 as built. A rule states how it is checked (hq), P9.