Write milestone H's design lines so the one model is decided before code
Design 47 carried the commit-on-a-watched-branch model and the earlier per-pull-request model side by side; the operator's answers of 2026-11-17 and 2026-11-20 (ADR 0682) lived only in lead answers. The part H-1 to H-3 (design 47 H §734 to §765) states the merge call as the start and group, the gate's watchdog, the take-in and validate step, one pipeline per take-in with none in parallel, the want rule, the builder's missing lines, reads made events, the missing read tools and what retires; G's contradicting lines are corrected in place, the main file gains the wake-up rule, tests 110 to 113 and the H row, and the glossary gains merge call, untaken head, take-in and mover. Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
+27
-3
@@ -600,7 +600,28 @@ controller (the planner, the rollout) until release 6 of ADR 0429; from each rel
|
||||
registering and changing one are trusted acts (ADR 0666 §2). The mesh knows modules, and a repository only as a
|
||||
module's git origin.
|
||||
- **watched branch** — a branch a module's registration names, whose commits start that module's pipeline and which a
|
||||
placement may choose for a node; registering one the forge does not protect is refused (ADR 0666 §3, §6).
|
||||
placement may choose for a node; registering one the forge does not protect is refused (ADR 0666 §3, §6), a refusal
|
||||
the operator removed on 2026-11-14 (design 47 G §5); a merge into it still needs its protection (ADR 0666 §11).
|
||||
- **merge call** — one call of the seat `git`'s verb `merge-pull` naming one or more pull requests, each at the head
|
||||
its caller names: from the delivery of design 47's milestone H the start of their delivery and, with two or more,
|
||||
their group; the forge module judges every member before it merges any and says the call as its event
|
||||
`merge-called`, from which the gate names the merged heads one source revision (ADR 0682). Not a merge made in the
|
||||
forge's own screen, which delivers nothing and leaves an **untaken head**.
|
||||
*Not:* ~~kick-off~~ (hq)
|
||||
- **untaken head** — a watched branch's head that the forge bridge said moved (`head-moved`) and that no source revision
|
||||
names within the gate's setting `untaken-bound`: a head moved outside the mesh, raised as the gate's finding
|
||||
`head-untaken` and delivered by nothing but a later merge call or the gate's hand take (ADR 0682; design 47 H §740).
|
||||
Not a pending revision, which is a source revision not yet taken in.
|
||||
*Not:* ~~merge-untaken~~ (hq)
|
||||
- **take-in** — the indexer's act on one source revision of a watched branch: the commits it names, the
|
||||
build-input fingerprints of the modules registered for those repositories, and one catalog revision of that branch,
|
||||
said as `take-in.taken` naming the **movers**; it validates no manifest (that is the pipeline step `validate`) and
|
||||
holds nothing for a named indexer (ADR 0682; A-476). Not a merge: what is taken in is a source revision the gate named.
|
||||
*Not:* ~~merge take-in~~ (hq)
|
||||
- **mover** — a module whose build-input fingerprint changed in a take-in, or a code dependent of one (a module, in any
|
||||
repository, that imports a package of one): the modules a take-in's one pipeline runs and delivers (A-476a; ADR
|
||||
0573 §3; ADR 0682). Not every module of the revision.
|
||||
*Not:* ~~moving module~~ (hq)
|
||||
- **run on request** — a pipeline run for a named commit or group that delivers nothing, asked by the runner's verb
|
||||
`run`; the indexer builds its candidate from the runner's `run-started` (ADR 0666 §18).
|
||||
- **artifact reference** — an artifact written `<module>:<artifact>`, such as `mesh-grants:program`: the end of a
|
||||
@@ -816,7 +837,8 @@ controller (the planner, the rollout) until release 6 of ADR 0429; from each rel
|
||||
level: a group holds deliveries, never groups. Its state is derived from its members, never set. From milestone G's
|
||||
delivery: a shared branch name carrying its issue number, complete when each member's commit has landed on its
|
||||
modules' watched branch, taken in as one source revision of that branch and run as one pipeline per watched branch
|
||||
(ADR 0666 §13).
|
||||
(ADR 0666 §13). From milestone H's delivery: the pull requests named in one **merge call**; no branch name and no
|
||||
pull request read after the call forms one (ADR 0682).
|
||||
- **hotfix** — one pull request in one repository, delivered at its merge (ADR 0401).
|
||||
- **feature** — one branch name across its repositories: in two or more, its pull requests are one delivery group,
|
||||
merged together and delivered member by member in the group's order; in one, a single pull request delivered as a
|
||||
@@ -890,7 +912,9 @@ controller (the planner, the rollout) until release 6 of ADR 0429; from each rel
|
||||
- **pending revision** — a source revision the running indexer has not taken in, because it names another build of
|
||||
the indexer or follows one that does: only the named indexer's own keys are written, the rest kept in the
|
||||
indexer's state `pending` until that indexer starts and takes it in (ADR 0633 §1 to §3). A group's members wait
|
||||
there too until the group's end, as members still gathered (§4).
|
||||
there too until the group's end, as members still gathered (§4). Ends at milestone H's delivery: a take-in holds
|
||||
nothing for a named indexer, and one that cannot be written waits as its unacknowledged `source-moved` (ADR 0682;
|
||||
design 47 H §744).
|
||||
- **canary** — the first node of a module's nodes, ordered by ring then name: a new fingerprint reaches it
|
||||
first and the module's other nodes only once it runs healthy there (ADR 0429 §6). Replaces sending to every
|
||||
machine at once from release 6 (§15); a fingerprint that fails there is held and the canary set back, or for
|
||||
|
||||
@@ -2,8 +2,10 @@
|
||||
layer: to-be
|
||||
status: in-progress
|
||||
code: [mesh-controller, mesh-catalog modules/mesh-delivery-gate, mesh-catalog modules/gitea, mesh-delivery, mesh-host, mesh-sdk, mesh-vault, mesh-contracts, mesh-tools, mesh-networking, hq 00-META/checks]
|
||||
updated: 2026-11-17
|
||||
updated: 2026-11-20
|
||||
decisions:
|
||||
- "ADR 0682"
|
||||
- "ADR 0681"
|
||||
- "ADR 0673"
|
||||
- "ADR 0672"
|
||||
- "ADR 0668"
|
||||
@@ -195,6 +197,16 @@ acting parts, the kept data on the bus restored with a delivery, and the verbs a
|
||||
section this file names in italics and does not hold is there, under the same name. A sentence that holds a delivered
|
||||
line and G's change together stays here.
|
||||
|
||||
**From milestone H's delivery, a delivery starts at the merge through the mesh** (ADR 0682; the operator,
|
||||
2026-11-20). One **merge call** of the seat `git`'s verb `merge-pull`, naming one or more pull requests, is a delivery's
|
||||
start and its group; the gate names the merged heads one source revision per watched branch and opens its delivery
|
||||
record, the indexer takes it in and names its **movers**, one pipeline runs per take-in and none in parallel, and a
|
||||
want names the newest released version whose pipeline passed. The forge bridge's one message per move of a watched
|
||||
branch's head is the gate's watchdog: a head no merge call delivered is an **untaken head**, said and delivered by
|
||||
nothing. Every line milestone H builds is in its part, opened by the plan
|
||||
[47-milestones/H-deliver-the-delivery-system.md](47-milestones/H-deliver-the-delivery-system.md) and cited as "design
|
||||
47 H §n" (§734 on); where an H line and a G line differ, the H line holds and the G line says so.
|
||||
|
||||
This is the delivery of [to-be 10](10-delivery.md) carried out. To-be 10 says what is built: the comparison
|
||||
of source and artifacts decides, and nothing here changes that. This design says who answers for one
|
||||
commit's journey, in what order the steps are allowed, and where each fact of it is kept. It was rewritten on
|
||||
@@ -1508,6 +1520,22 @@ way is written down before the switch (ADR 0526, which ADR 0522 §6 asked of R4g
|
||||
running versions are kept outside the artifact store on two nodes, each by digest with its module, artifact, commit, Go version and the
|
||||
steps that put it back, because the store's nightly collection removes a blob the controller did not record (ADR 0526 §6).
|
||||
|
||||
## Every delivery part wakes on its inputs alone
|
||||
|
||||
*ADR 0682 §9; issue 1982; the plan of milestone H, section 3.6.* A delivery part (the forge module, the forge
|
||||
bridge, the gate, the indexer, mesh-config, the runner, the builder, the build modules, the assigner, the node-engine,
|
||||
the grants part, the watchman, the condition keeper, the status view, the teller and the tool runner) keeps a watched
|
||||
copy of each of its own states, through one shape in mesh-sdk's state package (the shape the held pull request
|
||||
mesh-catalog #708 built for mesh-config, moved into mesh-sdk), and runs a pass only when an input it consumes changed,
|
||||
taking only the keys that input names. It keeps one timer, set to its earliest real deadline, a bound it states; it
|
||||
polls nothing, reads nothing of its own whole on a wake, and asks no call again on a timer. Which part moves onto the
|
||||
shape in which release is design 47 H §762. How it is checked: the code review of every delivery module from milestone
|
||||
H1 on refuses a timer that is no stated deadline, a poll and a whole re-read; mesh-sdk ships a test helper that counts
|
||||
the requests a pass makes, and each delivery module's integration test that starts it whole against the bus (ADR
|
||||
0548) asserts that a pass after one changed key requests that key alone; live, milestone H4 is proven by the bus's
|
||||
slow consumers and consumers behind at 0 for an hour, read with `mesh-broker.rates` (H §760) and the bus module's
|
||||
consumer reads.
|
||||
|
||||
## Acceptance tests
|
||||
|
||||
What the build proves before this design is implemented (research 055's direction):
|
||||
@@ -1664,7 +1692,7 @@ list:
|
||||
performance is fixed; no check starts real builds.
|
||||
37. **Nothing is delivered ahead.** Research 085's milestone is delivered with no part delivered ahead of it, read
|
||||
from its delivery record (ADR 0656, How it is checked).
|
||||
38. **A newer indexer is reached.** A merged revision naming a newer indexer gives, from the running indexer, a catalog
|
||||
38. **A newer indexer is reached.** *(Retires at milestone H, design 47 H §764.)* A merged revision naming a newer indexer gives, from the running indexer, a catalog
|
||||
graph revision that is the previous one with only the indexer's entry replaced; no other want moves; the new
|
||||
indexer is wanted, granted, started, and takes the revision in.
|
||||
39. **Revisions are kept, and stores say their fill.** A revision pinned by two records stays until both free it, one
|
||||
@@ -1706,7 +1734,7 @@ Each change ADR 0656 makes in an earlier record, and its test:
|
||||
are read by the indexer's candidate pass and by no running part (whole).
|
||||
48. **A process reports its handed build** (ADR 0639 §7). A part started while its node's want differs from what runs
|
||||
reports the build it was started with, and the node-engine seat's verb `process-builds` reads it (whole, node-engine).
|
||||
49. **The forge bridge reads a group from the gate's verb** (ADR 0633 §4, §5). The forge bridge sets the group on each
|
||||
49. **The forge bridge reads a group from the gate's verb** *(Retires at milestone H, design 47 H §764.)* (ADR 0633 §4, §5). The forge bridge sets the group on each
|
||||
merged message and publishes a group's end again from the seat `mesh-delivery`'s verb `groups`, and its account
|
||||
holds no read of the gate's `merges` state, so a read of it is refused (whole, forge bridge).
|
||||
|
||||
@@ -1728,11 +1756,9 @@ What milestone G's prepare found, and its test:
|
||||
(whole, gate, checker and forge module).
|
||||
53. **What is owed is said, answered and kept.** An `owed` said while the forge bridge is stopped is performed once after
|
||||
its restart; the bridge stopped between an act and its `owed.ended` repeats it and the forge holds it once; an
|
||||
undecodable act is said `undecodable`; an act unanswered 15 minutes is listed by `stalled`; the switch with a merge
|
||||
handed and not yet merged opens no `forge-made` record; a merge made at the forge opens one, said as `transition`
|
||||
with why `forge-made`, and a later merge in its repository follows it; the checker's `mesh/check` is performed by
|
||||
the bridge from the checker's `owed`, and a checker status the forge refuses is recorded in the checker's own
|
||||
state and listed in its stalled read (whole, gate, checker and forge bridge).
|
||||
undecodable act is said `undecodable`; an act unanswered 15 minutes is listed by `stalled` (whole, gate and forge bridge). The rows of a `forge-made` record
|
||||
and of the checker's `mesh/check` went: no record is marked `forge-made` (design 47 G §151), a head moved outside
|
||||
the mesh is an untaken head (design 47 H §740), and the checker goes (corrected in place by design 47 H §763).
|
||||
54. **One reader of the seat list per part, and one view machinery.** Every part that reads the seat list has the two
|
||||
tools of ADR 0636 §7 from the runtime and no wiring of its own; every part that takes a first view answers its
|
||||
held and awaited revision in `<module>_first_views`. With the forge on its old build, serving no verb of the seat
|
||||
@@ -1865,9 +1891,9 @@ No module ends the milestone with more tests than it starts with, counted per ca
|
||||
|
||||
The failure paths:
|
||||
|
||||
81. **A group that never completes** raises `take-in-waits` at 30 minutes, and none of its members is delivered (whole,
|
||||
81. **A group that never completes** *(Retires at milestone H, design 47 H §764.)* raises `take-in-waits` at 30 minutes, and none of its members is delivered (whole,
|
||||
indexer and watchman).
|
||||
82. **An indexer whose manifest its validator refuses** leaves its revision pending, holds only its own watched branch,
|
||||
82. **An indexer whose manifest its validator refuses** *(Retires at milestone H, design 47 H §764.)* leaves its revision pending, holds only its own watched branch,
|
||||
raises `take-in-waits` at 60 minutes, a later merge on that branch waits behind it and is not taken in past it, and
|
||||
a revert taken in moves the branch on (whole, indexer).
|
||||
83. **A declined registration change, and an unprotected branch,** each write nothing: the first after its Decline, the
|
||||
@@ -1953,13 +1979,13 @@ ADR 0667's checks, of milestone G itself:
|
||||
package rebuilds it, started by the runner after its `outdated` ask, one that leaves its digest as it was rebuilds nothing, and a change of the Go build module's
|
||||
own code rebuilds no module; a `beta` build's entries compare by digest (whole, indexer, builder and runner,
|
||||
mesh-delivery).
|
||||
105. **One query finds what is behind** (design 47 G §375). With the runner stopped while mesh-sdk `0.1.16` is
|
||||
105. **One query finds what is behind** *(Retires at milestone H, design 47 H §764.)* (design 47 G §375). With the runner stopped while mesh-sdk `0.1.16` is
|
||||
released, `outdated` names the module's kind-1 edge at `0.1.15` against `0.1.16`, and at its restart the runner
|
||||
starts that module's pipeline once, keyed by mesh-sdk's source revision; `runner_catch_up` does it by hand and
|
||||
writes the hand-act log
|
||||
(whole, indexer and runner, mesh-delivery). After the first fill (§377), a mesh running its newest builds is
|
||||
answered with nothing behind.
|
||||
106. **A delivery is waited for mesh-wide** (design 47 G §376, §379, §380). A module ordered after a provider's
|
||||
106. **A delivery is waited for mesh-wide** *(Retires at milestone H, design 47 H §764.)* (design 47 G §376, §379, §380). A module ordered after a provider's
|
||||
new version is wanted only once `version-delivered` says every present machine placing the provider runs it; with
|
||||
one machine away the module's status reads "waiting for delivery of" the provider, naming the machine, and it
|
||||
catches up when that machine is back; with every placing machine away the provider reads "waiting for <machine>
|
||||
@@ -1993,9 +2019,37 @@ ADR 0667's checks, of milestone G itself:
|
||||
and Go build module, mesh-delivery and mesh-catalog). Live: each module's test steps run once per level, read with
|
||||
`runner_test_runs`. A reader no part ends raises `pipeline-stands` within five minutes of its last sign of life
|
||||
(whole, watchman; design 47 G §732).
|
||||
110. **One merge call is delivered end to end with no hand act** (design 47 H §734 to §738, §743, §746, §750). With
|
||||
`pipelines-at-once` at 1, a merge call naming one pull request that changes one module says one `merge-called`;
|
||||
the gate writes one source revision and opens one record; the indexer says one `take-in.taken` naming that module
|
||||
alone; the runner runs one pipeline; once it passes and the version is released, the module is wanted on every
|
||||
machine that places it, runs there, and the record ends (whole, forge module, gate, indexer, runner, assigner and
|
||||
node-engine, mesh-catalog, mesh-delivery and `mesh-host`). Live: the plan's section 5, step 7, read with the tools
|
||||
and quoted with its times.
|
||||
111. **A head moved outside the mesh delivers nothing and is said** (design 47 H §739 to §742). A merge made in the
|
||||
forge's screen gives one `head-moved`, no source revision and no pipeline; `head-untaken` is raised within
|
||||
`untaken-bound`, naming the repository, branch and head; a later merge call in that repository clears it; and
|
||||
`gate_head_take` delivers such a head by hand, written in the hand-act log (whole, forge bridge and gate,
|
||||
mesh-delivery and mesh-catalog).
|
||||
112. **Two repositories in one merge call are one pipeline, and pipelines run one at a time** (design 47 H §734,
|
||||
§735, §743, §746 to §748). A merge call naming a mesh-sdk change and a module that imports it, both on one watched
|
||||
branch, merges both or, with one member refused, neither; merged, it is one source revision, one `take-in.taken`
|
||||
naming mesh-sdk, that module and mesh-sdk's other importers, and one pipeline in which every importer builds after
|
||||
mesh-sdk's `package-published`; a second merge call made while it runs is said waiting and runs after its
|
||||
`pipeline-ended`, and a restart of the runner starts no pipeline of its own (whole, forge module, gate, indexer and
|
||||
runner).
|
||||
113. **A want is the newest released version whose pipeline passed** (design 47 H §750, §751). A module released with
|
||||
a passed pipeline is wanted on every placing machine at once, whatever build an acting part runs and whatever a
|
||||
dependency's delivery; a released version whose pipeline failed is not wanted; an older version's end heard after
|
||||
a newer one writes nothing; on one machine the bus module's and the backup holder's changed wants apply before the
|
||||
others and the node-engine's last (whole, assigner and node-engine, mesh-delivery and `mesh-host`).
|
||||
|
||||
## What retires
|
||||
|
||||
- From milestone H's delivery: everything design 47 H §764 lists (the per-pull-request paths of the gate and the forge
|
||||
bridge, the catch-up by comparison, the runner's sweep, the start-time `outdated`, the checker, the groups by branch
|
||||
name, the want holds A-478 ends), and the stale state H §765 drops once.
|
||||
|
||||
- The "release branches" and the controller's check of them (ADR 0358, superseded by ADR 0401).
|
||||
- The toolchain image and its module (ADR 0405).
|
||||
- The window cutter, the merge catch-up timer, the rollout ticker, mesh-delivery's tick, reconcile and
|
||||
@@ -2089,6 +2143,7 @@ release reports the controller's code lines against research 063's baseline (acc
|
||||
| L7 | History and records leave the controller (ADR 0571): the builder keeps its build log, one entry at a build's start and one at its end, from which build history and durations are read and the module mesh-catalog asks the builds it missed; the artifact sweep is the seat `mesh-artifact-sweep`, held by artifact-store-tools beside the artifact store, its keep set from the store's own listing, the wants and the build log, sweeping at each build's end from the lease write and recording each deletion in the hand-act log; disk readings are disk-load's own state on every node; who holds which seat is the state `seat-holders` of the seat `mesh-placement` (now `mesh-module-assigner`), and tools are found by the tool runners' announcements; what a node runs is its want and its have; the grants part writes `grants.<module>.<fingerprint>` and keeps memberships in its own state; root-free is a probe of the self-check; no manifest but the controller's reads, invokes or consumes `mesh-controller`, but a named list kept to the lease write, so the lease write's check passes (ADR 0189, ADR 0547 §11, ADR 0549 §6) | — | mesh-sdk, mesh-controller (its pin only), mesh-delivery (builder, indexer, assigner, grants part, view), mesh-catalog (artifact-store-tools, disk-load, the backup seat's holder, mounts, nfs-server, minio, mesh-watcher, the messenger, the self-check, the module mesh-catalog, docker), mesh-tools (the tool runner) | 1955 |
|
||||
| B0 | The bootstrap delivery: every check, a lone pull request's as a group of one and a verdict carried after a trunk move included, is judged by a checking program built from the change's own heads in the build seat's sandbox, which also makes the heads' one seat list that the check hands the manifest validator and the composer; it brings no seat definition and no manifest field, so the running checker checks it (ADR 0644; *The bootstrap delivery, and the one milestone after it*) | 26 needs it | mesh-sdk (`go/delivery`: the seat `node-build-go`'s ask `run` and the checker's record of which checking program judged; `go/composer`: the request's seat list), mesh-catalog (mesh-build-go: the run step, the refused answer, the kept programs' tools and sweep), mesh-delivery (checker: the checking program and its command), hq (this design, the glossary) | 1921 |
|
||||
| G | Two graphs and one revision view: the catalog graph and the assignment graph kept per revision, a change delivered as its graph difference, the acting parts' rules on their seats as bounded waits that hold their modules when the new version fails, the check on the change's own acting parts, the revision view and each process's own build, the gate's delivery record, and the trace's links (ADR 0656); no part reads a pull request's description (ADR 0659); every delivery part reaches the forge through the seat `git` and names no other module; nothing holds an approved merge for another check; and, one milestone with them, research 086's pipelines: a change of any module goes from a commit on a watched branch to the machines through its module's pipeline, its policy in its registration, ordered by edges between artifacts, with no Approve per merge and no hand act, the checker gone (ADR 0666, ADR 0667). Test counts at its start (G's prepare, 2026-11-09): mesh-delivery 665 unit and 68 integration, the node-engine (`mesh-host`) 1,742 unit; each other repository's and each catalog module's from the last check's verdict, read in the joint prepare | 26 to 62, 63 to 106 | mesh-sdk (the runtime: the fingerprint, the view, the definition reader, the seat list's one wiring), mesh-contracts and the domains' contracts modules (`acts`, the new verbs and events, the seat `mesh-grants`, the seat `git`'s verbs), mesh-delivery (indexer, assigner, checker until its removal, builder, grants part, gate's view, forge bridge, watchman, the new pipeline runner `mesh-delivery-pipeline`, `contracts` and `sdk` moved under `modules/`), mesh-catalog (the gate, the build modules, the forge module, mesh-issues, mesh-knowledge, the `node-backup` holder, the router, nats: a module's kept data on the bus as a backed-up item and the object store beside each state), mesh-sdk (also its small object store package, for values of any size), the node-engine (`mesh-host`), hq | 1966, 1961 (retargeted to this row's shape), 1660, 1972, 1721, 1783, 1785, 1794, 1791, 1373, 595; 1962 goes back with 1958, whose assignment entry it needs (ADR 0641 §3) |
|
||||
| H | The build-and-delivery system delivers itself by its one model, in six releases (H0 to H5, the plan's section 6): one merge call of the seat `git`'s `merge-pull` naming one or more pull requests is a delivery's start and its group; the gate names the merged heads one source revision and opens its record; the indexer takes it in (a commit, the fingerprints of its repositories' modules, one catalog revision) and names the movers; one pipeline per take-in, none in parallel (`pipelines-at-once`, default 1); a want is the newest released version whose pipeline passed; the forge's event is the watchdog (`head-untaken`); every delivery part wakes on its inputs alone and reads no other part's state; the per-pull-request paths, the catch-up by comparison, the sweep and the checker go; one clean state placed by hand once, after which every release is delivered by its own pipeline (ADR 0682, ADR 0681, ADR 0666, ADR 0667; design 47 H §734 to §765) | 110 to 113 | mesh-delivery, mesh-catalog, `mesh-host`, mesh-tools, mesh-sdk, mesh-contracts, hq | opened by each release's prepare |
|
||||
|
||||
An issue is in one row only (ADR 0493 §2): where a row named an issue another row names too, the last row keeps it and the
|
||||
earlier row says so in words (the operator, 2026-10-26). Milestone M1 makes each row a record of the issue tracker
|
||||
|
||||
@@ -84,9 +84,10 @@ check and deliver milestone G itself (ADR 0667 §2); each of them says so in a l
|
||||
what moved); the verb `registrations` answers every registration, or one with its history. The indexer derives the
|
||||
modules it keeps from them, and the forge bridge its watched branches, each by a first view of `registrations` and
|
||||
then that event, never by reading the ledger (ADR 0666 §3, ADR 0596).
|
||||
- §5 **An unprotected branch is refused.** `register` and `watch` read a branch's protection through the seat `git`'s read
|
||||
verb `branch` (its head, and whether a rule refuses a direct push and admits only merges), and refuse a watched branch
|
||||
the forge does not protect, naming it (ADR 0666 §3).
|
||||
- §5 **An unprotected branch is not refused at registration** (corrected in place by design 47 H §763). `register`
|
||||
and `watch` read no branch's protection and refuse no watched branch for it: the operator approved removing the
|
||||
check on 2026-11-14 (G-23, *Met during G's start*), which ADR 0666 §3 still states. `merge-pull` still judges the
|
||||
protection at every merge (ADR 0666 §11, §38), and §17's `branch-unprotected` stands.
|
||||
- §6 **The foundation parts are the manifest validator's list.** The manifest validator's list (ADR 0619 §3) holds
|
||||
exactly the foundation parts, ADR 0619 §1's, the runner, which joins them (ADR 0666 §4), and the forge and image
|
||||
registry modules (§584); the checker leaves the
|
||||
@@ -317,8 +318,10 @@ check and deliver milestone G itself (ADR 0667 §2); each of them says so in a l
|
||||
removed with the checker's buckets and bus account, after the first pipeline after G's delivery has delivered a change
|
||||
end to end and on the operator's word (ADR 0667 §12; *How milestone G itself is checked and delivered*); the forge bridge hears the landed commit as it hears every commit of a watched
|
||||
branch.
|
||||
- §40 **The operator-channel hides no ask.** It keeps design 46's three open asks per asker, never holds the newest back,
|
||||
and replaces an open ask by the same asker's ask with the same `about` (ADR 0666 §12; design 46 §6).
|
||||
- §40 **The operator-channel hides no ask.** It keeps no count of open asks per asker and holds none back: every ask
|
||||
is offered when it is raised (A-424, the operator, 2026-11-15 about 15:50 CET), and it replaces an open ask by the
|
||||
same asker's ask with the same `about` (ADR 0666 §12, whose three open asks per asker A-424 ends; design 46 §6;
|
||||
corrected in place by design 47 H §763).
|
||||
- §41 **How it is checked.** Whole (forge module, forge bridge): a session's `merge-pull` at its head merges with no run yet,
|
||||
and with a passed one, and asks no Approve; with the runner stopped a head merges; a head at whose fingerprint any
|
||||
run failed a `required` step, a head that moved and a branch whose protection was removed since its last move are
|
||||
|
||||
@@ -242,8 +242,9 @@ each the design's choice with its reason, §468 to §479 those of the runner's,
|
||||
whole (forge module), a head that passed, then another commit at its fingerprint failed a `required` step, is
|
||||
refused; its `seen` key goes when the pull request closes.
|
||||
- §476 **`take-in.taken`'s body and its type.** (§493) The indexer's own `take-in.taken` carries, beside what it carries on
|
||||
main, `branch` (the watched branch), `source` (the source revision taken in) and `entries`, one `{module, commit,
|
||||
fingerprint}` per module of that revision. Its body is defined in the seat `mesh-catalog`'s definition, in its
|
||||
main, `branch` (the watched branch), `source` (the source revision taken in) and `entries`, one
|
||||
`{module, commit, fingerprint, repository}` per mover of that take-in (design 47 H §743; corrected in place by H §763, where this line
|
||||
said one entry per module of the revision). Its body is defined in the seat `mesh-catalog`'s definition, in its
|
||||
section `bodies` (§439, §454), so the generated contract carries the type the indexer writes and the runner reads,
|
||||
and neither imports the other (§333). Why: a body said on a module's own stream and read by others is a `bodies`
|
||||
entry (§439), never a client's hand-written type (develop question Q-RN4). How it is checked: unit (seat generator),
|
||||
|
||||
@@ -389,9 +389,10 @@ for several build maps is answered once, and the maps' names for it are given in
|
||||
(G-24 §720, §725), and from its `ask-taken` by its step's bound (A-466p). [mesh-delivery DQ-3.] How it is checked:
|
||||
whole (runner), a seat with no holder ends the pipeline at once, naming it; an ask a present holder has not taken
|
||||
past five minutes is not failed (test 109).
|
||||
- §648 **A `take-in.taken` entry carries the pull request.** (§476, §542) An entry is `{module, commit, fingerprint,
|
||||
repository, pull}`, the last two from a `merged` message and absent for a `pushed` one. [mesh-delivery DQ-5.] How it
|
||||
is checked: unit (indexer's contract).
|
||||
- §648 **A `take-in.taken` entry names its repository, never a pull request.** (§476) An entry is `{module, commit,
|
||||
fingerprint, repository}`, the repository from the gate's `source-moved` (design 47 H §743); the field `pull` goes,
|
||||
since nothing reads a pull request after the merge call (ADR 0682 §1; corrected in place by H §763). [mesh-delivery
|
||||
DQ-5.] How it is checked: unit (indexer's contract).
|
||||
- §649 **`ParseStepKey` answers the asker.** (§484) `buildstep.ParseStepKey(key)` answers `(asker, node, id, err)`,
|
||||
`asker` empty for main's form. [mesh-delivery DQ-8.] How it is checked: unit, both forms.
|
||||
- §650 **The `mesh-builds` client's name.** (§586) It is `contracts/go/clients/meshbuildsclient`, with `Reserved`.
|
||||
@@ -408,9 +409,8 @@ for several build maps is answered once, and the maps' names for it are given in
|
||||
|
||||
- §654 **The readers of the forge module's old events and tools move to the seat `git`.** (§310, §311, §313, §431;
|
||||
ADR 0659 §1) [mesh-catalog Q-F1.]
|
||||
- **mesh-config** consumes `git`'s `pull-merged` and `pull-closed` in place of `gitea.pull.merged`,
|
||||
`gitea.pull.closed` and `gitea.forge.pull-request.closed`, and invokes `seat:git.pull` in place of
|
||||
`gitea.gitea_get_pull_request`; **the records module** consumes `git.pull-merged`.
|
||||
- **mesh-config** consumes no pull request event and invokes no `seat:git.pull` (ADR 0681 §1, which replaces this
|
||||
bullet's first form; corrected in place by design 47 H §763); **the records module** consumes `git.pull-merged`.
|
||||
- **The order.** Main's forge module says its own `pull.merged`, not the seat's events, so each consumer of
|
||||
`git.pull-merged` or `pull-closed` is ordered after the forge module's version that says them, by the edge of kind
|
||||
6 its `consumes` gives (§558); its durable consumer is made from the stream's first message, so no merge said
|
||||
|
||||
@@ -1275,14 +1275,15 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
never at the revision its own view holds; while its view holds an older one, it waits for it (§200) and places no step.
|
||||
(Live, 2026-11-16: main.947 was started at revision 356 while its take-in made 357; its composition read 356 after
|
||||
the indexer had removed it.)
|
||||
- **A-449** (§153, §579, design 47's "kept while a delivery record pins it or it is current"; principle 7) A pipeline
|
||||
pins its catalog graph revision as a delivery record does: the runner says the seat `mesh-delivery`'s `pinned` when it
|
||||
starts a pipeline and `freed` when the pipeline ends, under the record id `pipeline.<key>`, so the indexer keeps the
|
||||
revision while any pipeline runs on it. No new mechanism; who may say them is a grant of the runner's account.
|
||||
- **A-449** (§153, §579, design 47's "kept while a delivery record pins it or it is current"; principle 7; corrected in
|
||||
place by design 47 H §763, H §749) A pipeline pins its catalog graph revision: the indexer pins it in the take-in's
|
||||
write (A-449a) or on the runner's `pipeline-started`, and frees it on the runner's `pipeline-ended`, so the indexer
|
||||
keeps the revision while any pipeline runs on it. The runner says no `pinned` or `freed` of the seat
|
||||
`mesh-delivery`; those stay the gate's alone (§153).
|
||||
- **A-449a** (completes A-449; principles 3 and 7) The indexer pins the revision a take-in made for each pipeline the
|
||||
take-in starts, under `pipeline.<key>` (`<branch>.<source>.<module>` of each entry), in the same write as it keeps the
|
||||
revision, so no later take-in can remove it before the runner hears of it. The runner's pin at a pipeline's start stays
|
||||
(a set: saying it twice is harmless) and its `freed` at the pipeline's end removes it.
|
||||
take-in starts, under `pipeline.<key>` (`<branch>.<source>`, the one pipeline of the take-in, design 47 H §746), in the
|
||||
same write as it keeps the revision, so no later take-in can remove it before the runner hears of it. Its free is on
|
||||
the runner's `pipeline-ended` (A-449 as corrected).
|
||||
- **A-226b** (completes A-226 and A-167; ADR 0593 §7; principles 7 and 9) The seat `node-engine`'s `compose-candidate`
|
||||
takes three key forms, parsed by one parser in the seat's client (`nodeengineclient`) that every caller builds its key
|
||||
with: a check's candidate `<group>.<heads hash>` (as today), a branch pipeline's revision `<branch>.<revision>` and a
|
||||
@@ -1862,7 +1863,7 @@ the principle that settles it, cited as "design 47 G A-n".
|
||||
- **A-475a** (A-475; principles 7, 2 and 11) "In a row" is counted on the pending revision's validation itself
|
||||
(`stale`, the stale ends since its last ask that was not stale), the only place that needs it. The catch-up waits
|
||||
while a validation ask of any repository is out, since every take-in moves the one revision a request is built from;
|
||||
it still compares the heads and raises A-463's merge-untaken condition meanwhile, and only its take-in waits.
|
||||
it still compares the heads and raises A-463's `merge-untaken` condition meanwhile, and only its take-in waits.
|
||||
`validate-tries` defaults to 3 and is at most 20. (From the develop and review of A-475.)
|
||||
- **A-476** (the operator, 2026-11-17 ~17:30 CET, from the delivery walkthrough: "no manifest check needed at this
|
||||
point"; "for each module that is registered in our module graph, for the affected repo -> check the fingerprints";
|
||||
|
||||
@@ -103,7 +103,9 @@ record says so in its Why. Round 3 of the review by architectural domain (2026-1
|
||||
`*.findings-stated` are the first. The manifest validator takes `*` only as the whole emitter, and only before an
|
||||
event that a seat's definition or a contract in mesh-sdk defines, with its fields (for the finding events, the seat `mesh-conditions`' definition, §439); it refuses `*.>` and `*` in part of an emitter's name, and a `*` entry before any other event keeps its meaning on main (§474). The grants part,
|
||||
from the catalog graph as it derives every grant (§59, §442), makes on each declaring module's stream one durable consumer
|
||||
for the consumer, named `<machine>_<module>` as ADR 0363 §5 names one, with its grants to read and acknowledge it and
|
||||
for each process of the consumer that hears it, named as A-397 names a process's durable (`<machine>_<module>` for
|
||||
its program, `<machine>_<module>_tools` for its tool runner, `<machine>_<module>_<process>` for another; corrected in
|
||||
place by design 47 H §763, where one per module stood), with its grants to read and acknowledge it and
|
||||
its membership's word to bind it; it drops that consumer when the module no longer declares the event, and makes one
|
||||
for a module that declares it later, with no change to the consumer's manifest. A `*` entry never reaches a
|
||||
restricted stream (one with a `grant`, ADR 0363 §4). Why: the keeper hears modules it finds in the catalog and its
|
||||
|
||||
@@ -0,0 +1,242 @@
|
||||
---
|
||||
layer: to-be
|
||||
status: in-progress
|
||||
design: 47
|
||||
milestone: H
|
||||
updated: 2026-11-20
|
||||
decisions:
|
||||
- "ADR 0682"
|
||||
- "ADR 0681"
|
||||
- "ADR 0667"
|
||||
- "ADR 0666"
|
||||
- "ADR 0656"
|
||||
- "ADR 0633"
|
||||
- "ADR 0596"
|
||||
- "ADR 0573"
|
||||
---
|
||||
# 47, milestone H: the merge call, the watchdog, the take-in and one pipeline at a time
|
||||
|
||||
One file of milestone H's part of [design 47](../47-delivery-from-commit-to-delivered.md); the plan that opens the part
|
||||
is [H-deliver-the-delivery-system](H-deliver-the-delivery-system.md). Its design lines continue the numbering of
|
||||
milestone G's part after §733 and are cited as "design 47 H §n". Each line says which release of the plan's section 6
|
||||
builds it (H1 to H5), how it is checked, and which line of G or lead's answer it replaces; where the code it lands in
|
||||
is named, it is named by module and function, from the gap tables of 2026-11-20, for the builder to find it.
|
||||
|
||||
*The operator, 2026-11-19 about 23:30 CET: "Nobody should 'take in a merge', only commits to the configured branch of
|
||||
registered modules." 2026-11-20 about 01:10 CET: "parallel pipelines sounds like a very bad idea". 01:15 to 01:20 CET:
|
||||
a delivery is started by hand by the merge it already needs, the lead named principle 3 (a start a person forgets is
|
||||
a silent non-delivery), and the operator chose "A": the merge through the mesh is the start and the group, and the
|
||||
forge's event is the watchdog. ADR 0682 records it. The chain these lines build, in one sentence: a **merge call**
|
||||
(the seat `git`'s `merge-pull` naming one or more pull requests) merges the heads, the gate names them one source
|
||||
revision per watched branch and opens its delivery record, the indexer takes that revision in and names the movers,
|
||||
the runner runs one pipeline for it when no other runs, and the assigner wants the newest passed release; the forge
|
||||
bridge's one message per head move is heard only by the gate's watchdog, which raises an **untaken head** for a head
|
||||
no merge call delivered.*
|
||||
|
||||
```mermaid
|
||||
flowchart LR
|
||||
S[session or operator] -->|git.merge-pull pulls| F[forge module, seat git]
|
||||
F -->|merge-called| G[gate, seat mesh-delivery]
|
||||
G -->|source-moved| I[indexer, seat mesh-catalog]
|
||||
I -->|take-in.taken: movers| R[runner, seat mesh-pipeline-runner]
|
||||
R -->|pipeline-ended| A[assigner, seat mesh-wants]
|
||||
F -->|branch-moved| B[forge bridge]
|
||||
B -->|head-moved| G
|
||||
G -.->|head-untaken| K[condition keeper]
|
||||
```
|
||||
|
||||
### The merge call
|
||||
|
||||
- §734 **One merge call is a delivery's start and its group.** (ADR 0682 §1, ADR 0666 §11; the operator, 2026-11-20
|
||||
01:20 CET; principle 3) The seat `git`'s verb `merge-pull` takes `pulls`, a list of one or more members
|
||||
`{repository, number, head}` (the head the caller names, as ADR 0666 §11 has it), and `by`, the caller as who@node.
|
||||
The members named in one call are one delivery and, when there are two or more, its group; nothing else makes a group.
|
||||
The verb's single-pull form goes: a call naming one pull request is a list of one. Built in H1 in the forge module's
|
||||
`merge-pull` handler and the seat `git`'s contract in mesh-delivery-contracts. How it is checked: whole (forge
|
||||
module): a call naming two pull requests in two repositories merges both and says one `merge-called` (§736).
|
||||
Replaces G §38's one-pull form.
|
||||
- §735 **Every member is judged before any is merged.** (ADR 0666 §11; principle 3) The verb judges each member as
|
||||
ADR 0666 §11 does (still the pull request's head, a branch protection that refuses a direct push, read again; no run
|
||||
at the head's build-input fingerprint failed a `required` step, from the forge module's own `failed-steps`), all of
|
||||
them first. When one member is refused, none is merged, and the answer names every refused member and why. Then it
|
||||
merges the members in the order the call names them. Why this order: a group merged in part would land half a
|
||||
delivery (ADR 0666 §13's "none delivered if one fails", kept for the call's group). What the call says when the
|
||||
forge refuses a member after all were judged is question 1 of *Questions this file leaves open*. Built in H1 (forge
|
||||
module). How it is checked: whole (forge module): a call whose second member's head moved merges neither and names
|
||||
it.
|
||||
- §736 **The merge call says one event.** (ADR 0682 §1; principle 1) When every member is merged, the forge module says
|
||||
the seat `git`'s event `merge-called` on `mesh.seat.git.event.merge-called.<call>`, kept on the stream
|
||||
`SEAT_git_merge-called` for 30 days and up to 64 MiB, its body in the seat's `bodies`: `call` (an id the forge module
|
||||
makes once per call: 16 lowercase hex), `by`, `at` (the time of the last merge) and `members`, one
|
||||
`{repository, number, branch, head, commit}` per member, where `branch` is the pull request's base (a watched
|
||||
branch) and `commit` the merge commit the forge records for that pull request. Only the forge module says it. Its
|
||||
one consumer is the gate (§737), on a durable consumer of its program. Why 30 days: the gate takes in a call heard
|
||||
after a long stop, and the forge module's `seen` keys are kept as long (G §585). Built in H1 (forge module, seat
|
||||
`git`'s definition and contract). How it is checked: unit (the seat definition: the event and its body);
|
||||
whole (forge module) as §734.
|
||||
- §737 **The gate names the merged heads one source revision and opens the record.** (ADR 0682 §1; principles 1
|
||||
and 12) The gate consumes `merge-called`. For each watched branch its members name, it writes `source.<branch>` once,
|
||||
by compare-and-set: the branch's previous heads with each member's repository at its `commit`, numbered one above
|
||||
the branch's newest, carrying `call`. It opens one delivery record per such revision, keyed `<branch>.<source>`
|
||||
(A-33 stands), its members the call's members on that branch, `call` and `by` in its trace, and says `source-moved`
|
||||
with `branch`, `source`, `call`, `start` (false; true only for A-401's start pass of a newly watched branch, which
|
||||
stays) and `heads` (the repositories it moved, each `{repository, commit}`). A
|
||||
`merge-called` heard again writes nothing: its record's key exists. A call whose members name two branches is two
|
||||
source revisions and two records, each naming the same `call`. The gate numbers every source revision; no other part
|
||||
keeps a number of its own. Built in H1 in the gate: its `moveSource` moves from the `take-in.taken` handler to a
|
||||
`merge-called` handler; `ForgeMerged`, `moveHead` and the tool `gate_source_follow` go (§764). How it is checked:
|
||||
whole (gate): a `merge-called` with two members on one branch gives one revision, one record and one
|
||||
`source-moved`; the same event heard twice gives one. Replaces A-34 (the source moved on `take-in.taken`), G §291,
|
||||
A-431's numbering by the indexer, and A-464 to A-464e.
|
||||
- §738 **A delivery record follows its pipeline to the machines.** (ADR 0666 §9; G §141 to §147) The record opened by
|
||||
§737 is the record of G §141 to §147, one per source revision: it consumes the runner's `pipeline-started` and
|
||||
`pipeline-ended`, the parts' `wait-held` and `wait-ended`, and the node-engine seat's `running`, on the gate's own
|
||||
durable consumer, writes its trace (the assignment graph revisions it moved between, from the assigner's `wanted`),
|
||||
and ends as G §147 says. A take-in with no movers (§741) ends its record at once as `nothing to deliver`. Built in
|
||||
H3 in the gate's consumer (`stepFamilies`) and record (`SetTrace`, `EndIfRun`). How it is checked: whole (gate):
|
||||
a record of a one-module delivery ends when the module runs on every placing machine (acceptance test 110).
|
||||
|
||||
### The forge bridge's one message, and the watchdog
|
||||
|
||||
- §739 **The forge bridge says one message per move of a watched branch's head.** (ADR 0682 §2, ADR 0666 §6; G §11,
|
||||
A-236) On every `git.branch-moved` of a watched branch, and at its start for every watched branch's head, the bridge
|
||||
reads the head through `git.branch` (never the event's body) and writes one message `head-moved` on its stream
|
||||
`forge`, subject `forge.<repository>.<branch>.head-moved`: `repository`, `branch`, `head`, `before` (the head it held
|
||||
for that branch in its state `heads`, empty the first time) and `start` (true when said at its start). It writes it
|
||||
whether the head moved by a merge call, a merge in the forge's screen or an admitted push: it reads no pull request
|
||||
and no tree. A head equal to the one it holds writes nothing. An unprotected watched branch writes nothing and is
|
||||
said as `branch-unprotected` (G §17 stands). Its one consumer is the gate (§740). Built in H1 in the bridge; the
|
||||
messages `merged` and `pushed`, their `base`, their trees in its state `inputs`, and its call of `git.pull` for a
|
||||
merged commit go (§764). How it is checked: whole (bridge): a merge, an admitted push and a restart each give one
|
||||
`head-moved`; a head heard twice gives one. Replaces G §509 and §714's message form; this is item 6 of the plan's
|
||||
section 4.
|
||||
- §740 **A head no merge call delivered is an untaken head.** (ADR 0682 §2; principles 1 and 3) The gate consumes
|
||||
`head-moved` and keeps, in its template state `heads` (one key `<repository>.<branch>`, value `{head, since}`, the
|
||||
key deleted by the gate when `source.<branch>` names that head), each head that `source.<branch>` does not name for
|
||||
that repository. When `untaken-bound` (a setting of the gate, default 10 minutes, at least 1) passes and
|
||||
`source.<branch>` still does not name that head, the gate raises the finding `head-untaken`, scope `delivery`, id
|
||||
`<repository>.<branch>`, naming the repository, the branch, the head, since when, and "moved outside the mesh:
|
||||
delivered by nothing". It clears it when `source.<branch>` names that repository at the newest head `head-moved`
|
||||
said (a later merge call delivers it). The gate keeps one deadline timer, set to the earliest `since` plus the bound,
|
||||
and no other clock. Built in H1 in the gate. How it is checked: whole (gate, bridge): a head moved by a merge call
|
||||
raises nothing; a head pushed outside the mesh raises `head-untaken` within the bound, starts no pipeline, and
|
||||
clears when a later merge call takes its repository in (acceptance test 111). Replaces A-463's `merge-untaken` and
|
||||
the head half of G §12 (§741 keeps its step half).
|
||||
- §741 **`pipeline-stands` times a pipeline's steps, not a head.** (ADR 0666 §24; principle 7) The watchman's finding
|
||||
`pipeline-stands` (G §12, §75) is raised for a pipeline step standing still five minutes; a watched branch's head
|
||||
that starts no pipeline is the gate's `head-untaken` (§740) alone, so the watchman learns no head. A pipeline waiting
|
||||
its turn (§746) is progress not owed and raises neither. Built in H1 in the watchman's `takein` and `signals` parts.
|
||||
How it is checked: whole (watchman): a pipeline waiting behind another raises nothing. Answers question 6 of
|
||||
specification A.
|
||||
- §742 **Taking an untaken head in by hand.** (ADR 0682 §2; principle 4) The gate's tool `gate_heads` reads the state
|
||||
`heads` with each head's since and finding; `gate_head_take`, with `repository`, `branch` and `why`, names that head
|
||||
a source revision as §737 does, its `call` `hand.<by>.<time>`, written in the hand-act log, and the chain follows.
|
||||
Nothing else delivers an untaken head. Why: a merge in the forge's screen leaves a head the mesh holds no record
|
||||
of; the operator may want it delivered without a new pull request (principle 4, recover without help). Built in H1
|
||||
(gate tools). How it is checked: unit (gate tools); whole (gate): a hand take writes one revision and clears the
|
||||
finding.
|
||||
|
||||
### The take-in
|
||||
|
||||
- §743 **The indexer takes in what the gate names.** (ADR 0682 §3; A-476, A-476a; principles 7 and 10) The indexer
|
||||
consumes the gate's `source-moved`, on its own durable consumer, one message at a time, acknowledged once its catalog
|
||||
revision and `take-in.taken` are written. For each repository the event moves it reads the trees at the named commit
|
||||
through `git.trees` (one of its kept calls, A-190), computes the build-input fingerprints of the modules registered
|
||||
for that repository (a registration's git origin), and takes as **movers** those whose fingerprint differs from
|
||||
their entry in the branch's newest catalog revision, and every module, in any repository, that imports a package of
|
||||
one of them (its code dependents, A-476a; ADR 0573 §3). It writes one catalog revision of that branch, pins it for the
|
||||
pipeline of §745 in the same write (A-449a, key `pipeline.<branch>.<source>`), and says `take-in.taken` once, with
|
||||
`branch`, `source`, `revision`, `call` and `entries`, one `{module, commit, fingerprint, repository}` per mover (§763
|
||||
corrects G §476 and §648: no `pull`). It validates no manifest and holds nothing for the indexer a revision names;
|
||||
it takes in with the build it runs (A-476 (a), (b)). A `source-moved` with no mover says `take-in.taken` with no
|
||||
entries. A branch's first source revision (the gate's start pass for a newly watched branch, A-401 and A-403,
|
||||
said as `source-moved` with `start` true) is taken in with no mover: its entries are the base the branch's later
|
||||
take-ins are held against, and nothing of it is delivered, since every module is already wanted by its newest passed
|
||||
release (§750). Built in H1: the indexer's take-in part written again (today `Arrive`, `evaluate`, `takeInWhole`,
|
||||
`takenWhat`, `nextSource` and `ApplyBranchSource`, fed by the bridge's messages); its storage, entries, pins'
|
||||
state, versions and verbs (`KeepView`, `keepBranchEntries`) stay. How it is checked: whole (indexer): a
|
||||
`source-moved` naming a mesh-sdk commit names mesh-sdk and its importers; one changing only a document names no
|
||||
mover; a restart between the revision's write and the event's acknowledgement writes no second revision (the
|
||||
revision is keyed `<branch>.<source>` by compare-and-set). Replaces G §16, §19, §509, §712 to §715 and the main
|
||||
file's *Taken in by the indexer it names* (§764).
|
||||
- §744 **A take-in that cannot be written waits, said and bounded.** (ADR 0633 §5's revision bound, kept for what
|
||||
still waits; principle 3) A take-in that cannot be written (the catalog store `full`, G §181; `git.trees`
|
||||
unanswered) leaves its `source-moved` unacknowledged, so the bus delivers it again, says `take-in.pending` with
|
||||
`branch`, `source` and `why`, and the watchman raises `take-in-waits` when no `take-in.taken` for that source follows
|
||||
within 60 minutes (G §497). Take-ins of one branch go in source order, since the consumer delivers one at a time.
|
||||
The state `pending`, its keys `m.<sequence>` and `g.<group>`, and `indexer_take_in_pending` and
|
||||
`indexer_drop_pending` go (§764); `indexer_pending` reads the one waiting `source-moved` and why. Built in H1
|
||||
(indexer). How it is checked: whole (indexer): with the store full a `source-moved` waits, is said, and is taken in
|
||||
on `room`.
|
||||
- §745 **Manifest validation is the pipeline step `validate`.** (ADR 0682 §4; A-476 (a); ADR 0666 §17) The step
|
||||
`validate` is served by the assigner on the seat `mesh-module-assigner`, as an accepted kind `step` on that seat's
|
||||
work queue, asked by the runner for each mover as the step before its composition step: the assigner runs the manifest validator built from the take-in's own heads,
|
||||
in the sandbox, as it runs the composer (G §718), over the revision's manifests, refusing only a problem in a
|
||||
manifest the revision alters or one between manifests an altered one takes part in (ADR 0578 §2). It ends `failed`
|
||||
with the reason `manifest-refused` naming each problem, or `cycle` naming the cycle the revision makes (the cycle
|
||||
refusal A-326 and G §569 made at the take-in), and `passed` otherwise. Its status is `required` in every policy by
|
||||
default: the seed (A-441) writes it, and §22's list of steps gains it. The indexer's events `manifest-refused` and
|
||||
`manifest-accepted` (G §500, §668) go; their readers read the step's end. Built in H1 (assigner: the step; runner:
|
||||
the order; indexer: the seed's default). How it is checked: whole (assigner, runner): a take-in whose manifest names
|
||||
an unknown field fails `validate` and asks no composition; a take-in that validates no manifest at the indexer is
|
||||
shown by the indexer's manifest declaring no validator run. G §22 serves the composition step itself on the seat
|
||||
`mesh-wants` (question 2 below).
|
||||
|
||||
### One take-in, one pipeline, none in parallel
|
||||
|
||||
- §746 **One take-in is one pipeline.** (ADR 0682 §5; the operator, 2026-11-20 01:10 CET; ADR 0666 §1, §7, §9 read per
|
||||
source revision) On a `take-in.taken` with entries the runner starts exactly one pipeline, keyed `<branch>.<source>`
|
||||
by compare-and-set on its absence, whose movers are the event's entries. It asks each mover's pipeline steps in the
|
||||
catalog graph's build order (a mover's build waits for the `package-published` of each mover it has a "published
|
||||
before it builds" edge to, toolchain edges first), and its end lists the movers in ADR 0666 §14's delivery order. The
|
||||
pipeline passes when every mover's `required` steps passed, and fails when one did not; `pipeline-ended` is said
|
||||
once, keyed by the source revision, with every mover's step results and the pipeline's outcome. A single commit is
|
||||
the case of one take-in. The runner says no `group-ended`: every pipeline is per source revision. How the order of
|
||||
delivery is kept once wants are written is question 3 below. Built in H1 in the runner: the pipeline key
|
||||
`<branch>.<source>.<module>` becomes `<branch>.<source>`, its step keys gain the mover. How it is checked: whole
|
||||
(runner): a take-in naming mesh-sdk and one importer is one pipeline whose importer builds after mesh-sdk's
|
||||
`package-published`, and one `pipeline-ended` (acceptance test 112). Replaces G §44's pipeline per watched branch
|
||||
of a group and G §332's `group-ended`.
|
||||
- §747 **A start names an event, never a sweep or a comparison.** (ADR 0682 §5; G §12, §112; principle 1) The runner
|
||||
starts a pipeline on `take-in.taken` with entries, and on `package-published` only when no pipeline of the
|
||||
publishing source revision runs (a publish again of an older build, G §588): that pipeline is keyed
|
||||
`<branch>.published.<package>.<version>` and its movers are the package's kind-1 dependents. A publish from a
|
||||
running pipeline starts nothing; that pipeline's dependents wait for it as §746 says. A hand `start`, `run` and the
|
||||
set-aside keys of A-446 stay. The sweep (`StartUnstarted`, `Unstarted`, `StartHeld` of the held pull request
|
||||
mesh-delivery #262), the start-time `outdated` of G §375 and `runner_catch_up` go: the runner's durable consumer of
|
||||
`package-published` delivers a publish heard after a stop. Built in H1 (runner: `Starter`, `run`'s `resume`). How
|
||||
it is checked: whole (runner): a restart with modules whose fingerprint has no pipeline starts none; a publish heard
|
||||
after a stop starts its dependents once.
|
||||
- §748 **At most `pipelines-at-once` pipelines run.** (ADR 0682 §6; the operator, 2026-11-20 01:10 CET; principle
|
||||
11) The runner's setting `pipelines-at-once` (a config key of its module, default 1, from 1 to 8) bounds the
|
||||
pipelines whose steps are asked at once. A pipeline started over the bound is written with no step asked, state
|
||||
`waiting`, and says `wait-held` with `step` `pipeline` and `on` `pipelines-at-once`; the runner places the waiting
|
||||
pipelines oldest first, by the sequence of the event that started them, each on its own `pipeline-ended` of a running
|
||||
one, with no timer, and says `wait-ended`. A waiting pipeline is progress not owed (§741). A newer pipeline never
|
||||
replaces a waiting one; a mover's running steps are superseded only as G §31 says. The runner's tool `runner_waiting`
|
||||
lists the waiting pipelines in their order; `runner_place`, with a pipeline's key and `why`, places one ahead of its
|
||||
turn, written in the hand-act log. Built in H1 (runner). How it is checked: whole (runner): two take-ins in a row
|
||||
run one after the other, the second said waiting, with `pipelines-at-once` at 1 (acceptance test 112). This is the
|
||||
bound specification C found missing.
|
||||
- §749 **A pipeline's pins are the indexer's, freed on its end.** (ADR 0666 §9; A-449a; principle 12) The indexer pins
|
||||
a take-in's revision in the take-in's write (§743), and a pipeline §747 starts on its `pipeline-started`, which
|
||||
carries `revision`; it frees the pin on that pipeline's `pipeline-ended`, both heard on durable consumers of its own.
|
||||
At its start it judges each kept revision against the pins its own state holds, never against a count of pins
|
||||
stated. The runner says no `pinned` or `freed`; §153's rule that only the gate's account says them stands. Built in
|
||||
H1 (indexer: `pins.go`'s `JudgePins`; runner). How it is checked: whole (indexer): a restart while a pipeline runs
|
||||
on revision 510 keeps 510. Corrects A-449 (§763).
|
||||
|
||||
### Questions this file leaves open
|
||||
|
||||
1. **A member the forge refuses after every member was judged** (a conflict appearing between the judging and the
|
||||
merge, or the forge down mid-call). ADR 0682 makes the call the group; it does not say whether the landed members
|
||||
are delivered. Recommendation: the call says `merge-called` with the landed members and a field `refused` naming
|
||||
the rest, the gate takes the landed members in, and the forge module raises `merge-partial` naming the call, since
|
||||
a landed head that is not delivered would raise `head-untaken` anyway.
|
||||
2. **The seat of the composition step.** ADR 0682 §4 serves `validate` on `mesh-module-assigner` "as the step before
|
||||
its composition step", while G §22 serves the composition step on `mesh-wants`. Recommendation: both steps on one
|
||||
seat; which one is a seat-definition choice for the lead (principle 9).
|
||||
3. **How the delivery order of §746 is kept** when A-478 ends every want hold for another module's delivery.
|
||||
Recommendation: the assigner writes every mover's want at once, and each node-engine applies the wants of one
|
||||
pipeline in the order `pipeline-ended` lists them (the one-machine order of A-478b, §751); nothing orders across
|
||||
machines.
|
||||
@@ -0,0 +1,163 @@
|
||||
---
|
||||
layer: to-be
|
||||
status: in-progress
|
||||
design: 47
|
||||
milestone: H
|
||||
updated: 2026-11-20
|
||||
decisions:
|
||||
- "ADR 0682"
|
||||
- "ADR 0666"
|
||||
- "ADR 0656"
|
||||
- "ADR 0596"
|
||||
- "ADR 0595"
|
||||
- "ADR 0573"
|
||||
- "ADR 0548"
|
||||
- "ADR 0525"
|
||||
---
|
||||
# 47, milestone H: the want rule, the builder's lines, the reads of other parts and the missing read tools
|
||||
|
||||
One file of milestone H's part of [design 47](../47-delivery-from-commit-to-delivered.md); the part opens at
|
||||
[H-deliver-the-delivery-system](H-deliver-the-delivery-system.md), and its lines are numbered after
|
||||
[H-1](H-1-the-merge-call-and-the-take-in.md)'s and cited as "design 47 H §n". These are items 8 and 11 to 13 of the
|
||||
plan's section 4, and A-434 as a line. The wake-up rule (item 9) is one rule for every delivery part and is in the
|
||||
main file, *Every delivery part wakes on its inputs alone*; §762 here says which part moves onto it where.
|
||||
|
||||
### The want rule
|
||||
|
||||
- §750 **A want names the newest released version whose pipeline passed.** (ADR 0682 §7; A-478; the operator,
|
||||
2026-11-17 about 21:45 CET; principles 2 and 7) For every machine whose assignment places module M on watched branch
|
||||
B, the assigner writes `want.<node>.<M>` naming `version`, the highest version of M released on B (`version-released`)
|
||||
whose pipeline's `pipeline-ended` passed; it writes it on either event, by compare-and-set on a newer version, so an
|
||||
older end heard later writes nothing (G §352's state `written` keeps, per module and branch, the newest passed
|
||||
version). A want names a version, never a part's digest (A-430): A-436's stand-in ends, and G §379's digests go. The
|
||||
want is held for nothing else. These holds end, with their states, findings and tools: the canary and the "at most
|
||||
`step` ahead" rule, every provider healthy, the grant exists, the served verb, the bus state (rule 8), the acting
|
||||
part's new version first (G §266, §268, §269, §274, §276: `acting-part-late`, `assigner_waits`'s acting rows,
|
||||
`assigner_release`), the dependency's `version-delivered` (G §376, A-189, A-246, A-250: `delivery-waits`,
|
||||
`assigner_delivered_again`, the event `version-delivered` itself, read by nothing else), and the parts check (G §524,
|
||||
the `want-parts` capability). The backup before the apply, the operator's yes on a failed backup and on a held revert
|
||||
are the node-engine's and the asker's (A-478 (c); G §296, §710), never a hold of the want. Built in H1: the
|
||||
assigner's want rule (`wants.go` and the want half of its pass) written again; the old holds deleted. How it is
|
||||
checked: whole (assigner): a module released with a passed pipeline is wanted on every placing machine at once,
|
||||
whatever build an acting part runs and whatever a dependency's delivery; a version whose pipeline failed is not
|
||||
wanted; an older version's end heard after a newer one writes nothing (acceptance test 113). Replaces G §29's
|
||||
per-revision want, §291, §292 in their want half, and design 47's six rules in *Where it goes*.
|
||||
- §751 **The order on one machine is the node-engine's apply order.** (ADR 0682 §7; A-478b; principles 2 and 7) The
|
||||
assigner writes a machine's changed wants at once. The node-engine, which applies its wants one module at a time
|
||||
(R6), takes the changed ones in this order: the holder of the seat `node-backup` and the bus module first, then the
|
||||
movers of one pipeline in the order its `pipeline-ended` lists them, then the rest by name, its own want last; at a
|
||||
revert, the module whose take-in is reverted first. The assigner's order waits (`order.<node>.<module>.<part>` in
|
||||
its state `waits`, step `placing`, G §298, A-245, A-258 to A-260) go. Why the node-engine: an order that holds a
|
||||
want is the hold A-478 ends, and the node-engine is the one part that applies (principle 12). Built in H1 (node-engine
|
||||
apply pass; assigner). How it is checked: whole (node-engine): wants of the bus module, the backup holder and two
|
||||
movers changed at once are applied in that order.
|
||||
|
||||
### Accounts
|
||||
|
||||
- §752 **Every account may call every verb.** (ADR 0682 §8; A-434; principle 6) Until a record on the mesh's
|
||||
accounts says otherwise, the grants part grants every module's account every verb and every event; no seat
|
||||
definition names callers, and the `callers` lists of every seat contract go (G §610's class defaults are not built).
|
||||
Acceptance tests 40, 51 (its callers row) and 85 are not checked while this holds. Built in H1 (seat contracts in
|
||||
mesh-contracts and mesh-delivery-contracts; grants part). How it is checked: unit (seat definition reader: a
|
||||
definition naming callers is refused); whole (grants part): a module calls a verb its manifest does not invoke and
|
||||
is answered.
|
||||
|
||||
### Builds and the builder
|
||||
|
||||
- §753 **A build module takes deliveries first.** (ADR 0525 §4; G §86) Each build module pulls its delivery queue
|
||||
first, then its check queue, then its recheck queue, taking from a later queue only while the earlier is empty, and
|
||||
waits on the bus's pull with no idle re-pull: the five-second idle pull of the shared step runner in
|
||||
mesh-delivery-sdk goes. The turns the code takes today cite an operator's yes of 2026-11-15 that no record holds
|
||||
(asked of the knowledge base on 2026-11-20): ADR 0525 §4 is in force, so the line follows it. Built in H2
|
||||
(mesh-delivery-sdk's step runner, `buildrun`). How it is checked: whole (Go build module): with three queues full
|
||||
the delivery asks run first.
|
||||
- §754 **A done build with no reservation is reserved by the builder itself.** (G §369, A-455; principle 3) When the
|
||||
runner's build step asks a fingerprint whose build is done and carries no reserved version (a build made before
|
||||
reservations, or one whose reservation was lost), the builder reserves the next version for it at that ask, as
|
||||
`builder_reserve_done` does by hand, says it in its journal and in the step's end, and answers the step carried.
|
||||
Nothing else reserves an old build: the builder looks for none by itself. Built in H2 (builder: its reserver and the
|
||||
look that writes "done build no version reserved"). How it is checked: whole (builder): a build step for a done,
|
||||
unreserved fingerprint ends carried with a version.
|
||||
- §755 **A failed fingerprint built again keeps its reservation.** (G §369, A-490b; principle 7) When a key is built
|
||||
again (by a step ask, an event or `builder_build_again`), the reserver takes that key's own standing reservation as
|
||||
its number; a key with none takes one above the higher of the highest released and the highest any other key
|
||||
reserved. No number is skipped. Built in H2 (builder's reserver). How it is checked: unit (reserver): a failed
|
||||
0.1.19 built again is 0.1.19.
|
||||
- §756 **A build is entered only by the runner's build step.** (G §473, A-97) The builder builds only what a pipeline's
|
||||
build step asks: it builds no catalog entry it hears and follows no gate `source`; the pre-G numbering beside the
|
||||
reservations (design 51's, replaced) goes, with its floor wait. `build.ended` carries the reserved `version`
|
||||
(A-430b), for every watched branch. Built in H2 (builder). How it is checked: whole (builder): a catalog entry heard
|
||||
with no step ask builds nothing; `build.ended` names its version.
|
||||
- §757 **The steps a mover can run are asked at every pipeline.** (ADR 0666 §7; G §8, §22) At each pipeline's start the
|
||||
runner asks each build seat's `steps` for each mover's artifacts, never only at the seed; a step the answer says
|
||||
has nothing to do ends `nothing to run`. Whether a `required` step ending so holds the delivery is question 1
|
||||
below. Built in H2 (runner). How it is checked: whole (runner): a library module whose unit tests vanish ends that
|
||||
step `nothing to run` at its next pipeline.
|
||||
- §758 **A registration whose pipeline would have no step is refused.** (ADR 0666 §2; acceptance test 67) `register`
|
||||
and `policy` refuse a registration whose policy, read against the build seats' `steps` for its artifacts, leaves no
|
||||
step that runs, naming each artifact and step. A package module with no registration has no pipeline and is never
|
||||
built; the seed (A-441) registers every package module the graph holds, `mesh-delivery-sdk` among them. Built in H2
|
||||
(indexer: `register`, `policy`, the seed). How it is checked: whole (indexer): a registration with every step
|
||||
`bypass` is refused naming them.
|
||||
|
||||
### Reads of another part's data become its events and verbs
|
||||
|
||||
- §759 **The status view, the watchman and the grants part read no other part's bus state.** (ADR 0596 §2, §4;
|
||||
principles 1 and 9) Each read of another module's bucket becomes the owner's event, and for a first view the
|
||||
owner's seat verb:
|
||||
- **the status view's twelve bucket watches**, each retried every five seconds: the node-engine's `have` becomes the
|
||||
seat `node-engine`'s event `running`; the watchman's `presence` and `stuck` become the seat `mesh-watchdogs`'
|
||||
verbs `presence` and `stuck` and the findings it says (`*.finding-written`, `*.finding-cleared`, G §386's form);
|
||||
the builder's `builds` becomes the seat `mesh-builds`' `build.ended`; the indexer's `taken` becomes
|
||||
`take-in.taken`; the indexer's `candidates` and the teller's `answers` go with their uses (G §512). Built in H4.
|
||||
- **the watchman's** read of the provisioner's `provisions` and its watch of the grants part's bucket. Built in H4.
|
||||
- **the grants part's** reads of the node-engine's `have`, the vault's `bus-accounts` and `node-logins`, the
|
||||
enrolment module's `enrolments` and mesh-config's `resolved`, and its calls of the bus module by module name,
|
||||
which become the seat `mesh-broker`'s verbs. Built in H4b.
|
||||
A read whose owner says no event for it today stops that subtask as a design question for the lead (question 2
|
||||
below lists the ones known). How it is checked: unit (each manifest declares no `reads` of another module); whole
|
||||
(view, watchman, grants part) against the owners' events.
|
||||
- §760 **Rates on the bus are read on the seat `mesh-broker`.** (ADR 0595 §5; principle 4) The seat `mesh-broker`
|
||||
gains the read verb `rates`, with `window` (seconds, default 10, from 1 to 60): it reads the bus server's counters of
|
||||
each connection and each stream twice, `window` apart, within the call, and answers per connection (its account's
|
||||
module and node) and per stream the messages and bytes in and out per second, and the slow consumers counted, its
|
||||
call bounded at `window` plus 5 seconds. Built in H4 (seat definition in mesh-contracts; the bus module). How it is
|
||||
checked: whole (bus module): a fixture publishing 100 messages a second reads about 100.
|
||||
|
||||
### The read tools found missing
|
||||
|
||||
- §761 **One revision, narrowed, and its differences, in the indexer.** (ADR 0666 §25; principle 4; one-question-one-tool)
|
||||
The indexer gains the tools `indexer_revision` (`branch`, `revision`, optional `module` and `kind`: one catalog
|
||||
revision of any watched branch, narrowed to a module's entries and edges or to one edge kind), `indexer_difference`
|
||||
(`branch`, `from`, `to`: the modules and edges that differ), `indexer_build_order` (`branch`, `modules`: the order
|
||||
the catalog graph's build edges give, its cycles named) and `indexer_built_from` (`fingerprint`: the source revision
|
||||
and commit it was taken in at); `indexer_edges` (G §380) gains `kind`. The assigner gains `assigner_delivery_order`
|
||||
(`node`, optional `modules`: the order §751 applies on that machine), and the node-engine `engine_build` (its own
|
||||
fingerprint, version and commit). An answer over the bus's per-message limit is an object's name (ADR 0666 §16).
|
||||
The callers of tools no part serves go with their callers: the checker's of `indexer_read_candidates` (it goes,
|
||||
§764), and the health checks' and the first views' of `indexer_read_modules`. Built in H4. How it is checked: unit
|
||||
(each tool's answer); the principle-4 table of each module's pull request.
|
||||
- §762 **Every delivery part moves onto the wake-up shape.** (ADR 0682 §9; main file, *Every delivery part wakes on
|
||||
its inputs alone*) The parts and what goes, from the gap table of 2026-11-20 (part F, question 2): mesh-config's
|
||||
key-by-key pass, five-minute sweep and minute's read (`sources`, the held pull request mesh-catalog #708, H1); the
|
||||
grants part's whole recompose (`Compose`, H4b); the indexer's re-read of every module, graph key and manifest after
|
||||
each write (`KeepView`, `viewEntries`, `heldModules`, H4); the builder's start sweep and `builder_stuck`'s read of
|
||||
every key (`Sweep`, the stuck read: it answers from the builder's own index of what builds, H4); the assigner's input
|
||||
sweep and its ten-second poll of `backed-up` (`inputKeeper.sweep`, `snapshotTheBus`, H4); the watchman's
|
||||
five-minute recount of dead letters (H4); the build modules' stale round and idle pull (`EndStaleRound`, §753, H2);
|
||||
mesh-sdk's first view asked again with a backoff (`views` reader, H4); the view's five-second retries (§759, H4); the
|
||||
forge module's one-minute poll and ten-minute timer (H3). The decided pulses (G §496's minute of `step-progress`,
|
||||
G §606) are real deadlines and stay. How it is checked: as the main file's rule says.
|
||||
|
||||
### Questions this file leaves open
|
||||
|
||||
1. **A `required` step ending `nothing to run`.** ADR 0666 §9 lets a want follow only a revision whose `required` steps
|
||||
passed, and G §22 says `nothing to run` is never passed, so such a module is held for good (specification D,
|
||||
question 3). Recommendation: a `required` step that ends `nothing to run` holds nothing in that pipeline, as the
|
||||
seed's `bypass` does, since it ran everything the module has; it needs a clause, since ADR 0666 §9 says "passed".
|
||||
2. **Reads whose owner says no event today**: the watchman's of the provisioner's `provisions`, the grants part's of
|
||||
the vault's `bus-accounts` and `node-logins` and of the enrolment module's `enrolments`, and the agent's watch of
|
||||
the grants part's `user-list` (ADR 0547 §7, §9). Recommendation: each owner says a change event of its own (the
|
||||
provisioner `provision-changed`, the vault `account-changed`, the enrolment module `enrolled`, the grants part
|
||||
`user-list-changed`) and answers its first view by a read verb; these are four records' clauses (ADR 0547 §7, §9 are
|
||||
in force), not lines this file can write.
|
||||
@@ -0,0 +1,84 @@
|
||||
---
|
||||
layer: to-be
|
||||
status: in-progress
|
||||
design: 47
|
||||
milestone: H
|
||||
updated: 2026-11-20
|
||||
decisions:
|
||||
- "ADR 0682"
|
||||
- "ADR 0681"
|
||||
- "ADR 0667"
|
||||
- "ADR 0666"
|
||||
- "ADR 0633"
|
||||
- "ADR 0548"
|
||||
---
|
||||
# 47, milestone H: the corrections made in place, the stale state, and what retires
|
||||
|
||||
One file of milestone H's part of [design 47](../47-delivery-from-commit-to-delivered.md); the part opens at
|
||||
[H-deliver-the-delivery-system](H-deliver-the-delivery-system.md), and its lines follow
|
||||
[H-2](H-2-wants-builds-reads-and-tools.md)'s, cited as "design 47 H §n".
|
||||
|
||||
- §763 **The small contradictions are corrected in place.** (plan item 10; each line names its source) These lines of
|
||||
milestone G and the main file now say what holds, each marked "corrected in place by design 47 H §763":
|
||||
- G §5: `register` and `watch` refuse no unprotected branch (the operator, 2026-11-14, G-23 *Met during G's start*).
|
||||
ADR 0666 §3 still states the refusal: a clause owed, named in the report of this amendment.
|
||||
- G §654: mesh-config consumes no pull request event and calls no `git.pull` (ADR 0681 §1).
|
||||
- A-449 and A-449a: the runner says no `pinned` or `freed`; the indexer pins and frees a pipeline's revision (§749).
|
||||
- Acceptance test 53: its `forge-made` and checker rows go (G §151; §740; the checker goes).
|
||||
- G §476 and §648: `take-in.taken` carries one entry per mover, `{module, commit, fingerprint, repository}`, no
|
||||
`pull` (§743).
|
||||
- G §40: the operator channel keeps no count of open asks per asker (A-424, the operator, 2026-11-15). ADR 0666 §12
|
||||
still says three: a clause owed, named in the report.
|
||||
- G §386: the grants part makes one durable consumer per process that hears a `*` event, named as A-397 names it.
|
||||
How it is checked: hq's review of this amendment reads each corrected line against its source.
|
||||
- §764 **What retires at milestone H's delivery.** (ADR 0682 §1, §2, §3, §5, §7; ADR 0681; ADR 0667 §12) Each
|
||||
is removed in the release named, with its code, its state (dropped by §765 where it holds keys), its tools, its
|
||||
events in the seat definitions, and its tests; nothing of it is kept unread.
|
||||
- **The forge module (H1, H3):** the single-pull form of `merge-pull` (§734); the merge-check machinery: the
|
||||
`mesh/merge-gate` pending statuses, the weighing of trunk and sibling moves (`announceHead`, `passPulls`,
|
||||
`trunksMoved`, `siblingMoves`, `GateWriter`) and its files on disk, its one-minute poll and ten-minute timer (H3).
|
||||
- **The forge bridge (H1):** the messages `merged` and `pushed` and their `base` (§739); its state `inputs` and its
|
||||
read of trees; its call of `git.pull` for a merged commit; the group it sets on a member, `forge.group.merged`,
|
||||
`bridge_groups` and `bridge_group_end_again` (G §43, §45, §157, §715); its hearing of the checker's `owed` and the
|
||||
merge act of a switched key (`OwedActMerge`, its `invokes` of `seat:git.merge-pull`, G §510).
|
||||
- **The gate (H1, H3):** the source per merged message (A-464 to A-464e: `ForgeMerged`, `moveHead`,
|
||||
`gate_source_follow`, the start's comparison with the forge's heads) and its consumption of the bridge's `merged`
|
||||
(G §592's rule now holds); the source moved on `take-in.taken` (A-34; §737); the groups from a branch name (G §42,
|
||||
§716, A-279): its states `deliveries` and `groups`, its consumption of `pull-updated`, `pull-merged` and
|
||||
`pull-closed`, its start reconciliation through `open-pulls` and `pull`, and the verb `groups` (the verbs
|
||||
`deliveries` and `show` answer from the records, A-24); the switch and the carried approval (G §156, §169, §542,
|
||||
A-281: `approval-carried`, `approval-carried-open`), since §765 drops what they carried; the states `merges`,
|
||||
`owed` (the old bucket), `asks`, `pulls` and `turns`, and the seat definition's entries for them.
|
||||
- **The indexer (H1):** the take-in fed by the bridge's messages; the state `pending` with its keys `m.<sequence>`
|
||||
and `g.<group>`; the hold for the indexer a revision names and its hand acts (ADR 0633 §1, the main file's *Taken in
|
||||
by the indexer it names*; `indexer_take_in_pending`, `indexer_drop_pending`); the validation at the take-in
|
||||
(G §16, §19, §237, §712, §713; A-475, A-475a), which becomes §745's step; its events `manifest-refused` and
|
||||
`manifest-accepted`; the catch-up by comparison (A-463, A-463a, A-490k, G §177's first-start half, G §362:
|
||||
`kickBehind`, `TakeInBehind`, `sayUntaken`, `takeInHeads`, `kickCatchUp`, `CatchUp`) and its condition
|
||||
`merge-untaken`; the source numbering in memory (A-431, `nextSource`); the 30-minute group wait of `take-in-waits`;
|
||||
the field `pull`; mesh-config's config candidates (ADR 0681 §2).
|
||||
- **The runner (H1):** the sweep (`StartUnstarted`, `Unstarted`; `StartHeld` of mesh-delivery #262, closed unmerged);
|
||||
the start-time `outdated` (G §375) and `runner_catch_up`, never built; `group-ended` (G §332) and its stream; the
|
||||
pipeline key per module; its `pinned` and `freed`.
|
||||
- **The assigner (H1):** the holds §750 names, with `acting-part-late`, `delivery-waits`, `version-delivered`,
|
||||
`assigner_delivered_again`, the acting rows of `assigner_waits` and `assigner_release`, the order waits (§751), the
|
||||
parts check and the `want-parts` capability, and A-436's digests in a want.
|
||||
- **mesh-config (H1):** its pull request path (ADR 0681 §1, §7) and A-490l's pull sweep.
|
||||
- **The checker (H1):** `mesh-delivery-checker` whole, with its verdict verb, its calls of
|
||||
`indexer_read_candidates`, `mesh/check` and its try; it is not placed at the clean state, and its buckets and bus
|
||||
account go with §765 on the operator's word of 2026-11-20 (ADR 0667 §12).
|
||||
- **Every seat contract (H1):** the `callers` lists (§752).
|
||||
- **Acceptance tests:** 38, 49, 81, 82, 105 and 106 as written; tests 110 to 113 hold what remains of them, and test
|
||||
67 is read with a merge call naming its three repositories.
|
||||
How it is checked: after each release, a search of the trunks of mesh-catalog, mesh-delivery, mesh-sdk,
|
||||
mesh-contracts, `mesh-host` and mesh-tools for each name above finds it in no file outside tests that assert its
|
||||
absence, and `mesh-broker.list` shows no bucket of a state above.
|
||||
- §765 **The stale state of the earlier model goes once, at the clean state.** (ADR 0682 §10; the operator,
|
||||
2026-11-20 about 01:10 CET: "I don't care about old data at this moment, I want a working mesh again") At milestone
|
||||
H1's clean state (the plan's section 5, step 4): the gate's buckets `merges`, `owed`, `asks`, `pulls` and `turns`
|
||||
and its 833 open records; the indexer's pins that name no running pipeline; the pipelines of the earlier model still
|
||||
running; every held or failed want; the checker's buckets. Each goes as ADR 0595 §4 removes kept data, on that word:
|
||||
through its module's tool where one exists, otherwise, once no running module declares the state (an orphan
|
||||
`orphans` lists), through the seat `mesh-broker`'s `drop` after its stream snapshot, the pack saying what it
|
||||
deleted, counted. The delivery records of the one model start from the clean state. How it is checked: the lead reads
|
||||
`mesh-broker.list` and each module's read tools before and after, and quotes the counts.
|
||||
@@ -5,10 +5,17 @@ design: 47
|
||||
milestone: H
|
||||
updated: 2026-11-20
|
||||
decisions:
|
||||
- "ADR 0666"
|
||||
- "ADR 0667"
|
||||
- "ADR 0682"
|
||||
- "ADR 0681"
|
||||
- "ADR 0667"
|
||||
- "ADR 0666"
|
||||
- "ADR 0656"
|
||||
- "ADR 0633"
|
||||
- "ADR 0596"
|
||||
- "ADR 0595"
|
||||
- "ADR 0573"
|
||||
- "ADR 0548"
|
||||
- "ADR 0525"
|
||||
---
|
||||
# 47, milestone H — the plan to deliver the build-and-delivery system properly
|
||||
|
||||
@@ -26,6 +33,21 @@ against that specification, with what runs live on each machine). The readings a
|
||||
here, and every number below comes from them unless it says otherwise. The plan is the lead's; the operator reads it
|
||||
before any code is written.
|
||||
|
||||
**Milestone H's part.** This file opens the part; its design lines (section 4's items as lines, numbered after G's
|
||||
§733 and cited as "design 47 H §n") are in three files, each read whole:
|
||||
|
||||
- [H-1-the-merge-call-and-the-take-in](H-1-the-merge-call-and-the-take-in.md): the merge call, the gate's source
|
||||
revision and record, the forge bridge's one message and the watchdog, the take-in, the step `validate`, one pipeline
|
||||
per take-in and none in parallel, a pipeline's pins (§734 to §749).
|
||||
- [H-2-wants-builds-reads-and-tools](H-2-wants-builds-reads-and-tools.md): the want rule, the order on one machine,
|
||||
every account may call every verb, the builder's lines, the reads of other parts made events, rates on the bus, the
|
||||
missing read tools, and which part moves onto the wake-up shape in which release (§750 to §762).
|
||||
- [H-3-corrections-and-what-retires](H-3-corrections-and-what-retires.md): the contradictions corrected in place, what
|
||||
retires, and the stale state dropped once (§763 to §765).
|
||||
|
||||
The wake-up rule itself is in the main file, *Every delivery part wakes on its inputs alone*. Where an H line and a G
|
||||
line or lead's answer differ, the H line holds, and the G line it corrects in place says so.
|
||||
|
||||
## 1. Where the system stands (read 2026-11-20 00:05 to 00:30 CET)
|
||||
|
||||
**What works.** One pipeline delivered one module end to end with no hand act on 2026-11-19 at 22:48 (the image
|
||||
@@ -302,8 +324,8 @@ deleted at release 6 of ADR 0429 and replaced by ADR 0666's pipelines per module
|
||||
what remained open was how the mesh learns which commits belong together, since ADR 0666 §13 reads a shared branch
|
||||
name through pull requests. The operator, 01:15 CET: since every version is deployed by a merge into main, an action,
|
||||
they have no objection to kicking the build-and-delivery process off by hand instead of listening to the forge's
|
||||
hooks; the lead named principle 3 (a kick-off a person forgets is a silent non-delivery) and proposed the merge through
|
||||
the mesh as the kick-off with the forge's event kept as the watchdog; the operator chose it (01:20 CET, "A, go
|
||||
hooks; the lead named principle 3 (a start a person forgets is a silent non-delivery) and proposed the merge through
|
||||
the mesh as the start with the forge's event kept as the watchdog; the operator chose it (01:20 CET, "A, go
|
||||
ahead"): one call of the seat `git`'s verb `merge-pull` naming one or more pull requests is the delivery's start and
|
||||
the group; nothing reads a pull request after it; a head moved outside the mesh raises a condition and delivers
|
||||
nothing. Item 1 below is answered so; item 6 is written from it. The operator also said they would not mind a start from scratch; the lead's answer is in
|
||||
|
||||
Reference in New Issue
Block a user