|
|
|
@@ -27,8 +27,9 @@ decisions:
|
|
|
|
|
# 47, milestone H2: the delivery system's owed work, as design lines
|
|
|
|
|
|
|
|
|
|
Milestone H2's part of [design 47](../47-delivery-from-commit-to-delivered.md), read whole by its builders with its
|
|
|
|
|
second file, [H2-stores-and-tools](H2-stores-and-tools.md) (the forge bridge, the gate and the forge module, the parts
|
|
|
|
|
beyond the chain, the new stores and the tools). Milestone H1 (the clean state and the one chain,
|
|
|
|
|
second file, [H2-stores-and-tools](H2-stores-and-tools.md) (the forge bridge, the gate and the forge module, the vault's
|
|
|
|
|
seat, the parts beyond the chain, the new stores and the tools); the prepare's questions and where design met code are
|
|
|
|
|
in [H2-prepare-questions](H2-prepare-questions.md), with the build maps in [H2-build-maps](H2-build-maps/). Milestone H1 (the clean state and the one chain,
|
|
|
|
|
[H-deliver-the-delivery-system](H-deliver-the-delivery-system.md)) ended at 19:31 on 2026-11-21 with both its proofs
|
|
|
|
|
shown; what its live run met and did not build is owed here: every item the lead's answers H-A-227 to H-A-331
|
|
|
|
|
([H-lead-answers](H-lead-answers.md)) name as owed to H2, every *Owed* of rows 103 to 199 of the plan's section 10,
|
|
|
|
@@ -70,35 +71,42 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
same ask id twice acts 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 0668 §1 and ADR 0664 §1 (insights of
|
|
|
|
|
2026-11-21, accepted); H-A-300 (2), H-A-301, H-A-334 (3), H-A-339 (5); 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`,
|
|
|
|
|
2026-11-21, accepted); H-A-300 (2), H-A-301, H-A-334 (3), H-A-339 (5); rows 177, 178) Each seat the delivery parts call
|
|
|
|
|
gains the error kind `away` among its own error kinds, the seat `git` first, with `part` (what did not answer) and
|
|
|
|
|
`words`; mesh-sdk's kept call, in Go and in its TypeScript helpers alike, reads `away` from the answer's `error-kind`
|
|
|
|
|
as a transport fault, and the conformance kit of each seat tests it (H-A-349 DQ-15, H-A-350 DMC-2). 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). 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; the line rests on those two
|
|
|
|
|
insights, accepted on 2026-11-21. Built in H2 in mesh-sdk (the error kinds) and the forge module
|
|
|
|
|
insights, accepted on 2026-11-21. Built in H2 in the seats' definitions, mesh-sdk (Go and TypeScript) 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.
|
|
|
|
|
- §777 **The seats `mesh-builds` and `mesh-wants` take their asks from a work queue and say `ask-taken`.** (ADR 0525
|
|
|
|
|
§1, §2, §6; ADR 0436 §6; ADR 0664 §2; H-A-241, H-A-243 (1), (2), H-A-320 (2), H-A-338 (4), (7), H-A-339 (7), (8),
|
|
|
|
|
H-A-340 (1), H-A-341 (4); rows 118, 130, 189) Each seat's definition (the delivery repository's contracts module)
|
|
|
|
|
declares its accepted kinds as work-queue streams the broker derives, as ADR 0525 §2 has it for the build seats:
|
|
|
|
|
`build` on `mesh-builds`, `validate` and `compose` on `mesh-wants`; each `max-age` 1 day and `max-msgs` 10,000, one
|
|
|
|
|
shared worker consumer its holder pulls, with ack wait 60 s, in-progress every 20 s, max ack pending 1,000, max
|
|
|
|
|
deliveries 5 (above ADR 0664 §2's three) and a duplicates window of 2 minutes (ADR 0436 §6). The holder pulls every
|
|
|
|
|
H-A-340 (1), H-A-341 (4), H-A-349 DQ-1, DQ-2, DQ-4, H-A-350 DMC-1; rows 118, 130, 189) Each seat keeps its one
|
|
|
|
|
accepted kind `step` (the step the ask names tells build, validate and compose apart), declared in its definition
|
|
|
|
|
(the delivery repository's contracts module) as a work-queue stream the broker derives, as ADR 0525 §2 has it for
|
|
|
|
|
the build seats. The definition's `accepts` gains the stream's and consumer's settings: `max-age` 1 day, `max-msgs`
|
|
|
|
|
10,000, one shared worker consumer its holder pulls, ack wait 60 s, in-progress every 20 s, max ack pending 1,000,
|
|
|
|
|
max deliveries 5 (above ADR 0664 §2's three) and a duplicates window of 2 minutes (ADR 0436 §6); they are derived
|
|
|
|
|
once, by mesh-sdk's `buscompose`, which the grants part takes, and the grants part's own copy of that derivation
|
|
|
|
|
(its `buscompose` with its own values) goes. The holder pulls every
|
|
|
|
|
ask waiting at once, never one at a time, acknowledges an ask when it says the ask's end, sends in-progress while it
|
|
|
|
|
works (ADR 0525 §6), and says `ask-taken` on the seat's family at the pull, subject `<seat>.ask-taken.<ask>`,
|
|
|
|
|
carrying `ask`, `node` and `at`; the definition declares `ask-taken`, so only the seat's holder publishes it. The
|
|
|
|
|
runner consumes both seats' `ask-taken`. An ask put while its holder is down waits on the stream. The runner puts an
|
|
|
|
|
ask again only when its put met a transport fault; a put refused by a full stream is said in the journal and asked
|
|
|
|
|
ask again only when its put met a transport fault, under the same id; its second put under `AgainID` and the bound
|
|
|
|
|
keys `ask2.<seat>.<ask>` go, for every seat; a put refused by a full stream is said in the journal and asked
|
|
|
|
|
again at the kept-call pace (§775). `builder_asks` and `assigner_asks` read what waits and what is taken on their
|
|
|
|
|
seat's stream; `builder_ask_drop` and `assigner_ask_drop` (ask, why) end one ask, written in the hand-act log. Fate:
|
|
|
|
|
the holders' plain subscriptions go; the runner's putting again of every open ask on the holder's `running`
|
|
|
|
|
(H-A-243 (1)) goes; `ask-silent-bound` and its bound key (H-A-243 (2)) go; the mesh-builds stream that no consumer
|
|
|
|
|
took (1,524 asks on 2026-11-21) is rebuilt empty through the bus module's tool `nats_recreate`, on the operator's
|
|
|
|
|
warrant (ADR 0595 §5), before the new builder and the new assigner start, so the rebuilt stream carries no message.
|
|
|
|
|
(H-A-243 (1)) goes; `ask-silent-bound` and its bound key (H-A-243 (2)) go; the mesh-builds and mesh-wants streams, which no consumer
|
|
|
|
|
took (1,558 and 1,598 asks on 2026-11-21), are rebuilt empty through the bus module's tool `nats_recreate`, on one
|
|
|
|
|
warrant of the operator (ADR 0595 §5), before the new builder and the new assigner start, so neither carries a
|
|
|
|
|
message.
|
|
|
|
|
Built in H2 in mesh-delivery (the contracts module, the builder, the assigner, the runner). How it is checked: whole
|
|
|
|
|
(builder): a build ask put while the builder is stopped is taken and ended after its start; whole (assigner): the
|
|
|
|
|
same for a validate ask; after a pipeline's end the streams' consumers hold 0 pending; unit (runner): a put refused
|
|
|
|
@@ -108,7 +116,8 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
seat's `ask-taken`), RFC 3339. The bound key `ask.<seat>.<ask>` is armed at `ask-taken` with the bound less the time
|
|
|
|
|
since `taken-at`, and again at every start for every open ask, so a restart never grants a fresh bound; an ask whose
|
|
|
|
|
time is spent at a start ends could-not-run at once. A step ended by its bound drops its ask through the seat's
|
|
|
|
|
`drop` (as ADR 0664 §4 has it for the build seats), so no holder works on it after. An ask not taken counts no bound:
|
|
|
|
|
`drop`, an act both seats gain (H-A-350 DMC-15), whose holder ends the ask as the build seats' `drop` does (ADR 0664
|
|
|
|
|
§4), so no holder works on it after. An ask not yet taken:
|
|
|
|
|
the runner's health names a step whose ask is untaken past `stalled-bound` (§790), and an ask still untaken
|
|
|
|
|
`ask-unanswered-bound` after its `asked-at` ends the step could-not-run "its ask was not taken: <seat>'s holder takes
|
|
|
|
|
none", so no slot is held without end (H-A-344 (6)). Built in H2 in the runner. How it is checked: unit (runner): an
|
|
|
|
@@ -133,26 +142,31 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
generated decoders for reading another part's value, event or answer keep unknown fields, never refuse them, and
|
|
|
|
|
return `form`; a tool whose record's `form` differs from the one it was built with says "form N, this reader knows M"
|
|
|
|
|
in its answer. A writer still validates its own value strictly before it writes. Fate: the runner's dropping of
|
|
|
|
|
`kept-revisions` before the seat's decode (row 190) goes. Built in H2 in mesh-sdk (the seat generator and its
|
|
|
|
|
decoders) and every seat definition (a regeneration). How it is checked: unit (mesh-sdk): a value, an event and an
|
|
|
|
|
`kept-revisions` before the seat's decode (row 190) goes. Built in H2 in the seat generator, mesh-delivery's
|
|
|
|
|
`modules/mesh-delivery-sdk/seatgen` (H-A-350 DMC-4), and every seat definition of mesh-delivery and mesh-contracts
|
|
|
|
|
(a regeneration). How it is checked: unit (mesh-sdk): a value, an event and an
|
|
|
|
|
answer with an unknown field decode and return their form; an absent `form` reads as 1; the seat generator's check
|
|
|
|
|
fails a definition whose fields changed with `form` unchanged.
|
|
|
|
|
- §781 **A tools program reads its module's settings.** (H-A-322, H-A-330; rows 190, 199) The node-engine composes a
|
|
|
|
|
module's settings into the module's slice of the tool runner's `MESH_TOOL_ENV` in the same files it composes for the
|
|
|
|
|
module's process, and mesh-sdk's settings reader reads them in a tools bundle as in a process. A bound one module
|
|
|
|
|
keeps on another's verb is that verb's `timeout` in its seat definition (built in H1), read by the caller from the
|
|
|
|
|
seat list: the packet filter's holder asks the node-engine seat's `converged` within that verb's `timeout`, and its
|
|
|
|
|
named 10 s goes. Built in H2 in the node-engine (`mesh-host`), mesh-sdk and the packet filter module. How it is
|
|
|
|
|
checked: unit (mesh-sdk): a tools bundle reads a setting the manifest sets; whole (runner): §790.
|
|
|
|
|
- §782 **The bus wrappers are safe for concurrent use.** (row 137, met twice) mesh-sdk's wrappers around one bus
|
|
|
|
|
handle guard each call the client does not allow at once with a lock inside the wrapper, so no module needs a
|
|
|
|
|
- §781 **A tools program reads its module's settings.** (H-A-322, H-A-330, H-A-350 DMC-12, DMC-13; rows 190, 199)
|
|
|
|
|
The node-engine composes a module's settings into the module's slice of the tool runner's `MESH_TOOL_ENV` in the
|
|
|
|
|
same files it composes for the module's process. mesh-sdk gains one settings reader, which takes a setting by its key
|
|
|
|
|
from the words the node-engine composes, in a process and in a bundle alike; the runner's own readers of its
|
|
|
|
|
`${config:<key>}` files move to it. A bound one module keeps on another's verb is that verb's `timeout` in its seat
|
|
|
|
|
definition, read by the caller from the seat list: the node-engine seat's `converged` with its `timeout` and the
|
|
|
|
|
packet filter's `allow` are the packet filter group's (ADR 0683), on main since 2026-11-21; H2 builds none of them
|
|
|
|
|
and reads them from main, and the holder's named 10 s goes once it reads `converged`'s `timeout`. Built in H2 in the
|
|
|
|
|
node-engine (`mesh-host`), mesh-sdk, the runner and the packet filter module. How it is checked: unit (mesh-sdk): a
|
|
|
|
|
process and a tools bundle read the same setting the manifest sets; whole (runner): §790.
|
|
|
|
|
- §782 **The bus wrappers are safe for concurrent use.** (row 137, met twice; H-A-349 DQ-3) mesh-sdk's wrappers
|
|
|
|
|
around one bus handle, `process.Conn` (its state and stream calls), `stdio.BusState` (through the runtime) and the
|
|
|
|
|
`views` reader, guard each call the client does not allow at once with a lock inside the wrapper, so no module needs a
|
|
|
|
|
handle per goroutine (one place, principle 7). Built in H2 in mesh-sdk. How it is checked: unit under the race
|
|
|
|
|
detector: concurrent gets, puts and watches through one wrapper.
|
|
|
|
|
- §783 **A module's findings history drops its oldest.** (ADR 0595 §2, §3; H-A-227, H-A-344 (3), (5); row 104) The
|
|
|
|
|
stream a module's findings writer appends to (three stood full on 2026-11-21: the runner's, the builder's, the
|
|
|
|
|
node-engine's) is asked for by the events template, which drops the oldest when full, with `max-bytes` 8 MiB and
|
|
|
|
|
`findings-max-age` (default 7 days); a foundation part (ADR 0619 §1, ADR 0666 §4) declares it in its old section
|
|
|
|
|
with the same cap and life (H-A-229). Its fill is read through the seat `mesh-broker`'s `show`. The findings state itself is unchanged. Built in H2 in mesh-sdk (the
|
|
|
|
|
`findings-max-age` (default 7 days); a foundation part (ADR 0619 §1, ADR 0666 §4; the list is
|
|
|
|
|
§814's) declares it in its old section with the same cap and life (H-A-229). Its fill is read through the seat `mesh-broker`'s `show`. The findings state itself is unchanged. Built in H2 in mesh-sdk (the
|
|
|
|
|
writer's requires) and every delivery module's manifest. How it is checked: whole (runner): 10,000 findings written
|
|
|
|
|
past the cap refuse none.
|
|
|
|
|
|
|
|
|
@@ -192,27 +206,30 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
yet read" once and places no step whose registration it has not read. `runner_health` answers
|
|
|
|
|
`registrations-read` (true or false, and since when). Built in H2. How it is checked: unit: a start with the view
|
|
|
|
|
unread raises no `registration-missing`, answers `registrations-read` false, and places the movers once it is read.
|
|
|
|
|
- §789 **A pipeline is read in parts.** (H-A-299 (3); rows 136, 142) The verb `show` and the tool `runner_show` take
|
|
|
|
|
- §789 **A pipeline is read in parts.** (H-A-299 (3), H-A-350 DMC-8; rows 136, 142) The seat verb `show` and the runner's new tool `runner_show` take
|
|
|
|
|
`mover`, `step` and `state` filters applied while reading, and answer at most 768 KB with `capped`, `total` and the
|
|
|
|
|
cursor of §779; `runner_movers` (a pipeline's key) answers each mover with one word per step (`passed`, `failed`,
|
|
|
|
|
`running`, `waiting`, `not-run`). Built in H2. How it is checked: unit: one mover's steps of a record of 129 movers
|
|
|
|
|
`running`, `waiting`, `not-run`), a new tool too; neither tool exists today. Built in H2. How it is checked: unit: one mover's steps of a record of 129 movers
|
|
|
|
|
answer under 64 KB; `runner_movers` of 1,000 movers answers under 768 KB.
|
|
|
|
|
- §790 **The stalled bound is a setting.** (H-A-311 (3), H-A-313, H-A-322; row 190) The five minutes after which the
|
|
|
|
|
runner's health names a running pipeline with nothing open, or a step whose ask is untaken (§778), become the
|
|
|
|
|
runner's setting `stalled-bound` (default 5 minutes, the rule nothing-moved-in-five-minutes), read by its process
|
|
|
|
|
and its tools program (§781). Built in H2. How it is checked: whole: with `stalled-bound` at one minute, the health
|
|
|
|
|
names such a pipeline after one minute, and no longer names it once a step is placed in it.
|
|
|
|
|
- §791 **A step's output is read where it is kept.** (H-A-294, H-A-341 (7); rows 144, 165, 168) A build module keeps a
|
|
|
|
|
- §791 **A step's output is read where it is kept.** (H-A-294, H-A-341 (7), H-A-350 DMC-16; rows 144, 165, 168) A build module keeps a
|
|
|
|
|
run's output in its `outputs` objects (§820), named on its step key `<node>.<ask id>` (ADR 0525 §6); the build seats
|
|
|
|
|
`node-build-go`, `node-build-node` and `node-build-image` gain the read verb `output` (input `ask`; answer the
|
|
|
|
|
output's last 64 KB, its size, and the failing tests' names with their words, or "no longer kept" past the objects'
|
|
|
|
|
max-age), and the runner's tool `runner_step_output` (pipeline, mover, step) asks it of the holder on the node the
|
|
|
|
|
step key names. Fate: the runner's objects `step-outputs`, which hold 0 bytes, go, dropped through the bus module.
|
|
|
|
|
step key names. Fate: the build-step part's `output` (the whole answer in chunks by `ask` and `call`) is replaced by
|
|
|
|
|
this form, the part's `form` raised (§780), and the runner's tool is its one reader; the runner's objects
|
|
|
|
|
`step-outputs`, which hold 0 bytes, go, dropped through the bus module.
|
|
|
|
|
Built in H2 in the build seats' definitions, the three build modules (mesh-catalog) and the runner. How it is
|
|
|
|
|
checked: whole (Go build module): a failing unit test's words are read through `runner_step_output`; an output past
|
|
|
|
|
its max-age answers "no longer kept".
|
|
|
|
|
- §821 **Every event of the delivery parts is waited on by its seat and name.** (H-A-338 (4), H-A-343) Every event
|
|
|
|
|
the runner says (`pipeline-started`, `step-ended`, `pipeline-ended`, `wait-held`, `wait-ended` and the re-pin's), the
|
|
|
|
|
the runner says (`pipeline-started`, `step-ended`, `pipeline-ended`, `wait-held`, `wait-ended` and `re-pinned`, new,
|
|
|
|
|
carrying `pipeline`, `mover` and `revision` when a kept mover is re-pinned, H-A-349 DQ-13), the
|
|
|
|
|
builder's `ask-taken` and `version-reserved` and the holder of `mesh-wants`' `ask-taken` are declared in their
|
|
|
|
|
seat's definition under the seat's events family, so a wait by seat and event name (`mesh_wait` with
|
|
|
|
|
`mesh-pipeline-runner.pipeline-ended`) is answered and no session reads a journal on a timer. Built in H2 in the
|
|
|
|
@@ -225,16 +242,17 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
ask it 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; 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, H-A-338 (5); row 158) The builder's publish
|
|
|
|
|
- §793 **The publish queue is a work-queue stream.** (H-A-290, H-A-291, H-A-338 (5), H-A-349 DQ-6; row 158) The builder's publish
|
|
|
|
|
items travel on its work queue `publishes` (§820), subject `publish.<holder>.<class>.<module>.<version>` with class
|
|
|
|
|
`live` (a build a pipeline's step waits on) or `again` (asked again at a start), one consumer per holder and class
|
|
|
|
|
that the builder pulls, `live` first, at most four sends in flight per holder (H-A-290 (3)); an item is acknowledged
|
|
|
|
|
`live` (a build a pipeline's step waits on) or `again` (asked again at a start), one consumer per holder and class,
|
|
|
|
|
declared with the stream in the builder's `requires`, that the builder pulls, `live` first, at most four sends in flight per holder (H-A-290 (3)); an item is acknowledged
|
|
|
|
|
when its publish is heard or confirmed (H-A-274), terminated when its build is withdrawn or superseded (H-A-290 (2),
|
|
|
|
|
H-A-291 (1)). `builder_publish_queue` reads the stream's counts per holder and class, the oldest and newest, and a
|
|
|
|
|
capped list; `builder_publish_drop` (module, version, why) terminates one item; `builder_publish_first` (module,
|
|
|
|
|
version, why) puts one item again as `live` and terminates the old; both are written in the hand-act log. Fate: the
|
|
|
|
|
version, why) puts one item again as `live` under the message id
|
|
|
|
|
`<holder>.live.<module>.<version>` and terminates the old; both are written in the hand-act log. Fate: the
|
|
|
|
|
state bucket of publish items, its listing and its relisting go; its items are put on the stream once at the
|
|
|
|
|
builder's first start of this release, each with the message id `<holder>.<module>.<version>`, so a move started
|
|
|
|
|
builder's first start of this release, each with the message id `<holder>.<class>.<module>.<version>`, so a move started
|
|
|
|
|
twice puts each item once within the duplicates window; then the bucket is dropped through the bus module. Built in
|
|
|
|
|
H2. How it is checked: whole (builder): a live publish enqueued behind 100 `again` items is sent first; a dropped
|
|
|
|
|
item is never sent; a move run twice puts each item once.
|
|
|
|
@@ -250,7 +268,9 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
language and kind and its count; `builder_unbuildable` lists them. Fate: the line per module and definition goes.
|
|
|
|
|
Built in H2. How it is checked: unit: 6,500 unbuildable plans write one line.
|
|
|
|
|
- §796 **A tag names its commit; the builder reads it before it reserves.** (H-A-234 (2), H-A-245, H-A-246, H-A-341
|
|
|
|
|
(3); rows 73, 121) The seat `git`'s `tags` answer gains `commit` per tag, and its listing's description says a
|
|
|
|
|
(3), H-A-350 DMC-3; rows 73, 121) The seat `git`'s `tags` answer, a list of strings today, becomes a list of
|
|
|
|
|
items `{tag, commit}`, the seat's `form` raised to 2 and read tolerantly (§780) by every reader (the builder's
|
|
|
|
|
versions claim, mesh-sdk's bootstrap copy of the seat); its listing's description says a
|
|
|
|
|
missing directory answers `not-found` (H-A-232): one contract change, its holder the forge module and mesh-sdk's
|
|
|
|
|
bootstrap copies in one group. The builder reads a module's tags once per catalog revision it reserves under, and
|
|
|
|
|
skips a number whose tag stands at another commit, with the finding `version-tagged-elsewhere` (scope module),
|
|
|
|
@@ -273,9 +293,10 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
- §799 **A fetch or a publish that meets its holder away is a transport fault.** (ADR 0668 §1 and ADR 0664 §1 (insights of 2026-11-21,
|
|
|
|
|
accepted); ADR 0664 §2; H-A-301, H-A-341 (8), H-A-342 (1); row 178) A build or check step whose fetch of its source meets a connection fault or a 401 or 5xx
|
|
|
|
|
answer of the forge, or whose publish to a registry seat meets no responders or a bundle that exited, ends its run
|
|
|
|
|
`again`, never the step (ADR 0664 §1), with no seat call to learn why; the tool runner settles the ask with a
|
|
|
|
|
delay of 15 s after the first run and 60 s after the second (`again-delays`, a setting of each build module, default
|
|
|
|
|
"15s,60s", so three runs span the one-minute absence met on 2026-11-21), and a third run's fault ends the step failed
|
|
|
|
|
`again`, never the step (ADR 0664 §1), with no seat call to learn why. The build module passes its delay with
|
|
|
|
|
its `again` (the bundle's own delayed settle): 15 s after the first run and 60 s after the second (`again-delays`,
|
|
|
|
|
a setting of each build module, default "15s,60s", so three runs span the one-minute absence met on 2026-11-21);
|
|
|
|
|
the tool runner's own back-off changes nothing (H-A-350 DMC-7); and a third run's fault ends the step failed
|
|
|
|
|
with the why `fetch: <words>` or `publish: <words>`, whichever met the fault (ADR 0664 §2), which the builder and the runner say apart from a build's failure. Built
|
|
|
|
|
in H2 in the build seats' conformance kit (ADR 0664 §6) and the three build modules. How it is checked: the
|
|
|
|
|
conformance kit holds a fetch met by a 401 and a publish met by no responders to `again`, and three such runs to the step failed
|
|
|
|
@@ -284,7 +305,9 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
H-A-327, H-A-338 (3), H-A-339 (6), H-A-340 (6), H-A-341 (7); rows 168, 170, 194) A step's summary counts `not-run`
|
|
|
|
|
apart from passed and failed, with each test's name and reason; a level whose tests passed or did not run passes,
|
|
|
|
|
its not-run listed; a test lacking tooling its step does not give says NOT RUN (H-A-294). A Go artifact may declare
|
|
|
|
|
`check-needs` with the value `node-modules` in its manifest: the runner then asks the seat `node-build-node` a step of
|
|
|
|
|
`check-needs` with the value `node-modules` in its manifest, which replaces the marker file `check-needs` in a
|
|
|
|
|
package's directory in the same release: the marker goes and its readers (the Go build module's digest, the
|
|
|
|
|
delivery SDK's `steprun.AskNeeds`) read the field (H-A-350 DMC-6); the runner then asks the seat `node-build-node` a step of
|
|
|
|
|
the new accepted kind `install` (input: the module's package lock at the commit) before the integration level; the
|
|
|
|
|
Node build module installs from the npm registry seat with an integrity-checked install (`npm ci`) and no install
|
|
|
|
|
scripts, keeps the tree as an archive in its `outputs` under the lock's digest (§820), and the step's end carries the
|
|
|
|
@@ -297,8 +320,9 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
catalog's `check-needs`), the build seats' definitions, the three build modules and those two modules' tests. How it
|
|
|
|
|
is checked: whole (Go build module): the forge module's whole-seat test runs with its npm tree; a test whose setup
|
|
|
|
|
is starved runs again and ends could-not-run at the third run; unit (Node build module): an install runs no script.
|
|
|
|
|
- §801 **Every build seat says what it takes and what runs.** (ADR 0525 §4, §10; H-A-302 (4), H-A-320 (3); rows 99,
|
|
|
|
|
179, 189) Each build seat's verb `current` answers, per holder, whether it takes check asks and why not (`paused`,
|
|
|
|
|
- §801 **Every build seat says what it takes and what runs.** (ADR 0525 §4, §10; H-A-302 (4), H-A-320 (3), H-A-350
|
|
|
|
|
DMC-16; rows 99, 179, 189) Each build seat's verb `current` (the build-step part's, its form replaced by this one and
|
|
|
|
|
the part's `form` raised) answers, per holder, whether it takes check asks and why not (`paused`,
|
|
|
|
|
`capacity 0`, `unhealthy`, with since when), and every ask it runs, whoever asked it (the builder's delivery asks
|
|
|
|
|
included); the build modules' steps read tools answer the steps state they keep, never empty while steps run;
|
|
|
|
|
`build_current` (the builder's tool) asks every holder and answers them together. Built in H2 in the three build
|
|
|
|
@@ -308,12 +332,17 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
### The indexer (seat `mesh-catalog`'s holder; mesh-delivery-indexer)
|
|
|
|
|
|
|
|
|
|
- §802 **A module moves only when its own build source changes.** (ADR 0267 §1, §2; ADR 0499 §2; H-A-202, H-A-298 (1),
|
|
|
|
|
H-A-338 (9); row 175) A module's fingerprint tree input is ADR 0499 §2's: the hash over its manifest and its named
|
|
|
|
|
H-A-338 (9), H-A-349 DQ-8, H-A-350 DMC-5; row 175) A module's fingerprint tree input is ADR 0499 §2's (already
|
|
|
|
|
built so in the indexer's inputs): the hash over its manifest and its named
|
|
|
|
|
paths where every artifact names `paths`, else its directory's tree object at the commit, with the directories of
|
|
|
|
|
its same-repository requirements taken in as H-A-202 has it; never the repository's commit. A commit outside them
|
|
|
|
|
moves nothing. The indexer and the builder take the new fingerprint function in one release. Fate: the fingerprint
|
|
|
|
|
its same-repository requirements taken in as H-A-202 has it; never the repository's commit. A mesh package of the module's
|
|
|
|
|
own repository that no module has published yet enters by its directory's tree, never by the head commit the gate's
|
|
|
|
|
source names (the same source, the same fingerprint); a package of another repository not yet published leaves the
|
|
|
|
|
module without a fingerprint until it is, said as `NoPackageVersion` today. A commit outside them moves nothing. The
|
|
|
|
|
one fingerprint function is the indexer's (`internal/fingerprint`, `form.go`); the builder reads what the indexer
|
|
|
|
|
writes and takes only the release, in one group with it. Fate: the fingerprint
|
|
|
|
|
over the repository's commit goes; every module's fingerprint changes once, at H2's delivery (§818). Built in H2 in
|
|
|
|
|
the indexer, the builder and mesh-sdk's one fingerprint function (ADR 0499 §2). How it is checked: whole (indexer): a
|
|
|
|
|
the indexer. How it is checked: whole (indexer): a
|
|
|
|
|
commit touching two test files of two modules in a repository of 36 moves those two and their importers alone.
|
|
|
|
|
- §803 **A take-in says what it waits on.** (H-A-298 (2); row 175) A take-in waiting longer than a minute on another
|
|
|
|
|
part (the seat `git`'s listing, a package's versions, a registry) writes one journal line naming the part, the verb
|
|
|
|
@@ -338,38 +367,52 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
with `module` and `repository` filters applied while reading, at most 768 KB, with `capped` and the cursor of §779.
|
|
|
|
|
Built in H2. How it is checked: unit.
|
|
|
|
|
|
|
|
|
|
### The delivery repository
|
|
|
|
|
|
|
|
|
|
- §823 **The stale copies at the delivery repository's root go.** (H-A-350; principle 3, one copy per thing) The
|
|
|
|
|
directories `contracts/` and `sdk/` at mesh-delivery's root, copies of the delivery contracts module and the
|
|
|
|
|
delivery SDK that no module builds from, are removed in H2 as a subtask of their own, after every reader is moved to
|
|
|
|
|
`modules/mesh-delivery-contracts` and `modules/mesh-delivery-sdk`. How it is checked: the repository's check finds
|
|
|
|
|
no import of either path, and the indexer's module graph is unchanged by the removal.
|
|
|
|
|
|
|
|
|
|
### The catalog's checks
|
|
|
|
|
|
|
|
|
|
- §814 **The validator reads the mesh's seat list, counts only new problems, and refuses an uncapped store.**
|
|
|
|
|
(H-A-299 (2), H-A-329, H-A-338 (10), H-A-339 (1), (8); rows 196, 198) The seat `mesh-catalog` gains the read verb
|
|
|
|
|
`seat-list` answering the seat list the mesh holds as one object in the indexer's objects, by digest (`digest`,
|
|
|
|
|
(H-A-299 (2), H-A-329, H-A-338 (10), H-A-339 (1), (8), H-A-349 DQ-5, DQ-10, H-A-350 DMC-9; rows 196, 198) The
|
|
|
|
|
seat `mesh-catalog` gains the read verb `seat-list` answering the seat list the mesh holds as one object in the
|
|
|
|
|
indexer's objects `seat-lists` (§820), one object per digest (`digest`,
|
|
|
|
|
`size`, `object`), which the manifest validator program takes by address, so a run by hand reads what the live
|
|
|
|
|
validate reads. The step `validate` counts, for a module it touches, only the problems new against its before case
|
|
|
|
|
(`causedProblems`); `indexer_validate_before` (pipeline, module) answers the before case's problems it did not count.
|
|
|
|
|
validate reads. The step `validate`, the assigner's, counts for a module it touches only the problems new against its before case
|
|
|
|
|
(its `causedProblems`, which today counts every problem of a touched module); `assigner_validate_before` (pipeline,
|
|
|
|
|
module) answers the before case's problems it did not count.
|
|
|
|
|
The validator refuses a delivery module's state, log or objects entry with no cap (§812); a delivery module is one
|
|
|
|
|
whose manifest claims a seat of the delivery system, which the validator reads from the claims; a foundation part's
|
|
|
|
|
old-section entry declares its cap in that section (H-A-229, ADR 0595 §10) and is never refused for lacking the new
|
|
|
|
|
form. Built in H2 in the indexer, the manifest validator and mesh-sdk's catalog. How it is checked: whole (indexer): a
|
|
|
|
|
whose manifest claims a seat of the delivery system, which the validator reads from the claims; the foundation parts among
|
|
|
|
|
the delivery modules are the indexer, the builder, the runner, the assigner, the gate, the teller and the delivery
|
|
|
|
|
contracts module (ADR 0619 §1), and a foundation part's old-section entry declares its cap in that section (H-A-229, ADR 0595 §10) and is never refused for lacking the new
|
|
|
|
|
form. Built in H2 in the indexer, the assigner, the manifest validator and mesh-sdk's catalog. How it is checked: whole (indexer): a
|
|
|
|
|
run 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; an uncapped entry of a delivery module is refused, a
|
|
|
|
|
foundation part's capped old-section entry is not.
|
|
|
|
|
- §819 **Every module H2 touches ends with fewer tests than it starts with.** (ADR 0548; the test budget, 50
|
|
|
|
|
integration and 500 unit per module; H-A-340 (8); rows 115 and the row of 18:40 on the budget) Each module a pull
|
|
|
|
|
request of H2 changes carries fewer tests at H2's end than at its start, counted as the build node counts them
|
|
|
|
|
(subtests included) and reported by each pull request's check. The starting counts: by the build node at H1's end,
|
|
|
|
|
integration and 500 unit per module; H-A-340 (8), H-A-349 DQ-14; rows 115 and the row of 18:40 on the budget) Each
|
|
|
|
|
module a pull request of H2 changes carries fewer tests at H2's end than at its start, as the check counts them: each
|
|
|
|
|
pull request's check reports the module's count at its base and at its head, and the budget is held to that way of
|
|
|
|
|
counting. The figures below are guesses, said as such, from two other ways of counting: by the build node at H1's end,
|
|
|
|
|
the indexer 538 integration, the assigner 64 integration, the node-engine 1,716 unit, the NFS server module 51
|
|
|
|
|
integration and the package manager module 121 integration; by top-level test functions on the trunks of
|
|
|
|
|
2026-11-21 (subtests not counted), the indexer 6 integration and 170 unit, the assigner 9 and 87, the runner 4 and
|
|
|
|
|
105, the builder 18 and 167, the node-engine 11 and 1,716. The NFS server and package manager modules shrink to 50
|
|
|
|
|
integration tests in H2. How it is checked: the check's counts per module in each pull request, read by its review
|
|
|
|
|
2026-11-21 (`go test -list`, with and without the integration tag), the indexer 6 integration and 167 unit, the
|
|
|
|
|
assigner 9 and 86, the runner 4 and 105, the builder 18 and 167, the node-engine 11 and 1,715, the NFS server module
|
|
|
|
|
0 and 51, the package manager module 3 and 118. The NFS server and package manager modules come within the budget
|
|
|
|
|
as the check counts them in H2. How it is checked: the check's counts per module in each pull request, read by its review
|
|
|
|
|
against the starting count.
|
|
|
|
|
|
|
|
|
|
### 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 §1; ADR 0666
|
|
|
|
|
§11, §18; ADR 0682 §1, §3; H-A-332, H-A-334 (1), H-A-338 (2), H-A-339 (3); 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`, `policy`, and `check`, which names a build seat and a step kind (for hq: `node-build-go`, `unit`,
|
|
|
|
|
is put to them; rows 176, 177; H-A-349 DQ-9) A registration of the seat `mesh-catalog` takes a source-only form, kept in the
|
|
|
|
|
same states as a module's under the key `source.<owner>.<name>` (its history under the same key), with `origin`,
|
|
|
|
|
`branches` (one), `policy` and `check`, which names a build seat and a step kind (for hq: `node-build-go`, `unit`,
|
|
|
|
|
at the repository's root), never a free command; it 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 pipeline runner's run on request of a pull request's head (ADR 0666 §18) runs that one step on
|
|
|
|
@@ -404,7 +447,8 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
module's budget). It is read from the gate's ended record (`gate_record`): `class` core, `delivery-time` under ten
|
|
|
|
|
minutes, no `over-budget` raised for it, quoted with its phases (§785); and from the hand-act log, empty for every
|
|
|
|
|
delivery part from `merge-called` to the last `running`; no other pipeline held the slot meanwhile. No hand act
|
|
|
|
|
touches the delivery system during it: no hand pack, no held put, no `runner_cancel`, `runner_end_again`, rerun,
|
|
|
|
|
touches the delivery system during it: no hand pack, no held put, no call of the seat verb `cancel` (H-A-350 DMC-8),
|
|
|
|
|
`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.
|
|
|
|
|
- §817 **Proof 2: a package and its importer in two repositories, one merge call, within ten minutes.** (ADR 0282 §1;
|
|
|
|
@@ -417,190 +461,3 @@ its own pipelines, with no hand pack (section 7 of the plan). Its two proofs (§
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
## Design questions
|
|
|
|
|
|
|
|
|
|
Found by H2's prepare (`mesh-preparer`, 2026-11-21 22:40 CET), for the lead's answers (playbook 07, step 0b). The code was
|
|
|
|
|
read at `origin/main`: `mesh-delivery` `7e597a623eb2`, `mesh-catalog` `553bfb0ccf7c`, `mesh-host` `637cfb1fd044`,
|
|
|
|
|
`mesh-sdk` `bdc5cff0d63d`, `mesh-contracts` `87eab81be134`, `mesh-tools` `02675a43eaf8`, `mesh-networking`
|
|
|
|
|
`19a04dfc602a` (a sibling for the build). The build maps are in [H2-build-maps](H2-build-maps/). Each recommendation is
|
|
|
|
|
the preparer's, said as one.
|
|
|
|
|
|
|
|
|
|
- **DQ-1** (§777) The line names the accepted kinds `build` on `mesh-builds` and `validate` and `compose` on `mesh-wants`;
|
|
|
|
|
both seats accept one kind, `step`, today (`mesh-delivery` `seats/mesh-builds/seat.json`, `seats/mesh-wants/seat.json`
|
|
|
|
|
`accepts`; the runner puts every step on `accept.step`, `cmd/mesh-delivery-pipeline/asks.go:27`). Left to the builder:
|
|
|
|
|
whether the kinds are renamed and split. Recommendation: keep the one kind `step` on each seat and read the line's
|
|
|
|
|
kinds as the step the ask names, so no subject and no reader changes.
|
|
|
|
|
answered: H-A-349 DQ-1.
|
|
|
|
|
- **DQ-2** (§777) The line rebuilds the `mesh-builds` stream empty through `nats_recreate`; the `mesh-wants` stream
|
|
|
|
|
`SEAT_MESH_WANTS` holds 1,598 messages and 0 consumers as well (live, `nats.nats_streams`, 22:25 CET), and `mesh-builds`'
|
|
|
|
|
1,558 now. Left: the fate of `SEAT_MESH_WANTS`' messages. Recommendation: rebuild both empty on the same warrant, before
|
|
|
|
|
the new builder and the new assigner start.
|
|
|
|
|
answered: H-A-349 DQ-2.
|
|
|
|
|
- **DQ-3** (§782) The line names "mesh-sdk's wrappers around one bus handle" without naming them; mesh-sdk holds several
|
|
|
|
|
(`process.Conn`'s state and stream calls, `stdio`'s `BusState` through the runtime, `views`). Recommendation: name the
|
|
|
|
|
wrapper row 137 met twice, by package and type, in the line.
|
|
|
|
|
answered: H-A-349 DQ-3.
|
|
|
|
|
- **DQ-4** (§777, §778) The runner's second put under `AgainID` with its bound key `ask2.` serves the build seats today
|
|
|
|
|
(`internal/pipeline/asks.go:27-60`, `:134-160`); the line says the runner puts again only on a transport fault but gives
|
|
|
|
|
`AgainID` and `ask2.` no fate. Recommendation: both go for every seat, by §777's rule.
|
|
|
|
|
answered: H-A-349 DQ-4.
|
|
|
|
|
- **DQ-5** (§783, §820) Which delivery modules are foundation parts (ADR 0619 §1, ADR 0666 §4) that declare their stores
|
|
|
|
|
in the old section, and which ask in `requires` by template, is not said; today the runner, the builder, the indexer and
|
|
|
|
|
the assigner use the old sections (`mesh-delivery-pipeline/module.json:205-240`, `mesh-delivery-builder/module.json:120-140`)
|
|
|
|
|
and the bridge uses `requires` (`mesh-delivery-forge-bridge/module.json:40-45`). Recommendation: the line lists the
|
|
|
|
|
foundation parts by module.
|
|
|
|
|
answered: H-A-349 DQ-5.
|
|
|
|
|
- **DQ-6** (§793) The work queue `publishes` (§820: work queue, 64 MiB, 7 days) names its subject and consumers per
|
|
|
|
|
holder and class, but not whether the consumers are declared in the builder's `requires` or derived by the broker, and
|
|
|
|
|
the move's message id `<holder>.<module>.<version>` names no class while `builder_publish_first` puts an item again as
|
|
|
|
|
`live` within the duplicates window. Recommendation: the builder declares the stream and its consumers in `requires`,
|
|
|
|
|
and `builder_publish_first` puts under an id carrying the class.
|
|
|
|
|
answered: H-A-349 DQ-6.
|
|
|
|
|
- **DQ-7** (§808, H-A-345) The vault's seat serves no write of a module's own secret, and its read `own` answers only the
|
|
|
|
|
node-engine of a machine, sealed to the machine's key, so a forge module process can neither write nor read its token
|
|
|
|
|
through `own` (`mesh-contracts` `identity-and-access/seats/mesh-vault/seat.json`, verbs `own`, `get`, `licence-put`;
|
|
|
|
|
live `mesh-vault.own`'s description, 22:27 CET). The write verb is a gap of this milestone (H-A-345); the read is a gap
|
|
|
|
|
too. Recommendation: add to the vault's seat a two-step sealed write of a module's own secret modelled on `licence-put`
|
|
|
|
|
(the module named by the caller's account, its newest generation kept), and read the token through `get`, sealed to the
|
|
|
|
|
process's key; built in `mesh-catalog` `modules/mesh-vault` and `mesh-contracts`, before the forge module's §808 work.
|
|
|
|
|
answered: H-A-349 DQ-7.
|
|
|
|
|
- **DQ-8** (§802) A mesh Go package that no module the indexer holds has published enters the fingerprint by the commit the
|
|
|
|
|
gate's source names for its repository (`mesh-delivery` `internal/index/form.go:113-125`, design 47 G A-365), and the
|
|
|
|
|
import form's versions are a holding module's published commit (`form.go:30-33`); the line does not say what such a
|
|
|
|
|
package enters by under ADR 0499 §2. Recommendation: a package of the module's own repository enters by its directory's
|
|
|
|
|
tree, as a directory replace does already (`form.go:39-41`); another repository's unpublished package leaves the module
|
|
|
|
|
without a fingerprint until it is published, said as today's `NoPackageVersion`.
|
|
|
|
|
answered: H-A-349 DQ-8.
|
|
|
|
|
- **DQ-9** (§815) The source-only registration has no module, while the state `registrations` is keyed `<module>` and a
|
|
|
|
|
registration requires `module`, `origin`, `path` and `branches` (`seats/mesh-catalog/seat.json` `defs.Registration`); the
|
|
|
|
|
line names `repository` and one `branch`. Left: its key, its field names against `origin` and `branches`, and its history
|
|
|
|
|
key. Recommendation: key `source.<owner>.<name>` in the same states, fields `origin`, `branches` (one), `policy`,
|
|
|
|
|
`check`, so readers of registrations read one form.
|
|
|
|
|
answered: H-A-349 DQ-9.
|
|
|
|
|
- **DQ-10** (§814, §820) The seat list as one object "in the indexer's objects, by digest" is a store §820's table does not
|
|
|
|
|
hold: its objects entry, cap, key life and deleter. Recommendation: the indexer's objects `seat-lists`, 64 MiB, one object
|
|
|
|
|
per digest, the indexer deleting every object but the newest two at each new list.
|
|
|
|
|
answered: H-A-349 DQ-10.
|
|
|
|
|
- **DQ-11** (§813 (4)) The node-engine marks each rule it writes `mesh-host <id> <digest>` and recognises its own rules and
|
|
|
|
|
stale ones by that mark (`mesh-host` `internal/firewall/firewall.go:415-427`, `:782`); the line's comment
|
|
|
|
|
`derived <module> <listen> scope <…>` gives the mark no fate. Recommendation: the scope words follow the mark in the one
|
|
|
|
|
comment, so the reconciling keeps reading the mark.
|
|
|
|
|
answered: H-A-349 DQ-11.
|
|
|
|
|
- **DQ-12** (§813 (1)) "A composition key" is not named: the state and key the holder of `mesh-wants` writes by
|
|
|
|
|
compare-and-set (its `wants` `want.<node>.<module>`, `compositions` `<group>.<heads>`, or the node-engine's composed
|
|
|
|
|
bucket), and `run`'s form: the node-engine contract already carries `run` as a string (`mesh-contracts`
|
|
|
|
|
`go/seats/nodeengine/contract.go:1764`) while the line says a pipeline sequence. Recommendation: name the state and key,
|
|
|
|
|
and keep the existing field `run` holding the sequence as a decimal string, so no form is raised.
|
|
|
|
|
answered: H-A-349 DQ-12.
|
|
|
|
|
- **DQ-12b** (§813 (3)) `engine_composition_diff` is "the node-engine's tool", but the node-engine serves only the seat
|
|
|
|
|
`node-engine`'s verbs and has no tools bundle (`mesh-host`: no `engine_` tool name in any file; live `ace/node-engine.*`
|
|
|
|
|
are seat verbs). Recommendation: a read verb `composition-diff` on the seat `node-engine`, beside `composition`.
|
|
|
|
|
answered: H-A-349 DQ-12b.
|
|
|
|
|
- **DQ-13** (§821) "The re-pin's" event is not named, and the runner's seat declares none for a re-pin today
|
|
|
|
|
(`seats/mesh-pipeline-runner/seat.json` events). Recommendation: the line names it (`re-pinned`, carrying the pipeline,
|
|
|
|
|
the mover and the revision).
|
|
|
|
|
answered: H-A-349 DQ-13.
|
|
|
|
|
- **DQ-14** (§819) The starting counts by `go test -list` without and with `-tags integration` (top-level functions, 22:30
|
|
|
|
|
CET) differ from the line's: the indexer 167 unit and 6 integration (line: 170 and 6), the assigner 86 and 9 (87 and 9),
|
|
|
|
|
the node-engine 1,715 and 11 (1,716 and 11); the runner 105 and 4 and the builder 167 and 18 agree. By the tag the NFS
|
|
|
|
|
server module holds 0 integration and 51 unit, the package manager module 3 and 118, where the line's 51 and 121 are the
|
|
|
|
|
build node's counts, which take untagged tests in. Recommendation: each pull request's check gives the starting count
|
|
|
|
|
at its base, and the line keeps its figures as a guess said as one.
|
|
|
|
|
answered: H-A-349 DQ-14.
|
|
|
|
|
- **DQ-15** (§776) The forge module is TypeScript; the line places `away` in mesh-sdk's seat error answer without saying
|
|
|
|
|
whether mesh-sdk's TypeScript seat helpers carry it. Recommendation: they do, in the same commit.
|
|
|
|
|
answered: H-A-349 DQ-15.
|
|
|
|
|
- **DQ-16** (§810) `class` is `core` "when it moves a core module of ADR 0282 §1"; the gate holds no list or field naming a
|
|
|
|
|
module's class (`grep -rn -i "core\|class" --include='*.go' mesh-catalog/modules/mesh-delivery-gate/cmd` finds none).
|
|
|
|
|
Left: where the gate reads it. Recommendation: the gate reads it from a setting `core-modules` (a list, default the
|
|
|
|
|
delivery system's modules and the node-engine), so the self-check's probe and the gate read one list.
|
|
|
|
|
answered: H-A-349 DQ-16.
|
|
|
|
|
|
|
|
|
|
## Design meets code
|
|
|
|
|
|
|
|
|
|
Each entry: the design line, the code (at the commits named above), which of the three it is, and the preparer's
|
|
|
|
|
recommendation, said as one.
|
|
|
|
|
|
|
|
|
|
- **DMC-1** (§777) *A form the code cannot take.* The seat definition's `accepts` carries no `max-age`, `max-msgs`, ack wait,
|
|
|
|
|
in-progress, max ack pending, max deliveries or duplicates window; the streams and the shared worker are derived by the
|
|
|
|
|
grants part with their own values (ack wait 60 s, max deliver 5, retain 7 days; `mesh-delivery`
|
|
|
|
|
`modules/mesh-grants/internal/buscompose/derived.go:86-110`, `:343-358`), and mesh-sdk keeps a second `buscompose`
|
|
|
|
|
(`mesh-sdk` `go/buscompose/nats.go:96-98`). Live max age is 168 hours. Recommendation: the seat definition's accepts gain
|
|
|
|
|
these settings, read by the one derivation in mesh-sdk's `buscompose`, which the grants part takes.
|
|
|
|
|
answered: H-A-350 DMC-1.
|
|
|
|
|
- **DMC-2** (§776) *A part the line assumes built that is not.* mesh-sdk has no seat error answer: error kinds are each
|
|
|
|
|
seat's own (`git`'s `ErrorKind`: `refused`, `not-found`, `failed`, `seats/git/seat.json`; `mesh-catalog`
|
|
|
|
|
`modules/gitea/seat.ts:71`). Recommendation: add `away` to the error kinds of every seat the delivery parts call
|
|
|
|
|
(`git` first), and mesh-sdk's kept call reads `away` as a transport fault by the answer's `error-kind`.
|
|
|
|
|
answered: H-A-350 DMC-2.
|
|
|
|
|
- **DMC-3** (§796) *A form the code cannot take.* The `tags` answer is a list of strings (`seats/git/seat.json` `tags`);
|
|
|
|
|
`commit` per tag makes each item an object, a form raised (§780) for every reader (`mesh-delivery-builder`
|
|
|
|
|
`internal/versions/claim.go:213`, `mesh-sdk` `seatlist/bootstrap/git.json`). Recommendation: items become `{tag, commit}`
|
|
|
|
|
with the seat's `form` 2, read tolerantly by §780.
|
|
|
|
|
answered: H-A-350 DMC-3.
|
|
|
|
|
- **DMC-4** (§780) *A part placed where it is not.* The seat generator is `mesh-delivery`'s
|
|
|
|
|
`modules/mesh-delivery-sdk/seatgen`, not mesh-sdk's; mesh-sdk's `seatdef` reads definitions only. Recommendation: build the
|
|
|
|
|
tolerant decoders and the `form` check in `seatgen`, and regenerate every seat in `mesh-delivery` and `mesh-contracts`.
|
|
|
|
|
answered: H-A-350 DMC-4.
|
|
|
|
|
- **DMC-5** (§802) *A part placed where it is not, and a form already built.* The one fingerprint function is the
|
|
|
|
|
indexer's (`mesh-delivery-indexer/internal/fingerprint/fingerprint.go:1-5`: "the indexer's own, and nobody else's"; the
|
|
|
|
|
builder reads what the indexer writes), not mesh-sdk's; and its tree input is already the directory's tree or the named
|
|
|
|
|
paths (`internal/index/inputs.go:97-118`); the commit enters through DQ-8's packages. Recommendation: build §802 in the
|
|
|
|
|
indexer's `fingerprint` and `form.go`, the builder taking nothing new but the release in one group.
|
|
|
|
|
answered: H-A-350 DMC-5.
|
|
|
|
|
- **DMC-6** (§800) *A rule in code the line breaks.* `check-needs` is a marker file in a package's directory, kept "not a
|
|
|
|
|
manifest field" on purpose (`mesh-catalog` `modules/mesh-build-go/cmd/mesh-build-go/digest.go:59-66`), read by
|
|
|
|
|
`mesh-delivery-sdk` `steprun.AskNeeds`; the line makes it a manifest field of a Go artifact. Recommendation: the line
|
|
|
|
|
holds: the manifest field replaces the marker file, whose fate (it goes, its readers moved) the line states.
|
|
|
|
|
answered: H-A-350 DMC-6.
|
|
|
|
|
- **DMC-7** (§799) *A part placed where it is not.* The delay before a run ended `again` is offered again is the tool
|
|
|
|
|
runner's `WorkBackoff` (5 s doubling to 10 minutes, `mesh-tools` `internal/bus/seat.go:71-79`, `:315`) or a bundle's own
|
|
|
|
|
`NakWithDelay` (`seat_pull.go:193`); the line says "the tool runner settles the ask with a delay of 15 s ... 60 s", a
|
|
|
|
|
build module's setting, built in the kit and the build modules. Recommendation: the build module passes its
|
|
|
|
|
`again-delays` with its `again` (the bundle's delay), so the tool runner changes nothing; mesh-tools' T3 then drops.
|
|
|
|
|
answered: H-A-350 DMC-7.
|
|
|
|
|
- **DMC-8** (§786, §789, §816) *Parts assumed built that are not.* The runner has no tools `runner_show`, `runner_cancel`
|
|
|
|
|
or `runner_movers` (`mesh-delivery-pipeline/module.json`, 14 tools; the verbs `show` and `cancel` exist on the seat).
|
|
|
|
|
Recommendation: `runner_show` and `runner_movers` are built in R8 as the tools table says; §816's `runner_cancel` reads as
|
|
|
|
|
the seat verb `cancel`.
|
|
|
|
|
answered: H-A-350 DMC-8.
|
|
|
|
|
- **DMC-9** (§814) *A part placed where it is not.* The validate step and `causedProblems` are the assigner's
|
|
|
|
|
(`mesh-delivery-assigner/cmd/mesh-delivery-assigner/validatestep.go:124`, `:203-230`), which counts every problem of a
|
|
|
|
|
touched module and only new ones of the rest; the line builds the counting in the indexer and names
|
|
|
|
|
`indexer_validate_before`. Recommendation: change `causedProblems` in the assigner and name the tool
|
|
|
|
|
`assigner_validate_before`.
|
|
|
|
|
answered: H-A-350 DMC-9.
|
|
|
|
|
- **DMC-10** (§813 (7)) *A part named that is not.* No seat `artifact-store`: the sweep holds `mesh-artifact-sweep`
|
|
|
|
|
(`artifact-store-tools`), the registry `mesh-artifact-store` and `oci-artifact-registry` (`distribution`); the registry's
|
|
|
|
|
`list` takes `name`, not `module` (`seats/oci-artifact-registry/seat.json`). Recommendation: read "the seat
|
|
|
|
|
`mesh-artifact-sweep`'s holder", and `list` takes `module` beside `name`.
|
|
|
|
|
answered: H-A-350 DMC-10.
|
|
|
|
|
- **DMC-11** (§813 (5)) *A part assumed built that is not.* No tool `nats_consumers`: the bus module has `nats_consumer` (one)
|
|
|
|
|
and `nats_backlog` (`mesh-catalog` `modules/nats/module.json`). Recommendation: `nats_consumers` is a new tool listing
|
|
|
|
|
consumers with the two sorts.
|
|
|
|
|
answered: H-A-350 DMC-11.
|
|
|
|
|
- **DMC-12** (§781, §813 (4)) *Parts assumed built that are not.* The node-engine seat has no `converged` and no verb with
|
|
|
|
|
`timeout` ("built in H1" in the line; `mesh-contracts` `seats/node-engine/seat.json`); the packet filter's holder
|
|
|
|
|
(`nftables`, TypeScript) serves `rules`, `reload`, `remove` and has no `allow`, asks no `converged` and holds no named
|
|
|
|
|
10 s (`mesh-catalog` `modules/nftables/client.ts`, `tools/index.ts`). Recommendation: the line says whether H2 builds
|
|
|
|
|
`converged` with its `timeout` and `allow`, or the clauses about them leave H2.
|
|
|
|
|
answered: H-A-350 DMC-12.
|
|
|
|
|
- **DMC-13** (§781) *A part assumed built that is not.* mesh-sdk has no settings reader: each module reads its
|
|
|
|
|
`${config:<key>}` files by names of its own (`mesh-delivery-pipeline/cmd/mesh-delivery-pipeline/askbounds.go:20-35`).
|
|
|
|
|
Recommendation: a reader in mesh-sdk takes a setting by its key from the words the node-engine composes, in a process
|
|
|
|
|
and in a bundle alike, and the runner's own readers move to it.
|
|
|
|
|
answered: H-A-350 DMC-13.
|
|
|
|
|
- **DMC-14** (§812) *A part assumed built that is not.* A state write answers its revision only (`mesh-sdk` `go/state.go:177`,
|
|
|
|
|
`:190`; `mesh-tools` `internal/bus/state.go:425`), and a publish's acknowledgement carries the stream and sequence, no
|
|
|
|
|
fill. Recommendation: the runtime's write answer carries the entry's `Fill` (`buscalls.Fill` exists), which the prune
|
|
|
|
|
helper judges.
|
|
|
|
|
answered: H-A-350 DMC-14.
|
|
|
|
|
- **DMC-15** (§778) *A part assumed built that is not.* "Drops its ask through the seat's `drop`": `mesh-builds` (verbs
|
|
|
|
|
`reserved`, `published`) and `mesh-wants` declare no `drop`; only the build-step part has one. Recommendation: D1 adds a
|
|
|
|
|
`drop` act to both seats, its holder ending the ask as the build seats' `drop` does.
|
|
|
|
|
answered: H-A-350 DMC-15.
|
|
|
|
|
- **DMC-16** (§791, §801) *A form the code cannot take as written.* The build-step part already has `output` (the whole
|
|
|
|
|
answer in chunks by `ask` and `call`) and `current` (the steps, capacity, paused) in other forms
|
|
|
|
|
(`mesh-delivery-contracts/parts/build-step.json`). Recommendation: the line's forms replace them with the part's `form`
|
|
|
|
|
raised, the runner's tool their one reader.
|
|
|
|
|
answered: H-A-350 DMC-16.
|
|
|
|
|