End tagged versions at milestone G, since no custom versions exist for now
The operator's answer of 2026-11-10 allows no custom version, and a tagged version is one: a group's run on request delivers nothing, so it builds its members against each package member's build by digest and publishes no version, and `tag-wanted` and `tag-asks` go with G's delivery. Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW
This commit is contained in:
@@ -1926,6 +1926,10 @@ ADR 0667's checks, of milestone G itself:
|
||||
publishes the other under `1.4.3`, which the catalog then says `version-released` once; a new `1.5` builds as
|
||||
`1.5.0`; two builds close together reserve two versions; a `beta` build reserves none and is delivered; a manifest
|
||||
saying `1.4-beta` is refused (whole, builder, indexer and Go build module, mesh-delivery and mesh-catalog).
|
||||
103. **A group's run on request publishes no version** (design 47 G §373). A run on request of a group changing a
|
||||
package and a module importing it builds the module against the package member's build by digest, publishes and
|
||||
reserves nothing, and no `tag-wanted` is said (whole, runner, builder and Go build module, mesh-delivery and
|
||||
mesh-catalog).
|
||||
|
||||
## What retires
|
||||
|
||||
@@ -2021,7 +2025,7 @@ release reports the controller's code lines against research 063's baseline (acc
|
||||
| L6 | Provisioning leaves the controller (ADR 0570): every provision is one key of the seat `mesh-provisioner`, held by mesh-provisioner, holding a reference and never a value, and each placed module's provisioning plan a key of its state `plans`, both composed from placement, the wants and the manifests on change events; each provider acts once all a provision depends on is provided; the assigner moves a want only once its build's provisions are provided; a provision no want needs is retiring, and its account or credential is removed only on the operator's Approve, its data never; the vault mints each provision's secret sealed to the consumer's and the provider's node, and the consumer's node-engine writes it; a wait for a person is a provision's state, which the watchman reads; bus permissions stay with the grants part (ADR 0349, ADR 0230, ADR 0547 §11) | — | mesh-sdk, the node-engine (`mesh-host`), mesh-tools (the tool runner's provisioner client), mesh-catalog (mesh-provisioner, the vault, the provisioner client, postgres, keycloak, gitea, route-adapter), mesh-delivery (assigner, watchman) | 1954 |
|
||||
| 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 102 | 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) |
|
||||
| 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 103 | 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) |
|
||||
|
||||
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
|
||||
|
||||
@@ -86,7 +86,7 @@ One file of milestone G's part of [design 47](../47-delivery-from-commit-to-deli
|
||||
- §64 **The run on request.** The runner's verb `run` takes one or more members, each a module at a named commit, runs them
|
||||
through their pipelines and delivers nothing, replacing the checker's try (ADR 0666 §18). Its callers are the
|
||||
sessions, as the agents' bus identities the tool runner proves, and the operator, and nothing else, since a run of a
|
||||
group builds and publishes its packages' tagged versions (design 51). The runner says `run-started`, the indexer builds
|
||||
group builds every member and its dependents on the build capacity (§373). The runner says `run-started`, the indexer builds
|
||||
the run's candidate from it, and the candidate's composition step writes no want (ADR 0656 §9); the candidate is
|
||||
dropped on that run's `pipeline-ended`. A step that could not run ends `could not run`, never as passed. A
|
||||
composition step for a node that sleeps passes it with a warning (ADR 0593 §9).
|
||||
|
||||
@@ -198,7 +198,8 @@ events are subscribed to): a new event of the seat `knowledge-base` would be a s
|
||||
the merge turns, their stalled line and tools and the setting `check-gates-merge`, once their record is accepted;
|
||||
the last three reads of a pull request's description (ADR 0659 §4); every delivery part's call of the forge module's
|
||||
own tools, for the seat `git`'s verbs; and the four seat-list readers the delivery parts wire by hand.
|
||||
- §321 At milestone G's delivery, from research 086 (ADR 0666, ADR 0667): the checker (`mesh-delivery-checker`), its seat,
|
||||
- §321 At milestone G's delivery, from research 086 (ADR 0666, ADR 0667): the tagged versions, `tag-wanted` and
|
||||
`tag-asks` (§373); the checker (`mesh-delivery-checker`), its seat,
|
||||
its try with `tryevent` and the indexer's try candidates, its kept verdicts and carries (the runner's from then), the
|
||||
checking program and `mesh/check`, and its buckets and bus account, removed with the gate's forge merge token only
|
||||
after the first pipeline after G's delivery has delivered a change end to end and on the operator's one word, its
|
||||
@@ -513,3 +514,12 @@ record it follows from, and replaces the builder's own choice where one was made
|
||||
without this every first version under G would start below today's and Go's `@latest` would never move (the
|
||||
design's choice, 2026-11-10). How it is checked: whole (indexer, builder), with `0.1.14` published before G, the
|
||||
first G build of `0.1` is `0.1.15`.
|
||||
- §373 **A group's run on request publishes no version.** A run on request of a group builds each member that
|
||||
depends on a package member against that member's build by its digest: the build module fetches the package
|
||||
member's build from the store by the digest its build's done key names and lays it in the build's workspace as the
|
||||
module that package names (a Go workspace's replacement, a TypeScript local package), so nothing is fetched by a
|
||||
version, and no version is reserved, numbered or published for the run. The tagged versions, `tag-wanted` (the
|
||||
checker's, and none of the runner's) and the builder's `tag-asks` with its tools `builder_tag`, `builder_tag_asks`
|
||||
and `builder_untag` go at G's delivery (design 51, *Tagged versions*). Why: the operator, 2026-11-10 about 21:40 CET,
|
||||
no custom versions for now, a tagged version being one; a run delivers nothing (ADR 0666 §18), so it needs no
|
||||
version. How it is checked: test 103.
|
||||
|
||||
@@ -6,7 +6,7 @@ code:
|
||||
- mesh-catalog modules/artifact-store-tools (the store's tools), modules/distribution (its program, holding the two image seats)
|
||||
- mesh-catalog modules/gitea (package retention; the two package seats' verbs in its Go bundle)
|
||||
- mesh-catalog modules/mesh-build-go, modules/mesh-build-node, modules/mesh-build-image (publishing through the seats)
|
||||
- mesh-delivery modules/mesh-delivery-builder (versions, tag asks; from milestone G a module's version reserved at its build's start and released by the catalog, the seat `mesh-builds`), the forge bridge, the indexer, the checker, the assigner, modules/mesh-delivery-pipeline (`tag-wanted` from milestone G)
|
||||
- mesh-delivery modules/mesh-delivery-builder (versions, tag asks; from milestone G a module's version reserved at its build's start and released by the catalog, the seat `mesh-builds`), the forge bridge, the indexer, the checker, the assigner, modules/mesh-delivery-pipeline (no tagged version from milestone G)
|
||||
- mesh-sdk (the bus helper for sending in parts)
|
||||
- mesh-catalog modules/docker (image pruning)
|
||||
- mesh-host internal/apply (every new image of a module pulled before any of its containers is replaced; a failed pull applied again on the status view's `settled` for the store's holder, and at the node-engine's start), internal/compose (each routed image reference written with its seat and that seat's holder)
|
||||
@@ -345,13 +345,17 @@ the verb.
|
||||
|
||||
### Tagged versions
|
||||
|
||||
- **From the delivery of design 47's milestone G there are no tagged versions** (the operator, 2026-11-10 about 21:40
|
||||
CET: no custom versions for now; design 47 G §373). A group's run on request builds its members against each
|
||||
package member's build by its digest and publishes no version; the tagged versions, the events `tag-wanted` (the
|
||||
checker's and any runner's), the builder's state `tag-asks` and its tools `builder_tag`, `builder_tag_asks` and
|
||||
`builder_untag` go, and nothing is numbered below a next version. The bullets below hold until that delivery.
|
||||
Tagged versions already published stay until a branch's end removes them as below, and nothing new is tagged. How
|
||||
it is checked: design 47's test 103.
|
||||
- **Asked by an event, never by a push** (ADR 0610 §1). The checker emits `tag-wanted` (repository, branch, head,
|
||||
tag), on a family of its own, `checker.asks`, kept seven days, apart from its verdicts, so a waiter on a verdict does
|
||||
not wake on it, for each head of a delivery group member that declares a package; a person asks through `builder_tag`.
|
||||
From the delivery of design 47's milestone G the checker goes, and the pipeline runner says `tag-wanted` instead, on
|
||||
its own seat `mesh-pipeline-runner`, for each member that declares a package of a run on request of a group not yet
|
||||
merged (ADR 0666 §18): a group merged together is one source revision whose packages are published before its
|
||||
dependents build, so only a run on request needs a tagged version. The
|
||||
Until the delivery of design 47's milestone G (below). The
|
||||
builder consumes the event on a durable consumer and keeps the ask in its own state `tag-asks`, removed when its
|
||||
branch is merged or deleted, or its pull request closed. An ask the builder has not answered within five minutes is narrated in the build log
|
||||
with what it waits on.
|
||||
@@ -359,9 +363,8 @@ the verb.
|
||||
and Go's `@latest` skips it. A package new in a group is numbered from its floor (`0.1.0-feat-x.1`).
|
||||
- **A group's check builds after `published`**: Go members by the tagged version, TypeScript members with their lock
|
||||
naming it and the registry's integrity; nothing is packed for a check, and a lone pull request's check publishes
|
||||
nothing. No `published` within the publish's bound (10 minutes) fails the check naming the package. From the
|
||||
delivery of design 47's milestone G the same holds for a group's run on request, whose pipeline steps build after
|
||||
`published`, and a step that gets no `published` within the bound ends failed, naming the package.
|
||||
nothing. No `published` within the publish's bound (10 minutes) fails the check naming the package. Until the
|
||||
delivery of design 47's milestone G (below).
|
||||
- **Removed with its branch**: on the forge bridge's `merged` event, its pull `closed`, or its branch-deleted event,
|
||||
heard on a durable consumer, the builder
|
||||
calls each seat's `remove`. It acknowledges the event only once every seat emitted `removed`; until then it retries
|
||||
|
||||
Reference in New Issue
Block a user