From 012ff6ef6289f9101ab78368390cc1e797be7713 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 20:39:52 +0100 Subject: [PATCH] Design 47 H: H-A-313 and H-A-314, the stalled pipeline's journal line; the packet filter's design after the seams review --- .../01-to-be/47-milestones/H-lead-answers.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) 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 7da6d803..43f33b6f 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 @@ -1863,3 +1863,23 @@ Where two preparers disagreed, the chosen one is named. removes every expired allowance before it answers allowed and says allowances-changed; while the holder is away, the loaded filter keeps an expired port open until it is back (the filter is kept rather than every port closed), and that is accepted and said in the record. P-failure-loud, H-A-310. ADR 0683 carries both. +- **H-A-313 (the stalled pipeline's journal line is the tools program's, 20:39)** Amends H-A-311 (3): the runner's + process hears events only; the health runs in the tools program; so the line is written by the tools program to + its journal when its health first names a pipeline's key, once per key for that program's life; the health answer + itself is the loud part. No new bound key. P-failure-loud, P3. +- **H-A-314 (the packet filter's design, the seams review's eight points, 20:39)** (1) ADR 0683's fifth version carries + H-A-308, H-A-310 and H-A-312. (2) The seat's whole definition: family node-packet-filter.events with max-age-days 7; + the event's subject allowances-changed. (as the node-engine seat's composed.); the state allowances + keeps history 1; the model is the node-engine's and git's whole definitions, not the private network's. (3) The + node-engine's manifest gains invokes seat:node-packet-filter.allowed and consumes + node-packet-filter.allowances-changed; the packet filter's manifest serves the six verbs, emits the event and + requires allowances by the state template. (4) The TypeScript SDK's state() asks the runtime's mesh/state methods + as Go bundles do, so there is no SDK gap: three repositories, the SDK out. (5) Two settings with defaults: the + node-engine's compose-ask bound (10 s) and the packet filter's allowances-max (100). (6) The expiry is an + in-process timer armed from the watch of the holder's own state at every start; a start past an until deletes the + key at once and says expired; the node-engine drops nothing past an until, the holder's answer is the truth (the + acceptance test at 08-milestones/control-verbs.md:83 follows line 6). (7) The refusal in the composition read is a + withheld part in H-A-306's form, the holder asked node-packet-filter.allowed; recovered by hand with the node- + engine's compose verb and loaded with reload. (8) The acceptance test first shows a home-network machine refused + before allow (today's render accepts every link that is neither outward nor the tunnel: the test must prove the + drop first). P7, P11 (settings with defaults), P-failure-loud.