Design 47 H2: the lead answers' times read from the clock

This commit is contained in:
2026-11-22 00:34:43 +01:00
parent 270f469fa1
commit 9981bcbfc3
2 changed files with 22 additions and 22 deletions
@@ -2315,4 +2315,4 @@ Where two preparers disagreed, the chosen one is named.
with an empty version, so the builder says "package-published not said … a by-digest publish" and the bundle is
not marked against its reservation. Fix in the Node build module: the publish carries the version the ask
reserved. Test: a bundle's publish names the ask's version. P3, P-failure-loud.
- **H-A-373 and later** are in H2-lead-answers.md (this file was split at 00:40 CET on 22 Nov; it ends at H-A-372).
- **H-A-373 and later** are in H2-lead-answers.md (this file was split at 00:13 CET on 22 Nov; it ends at H-A-372).
@@ -64,7 +64,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
gain `install`: every pipeline ask ends in a step-ended naming its step, one way, and the archive object's name rides
the install's end as §800 says. The contract part (mesh-contracts, regenerated) and the delivery SDK's check change
together in the group; the Node build module's install answers it. P3.
- **H-A-380 (the prune helper for a process, the keep's home, the tools' names, 00:08)** §812, S11. (1) A process's
- **H-A-380 (the prune helper for a process, the keep's home, the tools' names, 00:02)** §812, S11. (1) A process's
state write over the bus's key-value put answers a revision and no fill (the bundle side gets the Fill the runtime's
put answer carries, DMC-14). The helper for a process reads the entry's figures once when it binds the state and once
after each prune, and between those keeps a running sum of the bytes each write puts (an upper bound: the bucket's
@@ -76,7 +76,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
first. No new store per module (one store per thing, P3). (3) The tools are named as the generic tools are:
`<module>_state_prune_now` and `<module>_state_keep` (stateobjects.Tools' form); §812's bare names are the tool
kind. P3, P9, P-NATS-native.
- **H-A-381 (a repeat of a taken ask, and the taken key's bound, 00:12)** §775, RG1 and C2. (1) A holder that is asked
- **H-A-381 (a repeat of a taken ask, and the taken key's bound, 00:02)** §775, RG1 and C2. (1) A holder that is asked
again with an id it took follows H-A-364 (b): while the first act still runs the repeat joins it and gets the same
answer; after it ended the repeat answers the act's state as it stands, read afresh (the registry's publish answers
the transfer's parts held; a git verb answers the pull request as it is: merged, with its merge commit), which is
@@ -86,7 +86,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
minutes (the largest caller's bound, the runner's ask-unanswered-bound), declared in the registry's and the forge
module's manifests; the node-engine keeps compose-ask-bound as H-A-364 (a) decided. §775's "the ask's bound" reads
so. P3, ADR 0668 §2, principle 11.
- **H-A-382 (a page by cursor: seen-again and each kept message, 00:16)** §779, T1. (1) The runner keeps nothing per
- **H-A-382 (a page by cursor: seen-again and each kept message, 00:03)** §779, T1. (1) The runner keeps nothing per
read and a bucket keeps no trace of a key's removed older message, so seen-again marks every message written after
the read's first page (the cursor carries that page's stream sequence), a key first created after the read began
included: no state per read in the runner's memory (the mesh owns the truth, P-NATS-native), and a reader replacing a
@@ -94,7 +94,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
revisions included, each later revision of a key already handed marked seen-again by (1); only the first page may
ask last-per-key, and it does not: one way for every page (P3), as §779's acceptance says ("delivers each kept
message once"). P3, P-NATS-native, H-A-227.
- **H-A-383 (the node-engine's taken state names its cap; the baseline gains the word, 00:20)** E2. §820 gives every
- **H-A-383 (the node-engine's taken state names its cap; the baseline gains the word, 00:04)** E2. §820 gives every
holder's `taken` 8 MiB, and every kept store names its cap (§812, ADR 0595); the node-engine is no exception. Its
manifest declares taken {history 1, key-ttl, max-mib 8}. The word `state.max-mib` is one the engine reads already
(it writes every module's bucket cap from it), so mesh-sdk's baseline manifest reads (ADR 0614 §4) were incomplete:
@@ -103,7 +103,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
lacks the word: that hold is said to the operator before the delivery starts and answered then; it is the delivery
system doing what ADR 0614 asks, not a reason to leave the store uncapped (design-it-as-it-should-be).
P-failure-loud, §812, ADR 0614 §4.
- **H-A-384 (three node-engine lines the developer thought wrong, 00:24)** (1) §813 (4), H-A-357: the nft comment is a
- **H-A-384 (three node-engine lines the developer thought wrong, 00:05)** (1) §813 (4), H-A-357: the nft comment is a
label, the composition is the truth. Past 128 bytes the module list is cut with a count, `derived a,b,+4 tcp/443
scope any`, the whole list standing in the composition's filtering resource; the holder's rules reading (mesh-catalog
P1) reads that form; the compose never refuses for a label's length (a refusal would take the whole table down for a
@@ -115,9 +115,9 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
edge node-engine (the reader of the new form) before the composer that writes it; the older engine's strict decode
stays strict. The edge is named in the milestone plan with this answer (design-it-as-it-should-be). P3,
P-mesh-owns-the-truth.
- **H-A-379 (addendum, 00:24)** The install ask carries no artifact or fingerprint, so the delivery SDK's check takes an
- **H-A-379 (addendum, 00:05)** The install ask carries no artifact or fingerprint, so the delivery SDK's check takes an
install's end without them, naming module, commit and the archive (mesh-delivery 1767d7b4).
- **H-A-385 (the gate's ledger entries: what each keeps, 00:34)** §809, GT1. (1) The head entry `<branch>.<source>`
- **H-A-385 (the gate's ledger entries: what each keeps, 00:08)** §809, GT1. (1) The head entry `<branch>.<source>`
keeps every field about the record as a whole: group, trace, acts, away, recovery, call, the pull requests' heads,
with its outcome, the movers' count and §810's times; nothing per module. (2) A mover entry
`<branch>.<source>.<module>` keeps that module's step outcomes per node (taken-in, built, checked, composed, wanted,
@@ -126,13 +126,13 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
there; the 64 KiB cap holds per entry. (3) The catalog half, when it moves, is a mover with an entry of its own
(`<branch>.<source>.mesh-catalog`, no node) and counts in the head's movers. (4) The month list (type held) stays
the way the ledger is listed; nothing changes it. One way per thing, P3; ADR 0595 §3.
- **H-A-386 (the keep's prefix is `_keep/`; the runtime's put answer carries the fill, 00:14)** Corrects H-A-380 (2):
- **H-A-386 (the keep's prefix is `_keep/`; the runtime's put answer carries the fill, 00:10)** Corrects H-A-380 (2):
the bus refuses a key-value key beginning with '.', so the keep lives under the reserved prefix `_keep/<key>`, the
underscore form the tool runner already uses for `_meta` (H-A-351); everything else of H-A-380 stands. DMC-14, which
H-A-350 answered and no build map carries: the tool runner's put answer (mesh/state.put) carries the entry's fill as
`{"revision": n, "fill": {"count", "bytes", "max_bytes"}}`, buscalls.Fill's form, which mesh-sdk's bundle-side prune
helper reads; built by the mesh-tools developer in H2 beside T1, tested in the runtime's state tests. P3, H-A-227.
- **H-A-387 (the artifact registry takes a publish whose reservation names no digest yet, 00:20)** Since H-A-373 the Go
- **H-A-387 (the artifact registry takes a publish whose reservation names no digest yet, 00:11)** Since H-A-373 the Go
build module publishes an archive with its reserved version during the build step, when the builder's reservation
still holds an empty digest for every artifact (the builder records digests only at the build's end); the
distribution module's holder (the seat oci-artifact-registry) accepts only an equal digest and says "for another
@@ -145,7 +145,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
digest is refused naming both. The pack is reproducible (the same archive bytes at 0.1.0, 0.1.1 and the refused
publish). Recovery: rerun the build steps once the distribution module runs on novox. A-490j, P-failure-loud,
fix-a-bug-met-twice (the same symptom met 19 Nov).
- **H-A-388 (the have carries the applied run; the declaration's version is its form, 00:26)** E4b, E7b. (1) The
- **H-A-388 (the have carries the applied run; the declaration's version is its form, 00:13)** E4b, E7b. (1) The
node-engine's have value gains `run` (the composition run's sequence the module was applied from) in
seats/node-engine/seat.json, generated, its form raised by one as H-A-352 (2) has it; the node-engine's developer
makes that K row in the mesh-contracts worktree (one commit citing this answer) since no other developer holds it
@@ -158,7 +158,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
and the two manifest words in mesh-sdk (its developer), the engine's word and reader (`mesh-host`), the composer's word
and writer and the plan's edge (mesh-delivery, with A1-A6). Until the plan reads the edge, the milestone plan names
the order by hand: node-engine before the assigner. design-it-as-it-should-be, P3, ADR 0614.
- **H-A-389 (a validate step judging a candidate that changes a seat's form, 00:26)** The mesh-catalog developer found
- **H-A-389 (a validate step judging a candidate that changes a seat's form, 00:13)** The mesh-catalog developer found
the trunk validator refuses H2's delivery seat definitions (form, max-age: fields its format does not know), so a
pipeline's validate step, asked of the running assigner, cannot judge a candidate that raises a seat's form. Today
validate is an optional step (main.175 shows it so), so the H2 group's pipeline is not failed by it; the gap stands:
@@ -166,17 +166,17 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
heads (ADR 0573 §2's rule for the check, carried to the validate step: the runner builds the validator tool from the
candidate like any artifact and asks it). Queued for H2b in mesh-delivery; the H2 group's validate verdicts are
read by hand once after its merge. design-it-as-it-should-be, ADR 0573 §2.
- **H-A-390 (§799's shared parts are the delivery SDK's developer's, 00:26)** BM1: the shared parts in
- **H-A-390 (§799's shared parts are the delivery SDK's developer's, 00:13)** BM1: the shared parts in
mesh-delivery-sdk's steprun (again-delays parsed into Puller.Delay, the third run's "fetch:"/"publish:" why,
HolderSilentOr's assigner call "with no seat call to learn why") are built by the mesh-delivery developer with its B
lines; the mesh-catalog developer builds the three build modules' settings and their use of the conformance kit
against the relayed head. One owner per file (P3).
- **H-A-391 (the gate's mover entries are found by an index on the record's key, 00:30)** §809, GT1. The ledger type
- **H-A-391 (the gate's mover entries are found by an index on the record's key, 00:14)** §809, GT1. The ledger type
`mover` declares an index on its record's key in the gate's manifest `requires` (records' `indexes`), and
gate_record's join is one `mesh/ledger.query` on that index with the key `<branch>.<source>.>`; the head entry stays
per record (its count of movers and nothing per module), and nothing reads the revision's graph again. A mover's
instance path is `mover/<token of branch.source.module>` beside `record/<token of branch.source>`. P-NATS-native, P3.
- **H-A-392 (what H-A-374 changes in the node-engine, 00:30)** (a) Issue 339's rule stands: a directory the mesh never
- **H-A-392 (what H-A-374 changes in the node-engine, 00:14)** (a) Issue 339's rule stands: a directory the mesh never
made, found with another owner or mode, is used as found and said so; H-A-374 holds for a directory the engine's
record says the mesh made. (b) Two things, both read-only on the judgement: the verb composition with diff reads a
record-held directory's owner and mode on disk and names one that differs as drift; and the engine converges the
@@ -184,7 +184,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
line per directory set right, so a drift lasts at most until the engine's next start. An unchanged composition is
still not applied (idempotence keeps). Test: a record-held directory with another mode is set right at the engine's
start; one the mesh never made is left and said. P-mesh-owns-the-truth, issue 339.
- **H-A-393 (a version the store already holds at another digest is refused before the reservation is asked, 00:44)**
- **H-A-393 (a version the store already holds at another digest is refused before the reservation is asked, 00:16)**
Addendum to H-A-387. While the reserved digest is still empty, a second node's publish of the same version with
another digest would pass Recorded, and the OCI store's Put would overwrite the tag the first publish set; the gitea
forge refuses this itself, the artifact registry's store does not. A-490j holds for every holder: "a second publish of
@@ -192,7 +192,7 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
Publish refuses, in its Held branch before Recorded is asked, a publish whose version the store already holds at
another digest, naming both digests; the same digest is taken as today. Test: a table row (version held at digest bb,
publish of aa, refused naming both). Same fix branch. P-failure-loud, A-490j.
- **H-A-394 (a module's class, where the gate reads it, and when a delivery's time starts, 00:52)** §810, GT2. (1)
- **H-A-394 (a module's class, where the gate reads it, and when a delivery's time starts, 00:20)** §810, GT2. (1)
mesh-sdk's catalog.Manifest gains the top-level field `class` (`core` or `leaf`; S12's row), the indexer carries it
in its catalog entry (an I line), and the catalog's manifests declare it in M1 by one rule: a module that claims a
seat is `core` (its delivery carries a contract of the mesh), a module that claims none is a `leaf`; a module with no
@@ -202,29 +202,29 @@ The lead's one-line answers to the questions H2's develop and review raise (impl
`delivery-time` runs from the merge-called event's own time, which the gate writes on the head entry as
`merge-called` when it opens the record on that event; `ended` is the last `running` of its movers. ADR 0282 §1,
P-NATS-native, a rule states how it is checked.
- **H-A-388 (addendum, 00:52)** The baseline manifest reads do not gain `declaration-reads` and `declaration-writes`:
- **H-A-388 (addendum, 00:20)** The baseline manifest reads do not gain `declaration-reads` and `declaration-writes`:
running engines do not read them, so an engine manifest stating `declaration-reads` is held for a yes once, the same
hold H-A-383 names, at the same delivery; both are said to the operator together. A new engine still reads a
composer's Version 1 and refuses only a Version above its own.
- **H-A-395 (the ask bound is re-armed by the holder's progress and holds for every seat, 00:58)** §778, R2. The
- **H-A-395 (the ask bound is re-armed by the holder's progress and holds for every seat, 00:21)** §778, R2. The
bound key `ask.<seat>.<ask>` is armed at ask-taken with ask-unanswered-bound less the time since taken-at, re-armed
from now at each step-progress the holder says for that ask, and ends at the step's end; it holds for the three
node-build seats as for every other seat (one rule, P3), so a Go build or test level running past 10 minutes lives
as long as its holder says progress within the bound, and a holder silent for the whole bound ends the step
could-not-run naming the silence (P-failure-loud: a holder that works and says nothing is the fault, and the
delivery SDK's step run says progress at each phase). H-A-238 (3)'s unbounded asks end. ADR 0668 §3.
- **H-A-394 (addendum, 01:14)** `class` does not join the baseline manifest reads: the running engine does not read it
- **H-A-394 (addendum, 00:28)** `class` does not join the baseline manifest reads: the running engine does not read it
(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
- **H-A-396 (gate_times names each class's newest delivery; the probe judges that, 00:31)** §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.
- **H-A-397 (a start puts again only the asks no holder took, 01:40)** §777, R2. The start's Resume puts every open
- **H-A-397 (a start puts again only the asks no holder took, 00:32)** §777, R2. The start's Resume puts every open
step's ask again under its own id (G §88); §777 puts an ask again only on a transport fault. Resume keeps only the
steps with no taken-at: a taken ask's put surely landed and its holder takes an id once (ADR 0668 §2), so putting it
again under a new id would ask the work twice; an untaken one may never have been put, and its bound key, armed at