Design 47 H2: H-A-396, gate_times names each class's newest delivery for the probe
This commit is contained in:
@@ -217,3 +217,10 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
|
||||
(the baseline states what the running engine reads, ADR 0614 §4; state.max-mib joined because it does). The
|
||||
node-engine's manifest at `class: core` and `declaration-reads: 2` is held for a yes once at this delivery, one hold
|
||||
for both words, said to the operator with H-A-383's.
|
||||
- **H-A-396 (gate_times names each class's newest delivery; the probe judges that, 01:35)** §810, SC1. gate_times answers
|
||||
per class `last`: the newest ended delivery (record, ended, delivery-time, over true or false, its longest phase)
|
||||
beside the budget, the seven days' median and worst and the deliveries over budget. The self-check's over-budget
|
||||
probe is a registry row (kind over-budget, id core or leaf) invoking mesh-delivery-gate.gate_times: it raises when
|
||||
`last` is over and clears when it is not; it reads no records itself (one read, one tool: tools-are-how-a-module-is-
|
||||
spoken-to, one-question-one-tool). H-A-394 (2) read as the developer did: a record has no movers at its open, so the
|
||||
gate reads a mover's class once when that mover's entry opens, with its fingerprint. P3.
|
||||
|
||||
Reference in New Issue
Block a user