Design 47 H2: hq a watched source, the destroy bend stands, asks placed are journal lines

The lead's H-A-332 to H-A-334 settle the two questions the first commit left
open and amend the journal lines, so the part leaves its builders no choice.
This commit is contained in:
2026-11-21 21:57:22 +01:00
parent 4b71fcbda9
commit f845e9f900
2 changed files with 39 additions and 13 deletions
@@ -425,7 +425,7 @@ own pipeline), in this order, the next starting when the previous one's delivery
|---|---|---|---|
| H0 | the design says the one model whole (section 4) | hq, the knowledge base | the four reviewers by architectural domain approve the batch; the operator's four answers are in |
| H1 | the one chain works with no hand act (section 5) | `mesh-delivery`, `mesh-catalog`, `mesh-host`, `mesh-tools`, `mesh-sdk`, `mesh-contracts` | the two proofs of step 7 |
| H2 | the work H1's live run owes, as the lines of its own part, [H2-the-delivery-systems-owed-work](H2-the-delivery-systems-owed-work.md) (design 47 H2 §775 to §816): every ask a kept call through a part away, the work queues and journal lines of the asks, the fingerprint over a module's own build source, the stores capped and read in parts, the gate's ledger per module and its delivery times | mesh-delivery, mesh-catalog, `mesh-host`, `mesh-tools`, `mesh-sdk` | H2 §815 and §816: a change to a delivery part, and a package with its importer in two repositories, each running everywhere within ten minutes of its merge call with no hand act |
| H2 | the work H1's live run owes, as the lines of its own part, [H2-the-delivery-systems-owed-work](H2-the-delivery-systems-owed-work.md) (design 47 H2 §775 to §817): every ask a kept call through a part away, the work queues and journal lines of the asks, the fingerprint over a module's own build source, the stores capped and read in parts, the gate's ledger per module and its delivery times, hq a watched source | mesh-delivery, mesh-catalog, `mesh-host`, `mesh-tools`, `mesh-sdk` | H2 §816 and §817: a change to a delivery part, and a package with its importer in two repositories, each running everywhere within ten minutes of its merge call with no hand act |
| H3 | the gate and the forge module carry only the one model; groups by the operator's answer; the forge module without its merge-check machinery | mesh-catalog, mesh-delivery | a group of two repositories delivers as one; every delivery record ends |
| H4 | every delivery part wakes on its inputs alone and is steered by its tools (sections 3.6, 7): the shared wake-up shape (mesh-config's full pass per event and its reads through module tools, the indexer's re-read after every verdict, the node-engine's retry clocks, the build modules' idle pull), the view and the watchman without reads of another part's state, the SDK's generic state tools with the fill against a cap, the missing tools per module, rates on the bus | `mesh-sdk`, `mesh-delivery`, `mesh-catalog`, `mesh-host` | the bus's slow consumers and behind counts at 0 for an hour; every module's tools pass the principle-4 table |
| H4b | the grants part says what it holds as events and reads nothing of another part's bus state (ADR 0596) | `mesh-delivery` | the grants part's own `filling` and `room` and no bucket watch in its code |
@@ -15,6 +15,7 @@ decisions:
- "ADR 0573"
- "ADR 0571"
- "ADR 0548"
- "ADR 0527"
- "ADR 0525"
- "ADR 0259"
- "ADR 0499"
@@ -35,7 +36,7 @@ edges), not this part's. The records each line follows are named in it; a choice
answer made is this part's own, given with its reason.
H2 is one release of playbook 07: prepared by `mesh-preparer`, built, reviewed once, checked once, and delivered by
its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§815, §816) close it.
its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§816, §817) close it.
### The asks between the delivery parts
@@ -58,14 +59,14 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
(mesh-sdk): a call met by no responders twice and then answered returns the answer and logs one line; a call past its
bound returns every try; a refusal returns at once. Whole (runner): a composition ask whose holder is away for 40 s
passes its step with no hand act.
- §776 **A holder says `away` when a part it depends on is away.** (ADR 0664 §1; ADR 0668 §1; H-A-300 (2), H-A-301;
rows 177, 178) mesh-sdk's seat error answer gains the kind `away`, with `part` (what did not answer) and `words`.
- §776 **A holder says `away` when a part it depends on is away.** (ADR 0664 §1; ADR 0668 §1, insight proposed
2026-11-21; H-A-300 (2), H-A-301, H-A-334 (3); rows 177, 178) mesh-sdk's seat error answer gains the kind `away`, with `part` (what did not answer) and `words`.
The forge module, holder of the seat `git`, answers `away` when the forge answers 401, 502 or 503 or a connection
fault and the forge's own unauthenticated version read fails or names its store unavailable; it answers `refused`,
"the forge refuses the mesh's admin account", only when that read succeeds and a freshly minted token (§808) is
refused too, and it never words a refusal as an account to create. Every caller reads `away` as a transport fault
(§775, §796). This adds one class, a holder's own word that what it depends on is away, to the classes ADR 0664 §1
and ADR 0668 §1 list. Built in H2 in mesh-sdk (the error kinds) and the forge module (mesh-catalog). How it is
and ADR 0668 §1 list, as the insight on ADR 0668 proposed 2026-11-21 says. Built in H2 in mesh-sdk (the error kinds) and the forge module (mesh-catalog). How it is
checked: unit (forge module): a 401 with the version read failing answers `away`; a 401 with the read passing and the
fresh token refused answers `refused`. Whole (forge module): with the store stopped for 30 s, a merge call in that
window answers `away` and lands when called again.
@@ -129,9 +130,12 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
### The pipeline runner (seat `mesh-pipeline-runner`; mesh-delivery-pipeline)
- §784 **A step's end is a journal line.** (H-A-320 (1); row 189) The runner writes one line per step end, "step
ended `<pipeline>` `<mover>` `<step>` `<outcome>` in `<duration>`", and nothing else per step. Built in H2. How it is
checked: unit: a step end writes exactly that line.
- §784 **An ask placed and a step's end are journal lines.** (H-A-320 (1), H-A-333; row 189) The runner writes one
line when it places an ask, "`<pipeline>` `<mover>` `<step>` asked on `<seat>`", and one when a step ends, "step
ended `<pipeline>` `<mover>` `<step>` `<outcome>` in `<duration>`", the latter in the one place that says
`step-ended`, so every end writes it: the unanswered bound's, the end at placing, a supersede, a re-pin, the
approval's end, the start pass and the verbs that end a step. Nothing else is written per step. Built in H2. How it
is checked: unit: each way a step ends writes exactly that line once.
- §785 **`pipeline-ended` carries the pipeline's phases.** (ADR 0282 §1, §6; row 111) `pipeline-ended` gains
`phases`: `taken` (the take-in), `placed`, `ended`, and for each step kind (build, lint, unit, integration, validate,
composition) the earliest start and the latest end across its movers, RFC 3339. Each mover's own step times stay in
@@ -176,7 +180,8 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
### The builder (seat `mesh-builds`; mesh-delivery-builder)
- §792 **An answered ask is a journal line.** (H-A-320 (1); row 189) The builder writes one line per build ask it
answers, "answered `<ask>` `<module>` `<fingerprint>` `<outcome>`"; the holder of `mesh-wants` one per validate or
answers, "answered `<ask>` `<pipeline>` `<movers>` `<step>` `<outcome>`", in the one place an ask is answered (its
build step's finish), beside the line per entry saying an existing build or one built now (H-A-333); the holder of `mesh-wants` one per validate or
compose ask answered. Built in H2 (builder, assigner). How it is checked: unit.
- §793 **The publish queue is a work-queue stream.** (H-A-290, H-A-291; row 158) The builder's publish items travel on
its work queue `publishes` (the work-queue template, ADR 0595 §2), subject `publish.<holder>.<class>.<module>.<version>`
@@ -362,6 +367,10 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
work from its seat's `current` (§801), not from the node-engine's held phase. Checked: unit (view).
10. *The teller's ask-again for want of room goes* (ADR 0682 §14; H-A-295): with A-424, the teller's ask-again for an
ask refused for room and its test are removed. Checked: the teller's suite holds no such test.
11. *The destroy-level answer's channel waits for its research* (ADR 0259; H-A-237, H-A-334 (2); row 114): the
bus module's keeper asks its drop and rebuild warrants at the approve level, as H-A-237 bends it, until a research
effort designs the channel that carries the destroy proof; H2 builds no such channel, and the bend's line in the
keeper's code names that research as its end. Checked: unit (keeper): a drop asks at the approve level.
### The catalog's checks
@@ -376,6 +385,23 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
by hand against `seat-list` gives the live validate's verdicts for the builder's and the runner's manifests; unit
(validator): a problem the before case holds is not counted.
### hq, a watched source with no module
- §815 **A repository with no module registers as a source alone, and merges like any other.** (ADR 0527; ADR 0682
§1, §3; H-A-332, H-A-334 (1); the operator, 2026-11-21 21:48: no merge is put to them; rows 176, 177) A registration
of the seat `mesh-catalog` takes a source-only form: `repository`, its watched `branch` and `check`, the repository's
own check command (for hq, its Go checks, ADR 0527), and names no module. The indexer keeps it with the
registrations, takes a move of that branch in as a take-in with no movers, and refuses a source-only registration
whose repository holds a manifest. The forge bridge says `head-moved` for it and the gate watches it as any watched
branch (`head-untaken`, ADR 0682 §3); the checker runs `check` on each pull request's head and writes it as the
status `mesh/check`; `merge-pull` merges its pull requests once that status passes, as for a module's, and the gate
opens a delivery record that ends `nothing to deliver`. Fate: hq's pull requests merged by the operator at the
forge end at H2's delivery; hq is registered so once through the seat `mesh-catalog`'s verb `register`, with the operator's channel saying it
as a registration change. Built in H2 in the indexer (the registration's source-only form and the seat's
definition), the gate and the checker. How it is checked: whole (indexer and gate): a source-only registration's
merge call lands, raises no `head-untaken` and ends its record `nothing to deliver`; whole (checker): an hq pull
request whose checks fail shows `mesh/check` failed and `merge-pull` refuses it.
### The tools this part adds
| tool | module | reads or steers | line |
@@ -396,7 +422,7 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
### How H2 is proven
- §815 **Proof 1: a one-line change to a delivery part runs everywhere within ten minutes, by its pipeline alone.**
- §816 **Proof 1: a one-line change to a delivery part runs everywhere within ten minutes, by its pipeline alone.**
(ADR 0282 §1; ADR 0682 §1, §6, §8; plan section 5, step 7) A one-line change (a comment) in one module of the
delivery system with lint, unit and composition steps, merged through one merge call (`merge-pull`), runs at its new
version on every present placing machine, reported healthy, within ten minutes of its `merge-called` (a core
@@ -404,12 +430,12 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
phases (§785). No hand act touches the delivery system during it: no hand pack, no held put, no `runner_cancel`,
`runner_end_again`, rerun, `builder_build_again` or `builder_publish_again`, and no start, stop or restart through the
seat `node-service-manager`; the only restart is the moved module's own, by its node-engine.
- §816 **Proof 2: a package and its importer in two repositories, one merge call, within ten minutes.** (ADR 0282 §1;
- §817 **Proof 2: a package and its importer in two repositories, one merge call, within ten minutes.** (ADR 0282 §1;
ADR 0682 §1, §2, §4; ADR 0573 §2) One merge call names two pull requests: a one-line change to a package of the
delivery repository whose importers are at most three, one of them the gate in the catalog repository (read with
the indexer's `indexer_package_users`), and a one-line change to the gate. The gate names one source revision for
both, one pipeline publishes the package and builds the gate against it, and every mover runs at its new version on
every present placing machine within ten minutes of `merge-called`, read and bound as §815, with no hand act and no
restart as §815 says. How it is checked for both: the lead reads each with the tools named and quotes the times in
every present placing machine within ten minutes of `merge-called`, read and bound as §816, with no hand act and no
restart as §816 says. How it is checked for both: the lead reads each with the tools named and quotes the times in
the milestone's report; a proof over its ten minutes or with a hand act is not shown, and its cause is fixed in its
repository and delivered before it is run again.