From b157283202be18ad3ec3a8721a854e0775ac1c34 Mon Sep 17 00:00:00 2001 From: jochen Date: Tue, 10 Nov 2026 21:50:26 +0100 Subject: [PATCH] Record on each released version what it was built against, and find what is behind with one query The operator chose on 2026-11-10 that the catalog of versions keeps a lockfile per released version (issue 1961): each edge's dependency version, so one query answers what is outdated after a restart or a missed event, while each edge kind is still started by its own event, a release or a delivery. Claude-Session: https://claude.ai/code/session_01JG73KK8HD1gufnqyFxMFdW --- .../47-delivery-from-commit-to-delivered.md | 11 ++++++- .../G-6-verbs-retires-and-answers.md | 32 +++++++++++++++++++ 2 files changed, 42 insertions(+), 1 deletion(-) diff --git a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md index eee387ed..5c804f3b 100644 --- a/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md +++ b/03-DESIGN/01-to-be/47-delivery-from-commit-to-delivered.md @@ -1930,6 +1930,15 @@ ADR 0667's checks, of milestone G itself: 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). +104. **A release records its dependencies, and each kind follows its event** (design 47 G §374, §376). A module + released at `1.4.3`, built against mesh-sdk `0.1.15` and delivered after a provider at `2.0.1`, holds those two + versions on its release; mesh-sdk's `version-released` of `0.1.16` rebuilds it, and the provider's + `version-delivered` of `2.0.2` writes its wants again; a node away is named and waits (whole, indexer, builder, + assigner 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 + 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; `indexer_outdated_again` says the event again and writes the hand-act log + (whole, indexer and runner, mesh-delivery). ## What retires @@ -2025,7 +2034,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..` 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 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) | +| 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 105 | 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 diff --git a/03-DESIGN/01-to-be/47-milestones/G-6-verbs-retires-and-answers.md b/03-DESIGN/01-to-be/47-milestones/G-6-verbs-retires-and-answers.md index bce2d577..8a89df26 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-6-verbs-retires-and-answers.md +++ b/03-DESIGN/01-to-be/47-milestones/G-6-verbs-retires-and-answers.md @@ -523,3 +523,35 @@ record it follows from, and replaces the builder's own choice where one was made 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. +- §374 **A released version records the versions it was built against or delivered after.** When the catalog + records a module's version as released (§349), it writes on that version, in its key of `versions`, one entry per + catalog-graph edge of the module's artifacts (the six kinds of *Dependencies between artifacts*): the kind, the + dependency's artifact reference and the dependency's version, a lockfile per released version. For the build kinds + (1 and 3) the version is the one the build used: the build module names each dependency version it resolved in its + step key, and the builder carries them in each artifact's `package-published`, so the indexer reads no other part's + state (ADR 0596). For the delivery kinds (2, 4, 5 and 6) it is the dependency's newest version running when the + released version first runs on a node, heard from the node-engine seat's `running` events through a durable consumer + of the indexer's own, the fingerprint mapped to its version in `versions`. The declared edge stays in the catalog + graph; the version is the release's fact, never changed after. Why: the operator, 2026-11-10 about 22:10 CET (issue + 1961). Each entry is about 0.1 KiB, about ten a version, so `versions` stays within its 64 MiB (an estimate). How it + is checked: test 104. +- §375 **One query finds every edge behind.** The seat `mesh-catalog`'s verb `outdated`, with the indexer's tool + `indexer_outdated`, answers every recorded edge whose version is lower than the dependency's newest released + version (kinds 1 and 2) or newest delivered version (kinds 3 to 6): the module and its version, the edge's kind, the + dependency, the recorded and the newest version, and the act that catches it up. A delivered version is one the + catalog has said `version-delivered` for (§376). Its callers are any person, an agent session, the healers, the + runner and the assigner; `indexer_outdated_again`, a hand act written in the hand-act log, says the event that + starts an edge's work again for one dependency. At its start, the runner and the assigner each ask `outdated` once + and start the work it names, so a restart or a missed event leaves nothing behind. Why: the operator, 2026-11-10 + (issue 1961's "outdated"); events start the work, and the query finds what is behind and answers a person. How it is + checked: test 105. +- §376 **Each kind is checked on its own event.** After a part's version is released, on its `version-released`: + the dependents by kind 1 are rebuilt against it and their pipelines started, as on `package-published` (§53), and + those by kind 2 are delivered again, the assigner writing their wants again naming the new version. After a part is + delivered, on the catalog's `version-delivered` (the module and the version, said once every present node that + places it runs it healthy, from the node-engine seat's `running`; nodes away are named and wait, ADR 0603 §7): the + dependents by kind 3 are rebuilt and their pipelines started, and those by kinds 4 and 6 are delivered again by + their wants. Kind 5, an acting part's act for a new version, is held by the acting parts' waits (*Within a revision + the new version acts first*) and is only recorded and shown by `outdated`. `version-delivered` is said on + `mesh.seat.mesh-catalog.event.version-delivered`, kept 90 days at 16 MiB. Why: the operator, 2026-11-10; the + events still start the work (ADR 0666 §14, §15). How it is checked: tests 104 and 105.