From 93039639e5db0f9f150776cd1f6f484f96c0dcb7 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 22 Nov 2026 02:22:57 +0100 Subject: [PATCH] Design 47 H2: H-A-453, mesh-catalog's review round 1 answers --- 03-DESIGN/01-to-be/47-milestones/H2-lead-answers.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) 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 b6ca8ff3..3af518e4 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 @@ -671,3 +671,16 @@ The lead's one-line answers to the questions H2's develop and review raise (impl seatlisttest, the one test seat list every repository's tests share (P3), so the refresh is a mesh-sdk commit: seatlisttest gains the mesh-recovery seat and every other definition the group's heads hold that it lacks, resolved as the live list is; no captured list of the validator's own. P3. +- **H-A-453 (mesh-catalog's review round 1, 02:52)** (1) P2 (§781's converged timeout) is not H2's: H-A-350 DMC-12 gave + the converged verb, its timeout and the allow to the packet filter group, merged on 21 Nov; the row is closed, no code. + (2) A package outside every artifact's `from` (the forge module's internal/seatgit whole test, which needs the Node build + seat) declares its need at the module's level: the manifest's top-level `check-needs` (a list of seat names, the same + form as an artifact's), read by the Go build module for the packages no artifact's `from` holds; gitea declares + `check-needs: ["node-build-node"]`; mesh-sdk's `catalogue.Manifest` gains the field (one line). (3) A whole criterion is + proven at its level: GT1 (§809), GT2 and SC1 (§810), RG3 (§813 (8)) and C4 (§808 "the forge holds one token after") each + become a step of their module's existing whole test, no new top-level function; P1 (§813 (4)) stays a unit test, since + no whole packet-filter test exists (noted for H2b). (4) §819 reads as the test-budget instruction has it: a module's + count never rises in a change, and a module over budget shrinks with every change that touches its tests; a module + whose count stands where it was is accepted this milestone (the fold of nine modules' tests would cost more than the + rule protects tonight: rules-are-weighed, said here). The fills gitea's caps rest on are written in a commit (H-A-437), + and tweetnacl is declared where test/fakebus.ts imports it. P3, rules-are-weighed.