From acf34312079eeee49d75654a7bbce59f270c2155 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 21 Nov 2026 22:05:35 +0100 Subject: [PATCH] Design 47 H: H-A-338 to H-A-340, H2's part after three reviews by domain --- .../01-to-be/47-milestones/H-lead-answers.md | 48 +++++++++++++++++++ 1 file changed, 48 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 977a8024..1b17dc36 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 @@ -2042,3 +2042,51 @@ Where two preparers disagreed, the chosen one is named. refused until no module is held (refusing more, never less); words that name their owner per entry (the owned paths) take the composed entries of modules not held plus the running entries whose owner names a held module. Both in the resolution, given the held set and each runtime process's running words. P3, ADR 0310 §5. +- **H-A-338 (H2's part after the security and upgrade review, 22:05)** (1) The forge token is a secret: kept where the + module keeps secrets (the vault's own, never plain in a state), the read tool masks it, each new mint deletes the + old token at the forge. (2) A source-only registration's check names a build seat and a step kind (for hq + node-build-go, unit at the repository root), run in that seat's sandbox, never a free command; merge-pull judges it + by the registration's policy, the same as a module's (ADR 0527 §1). (3) The install kind names its source (the npm + registry seat), an integrity-checked install (npm ci), no install scripts, the archive kept under the lock's digest. + (4) ask-taken and version-reserved are declared in their seats' definitions, so only the holder publishes them. + (5) builder_publish_drop, builder_publish_first (with a why) and bridge_owed_again are written in the hand-act log; + an act performed again checks its preconditions again. (6) The ids a holder took live in its own state taken, key + ., with the ask's bound as TTL. (7) A rebuilt asks stream carries no messages and is rebuilt before the + new builder and assigner start. (8) form is left out while it is 1 and an absent form reads as 1; the edge "the + tolerant node-engine before the assigner writes run" is named. (9) Every fingerprint changes once at H2's + delivery; every module becomes a mover of that one pipeline (a build with the same content is reused, the engines + restart nothing whose composition is unchanged); the indexer and the builder take the new fingerprint function in + one release. (10) Ledgers and the hand-act log are never pruned; the foundation's old sections are exempt from the + cap refusal; a delivery module is one whose manifest claims a delivery seat (the validator reads that). The main + file's size and the H file's size are their own reshaping run (H-A-334 (4)). P-security, P3. +- **H-A-339 (H2's part after the seams and tools review, 22:05)** (1) A foundation part declares each entry in its old + section with its cap there (H-A-229, ADR 0619, ADR 0666 §4); so for the validator's rule. (2) An owner prunes when + it hears the bus module's full condition for its own entry, down to prune-target; no periodic read. (3) hq's merge + check is a pipeline step on the seat node-build-go run by the runner, judged by merge-pull from the runner's step + events as for any module (ADR 0666 §11; the checker is gone). (4) Every holder of a kept call (the node-engine's + compose-candidate, the forge module's git verbs, the registry) keeps the ids it took as H-A-338 (6) says, each named + in its part. (5) §776 rests on the insights on ADR 0668 §1 and ADR 0664 §1 (proposed), accepted before the prepare. + (6) The install kind is a step the runner asks of the Node build seat; the step's end carries the archive object's + name (ADR 0666 §16). (7) Every new store names its form, cap, per-key TTL where it has one, and deleter (unfinished, + outputs, publishes, token, dry-runs); a put refused by a full queue is said and asked again with the kept-call + pacing. (8) The table of tools gains: what waits on the mesh-wants and mesh-builds queues and a drop of one ask; + place-now for an unfinished mover; prune-now and keep-now; a read of the token lease and of dry-runs; whether the + registrations view has been read; the before case's problems validate does not count. Notes taken: a changed shared + form rebuilds every module (said once per such line); the output verb's node from the step key; the unbuildable + list worked out again at every start. P7, P-NATS-native, tools-are-how-a-module-is-spoken-to. +- **H-A-340 (H2's part after the running and testing review, 22:05)** (1) The work queue names its consumer settings + (ack wait, in-progress interval, max ack pending, max deliveries, duplicates window, ADR 0436 §6); a holder pulls + every ask at once and says ask-taken at the pull, so the bound counts from the pull, never from queue length + (H-A-241). (2) The holder's compose bound is the setting compose-ask-bound (10 s). (3) Every store names its cap, + the gate's ledger included; the prune trigger is the full condition (H-A-339 (2)). (4) Past mint-lease the waiter + creates the lease itself; the token and the lease have per-key TTLs. (5) H2's own delivery is one pipeline of every + module, builds with the same content reused and unchanged compositions not restarted, before the proofs run; its + size and time are named. (6) A setup-starved NOT RUN ends the run again by §799's delays; a third ends the step + could-not-run. (7) §794's cost is a unit test counting one read and one write per event, not a wall clock. (8) Each + module ends H2 with fewer tests than it starts with, counts named per module. (9) Every line names its case, + including take-in-waiting, record-too-large and the third run's failure. (10) The proofs are read from the gate's + record (class core, delivery-time under ten minutes, no over-budget) and an empty hand-act log for every delivery + part from merge-called to the last running, with no other pipeline holding the slot. Notes taken: jitter in the + pacing; one journal line per seat; a key read twice between pages said; the head entry's count; the publish items' + move with a message id; tags read once per take-in; the verb a build module calls to learn away. P3, + P-failure-loud, test-budget.