From 916be3a63c0c1d132567bb26bb767f4323bc2296 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 20:34:47 +0100 Subject: [PATCH 01/70] Answer A-363 to A-368: G's first start composes rights from the trunk, builds unpublished packages at the source commit, and waits for nothing only G answers Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- .../47-milestones/G-22-lead-answers-2.md | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 584e9b3a..f8189c42 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -746,3 +746,19 @@ the principle that settles it, cited as "design 47 G A-n". on a cycle, so a call word's edge on a cycle is left out like an invoked verb's. - **A-362** (completes A-353; principles 3 and 7) The seat list a runner starts with (mesh-sdk's bootstrapped list) holds `mesh-delivery` beside `mesh-catalog`, so `mesh-delivery.source` is admitted before the seat list is read. +- **A-363** (cycle C7; principles 7 and 2) While its catalog half is unread, grants composes each account from the + manifest the indexer's `modules` first view names for its module (the trunk's), in union with what its want's entry + gives, never from the list in force alone; so the first G parts get their G subjects before any of them serves. +- **A-364** (completes A-363; principle 7) Grants' own account carries the right to create each kept event stream of + the seat list (`SEAT_*`, such as `SEAT_git_branch-moved`) while the catalog half is unread, composed the same way. +- **A-365** (cycle C4, a silence of ADR 0573 §2/§4, which speaks of the latest published version; principle 7) A mesh + Go package no published version holds is built, for its importer, at the commit the gate's `source` names for its + repository, as an import of the same repository is; once a version is published, the latest published applies. The + indexer asks such a build with that commit, not on the version line. +- **A-366** (W5; principles 7 and 3) The indexer takes its own build from `MESH_FINGERPRINT` (mesh-sdk + process.OwnBuild) first, and asks the node-engine's `composition` only when it is unset. +- **A-367** (W22; principle 3) A planner of the catalog half (the bus keeper) treats a `none-yet` trunk as not yet + viewed: it plans nothing, deletes no plan and says no module orphaned until the first revision with entries. +- **A-368** (C6; principle 7) When neither the registrations nor the gate's `source` name a branch (a fresh mesh), + the catalog half counts the trunk as `none-yet`, once in the catalog client's `Ready` for every part, so the approval + gate is ready and `indexer_seed_again` runs. In this release, since G's genesis needs it. From da161cdbf1bcd9ba597c04a380a4d96c3d7299ec Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 20:45:09 +0100 Subject: [PATCH 02/70] Answer A-369: grants' catalog wait asks the client's Ready, as every part does Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index f8189c42..5da3e129 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -762,3 +762,5 @@ the principle that settles it, cited as "design 47 G A-n". - **A-368** (C6; principle 7) When neither the registrations nor the gate's `source` name a branch (a fresh mesh), the catalog half counts the trunk as `none-yet`, once in the catalog client's `Ready` for every part, so the approval gate is ready and `indexer_seed_again` runs. In this release, since G's genesis needs it. +- **A-369** (completes A-368; principle 7) Grants' own wait for its catalog half (`CatalogOf.Waiting`) asks the catalog + client's `Ready`, so a mesh that names no branch counts as `none-yet` for grants as for every other part. From 904f5bfac5222882c6b12241406127d56f48d9dc Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 20:53:47 +0100 Subject: [PATCH 03/70] Answer A-370: the indexer answers the catalog's first views at once, never behind a running take-in Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 5da3e129..f0f5229c 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -764,3 +764,7 @@ the principle that settles it, cited as "design 47 G A-n". gate is ready and `indexer_seed_again` runs. In this release, since G's genesis needs it. - **A-369** (completes A-368; principle 7) Grants' own wait for its catalog half (`CatalogOf.Waiting`) asks the catalog client's `Ready`, so a mesh that names no branch counts as `none-yet` for grants as for every other part. +- **A-370** (cycle C8, found by dry run 2's baseline; principles 1 and 7) The indexer answers the first views of the seat + `mesh-catalog` (`registrations`, `revision`) at once from what its state holds, never held behind a running take-in; + a take-in that changes them says so on its events. So a runner's catalog half is read before the take-in's own calls + (such as the forge bridge's `bridge_merged_message`) reach it. From e9a2aaf25302763d8d321827755b2c7364c76e08 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 20:54:05 +0100 Subject: [PATCH 04/70] Answer A-371 and A-372: grants counts a seat stream it creates itself as empty, and the assigner asks Ready Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index f0f5229c..ef9afbc2 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -768,3 +768,9 @@ the principle that settles it, cited as "design 47 G A-n". `mesh-catalog` (`registrations`, `revision`) at once from what its state holds, never held behind a running take-in; a take-in that changes them says so on its events. So a runner's catalog half is read before the take-in's own calls (such as the forge bridge's `bridge_merged_message`) reach it. +- **A-371** (review r1 finding 1; completes A-364; principles 7 and 3) A first view grants reads from a seat stream that + does not exist yet, and that grants itself creates (such as `SEAT_node-engine_running`), is empty, not a wait: grants + composes the pass, writes its own right to create the stream with it, then creates the stream and hears it from its + start; its health says the stream was created after the pass. +- **A-372** (completes A-368; principle 7) The assigner's wait for its catalog half (its `adopted` callback) asks the + catalog client's `Ready` as well, so a mesh that names no branch is `none-yet` for the assigner too. From 591297f02e0829287df9bb94ff1e46054dea1b09 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 22:00:46 +0100 Subject: [PATCH 05/70] Answer A-373: grants keeps its user list and pass in an object store, since they outgrow one bucket value Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index ef9afbc2..9b1d81a2 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -774,3 +774,7 @@ the principle that settles it, cited as "design 47 G A-n". start; its health says the stream was created after the pass. - **A-372** (completes A-368; principle 7) The assigner's wait for its catalog half (its `adopted` callback) asks the catalog client's `Ready` as well, so a mesh that names no branch is `none-yet` for the assigner too. +- **A-373** (live start, novox 21:56: "the value for list in mesh-grants_user-list is 422584 bytes, over the 262144 bytes + the bucket takes"; principles 1, 3 and 7) Grants keeps its user list and its pass result, which outgrow one value of a + key-value bucket, as objects in an object store of its own state (declared in its manifest like any kept data), the key + naming the object; a write that cannot be made stays loud as today. From 61149124f816684322767a362a00b49bfb9b5761 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 22:10:26 +0100 Subject: [PATCH 06/70] Answer A-374: the seat verb withheld reads a small key beside the list Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 9b1d81a2..6df329b1 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -778,3 +778,7 @@ the principle that settles it, cited as "design 47 G A-n". the bucket takes"; principles 1, 3 and 7) Grants keeps its user list and its pass result, which outgrow one value of a key-value bucket, as objects in an object store of its own state (declared in its manifest like any kept data), the key naming the object; a write that cannot be made stays loud as today. +- **A-374** (completes A-373; principles 3 and 7) The seat verb `withheld`, served from grants' tools bundle, reads a + small key `withheld` that the process writes beside the list in its state `user-list` each pass it changes, so it + answers without the object the list became; before that key is first written it reads the list as before. + (Built in mesh-delivery d6d6bd18.) From c5adb7fe489e3bf3aed589cd3a463fb1771f209d Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 22:46:43 +0100 Subject: [PATCH 07/70] Answer A-375: the gate's start path also lets the bindings' first view through Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 6df329b1..c2a7923d 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -782,3 +782,8 @@ the principle that settles it, cited as "design 47 G A-n". small key `withheld` that the process writes beside the list in its state `user-list` each pass it changes, so it answers without the object the list became; before that key is first written it reads the list as before. (Built in mesh-delivery d6d6bd18.) +- **A-375** (live start, novox 22:28-22:44: grants "the first view seat:mesh-broker.list of the bindings is not answered + (Not run: the marks of nats are not read yet ...)", and the indexer runtime "was bound no object-store called + catalog-revisions ... bound: none"; extends A-359; principle 7) The gate's start path also lets through the seat + `mesh-broker`'s verb `list` (the bindings' first view) while the catalog half is unread, since the catalog half's own + owner is bound its bus state through it. From 64b9ffe8c11f8f3a654e278a1165c694d9c2cf43 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 23:01:04 +0100 Subject: [PATCH 08/70] Answer A-376: the keeper makes the catalog holder's own bus state before its catalog half is in Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index c2a7923d..f4369c2a 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -787,3 +787,9 @@ the principle that settles it, cited as "design 47 G A-n". catalog-revisions ... bound: none"; extends A-359; principle 7) The gate's start path also lets through the seat `mesh-broker`'s verb `list` (the bindings' first view) while the catalog half is unread, since the catalog half's own owner is bound its bus state through it. +- **A-376** (live start, novox 22:4x-23:0x: the indexer runtime "was bound no object-store called catalog-revisions"; + the keeper plans nothing "before the catalog half's first views", which need that very store; cycle C12; completes + A-367 as A-363 completes grants; principles 7 and 3) Before its catalog half's first views are in, the bus keeper + makes the bus state of the holder of the seat `mesh-catalog` (the catalog half's own source), read from that module's + manifest on the trunk as the indexer's `manifests` first view gives it, and says each made entry as it does today, so + grants binds it; every other module waits for the catalog half as A-367 says. From 0e9b6e5286b3ec96a5e783b9d0b6ac50399bbcc6 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 23:12:47 +0100 Subject: [PATCH 09/70] Answer A-377 and A-378: first-view tools pass the start path; the keeper may read the indexer's views Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index f4369c2a..1a151b13 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -793,3 +793,10 @@ the principle that settles it, cited as "design 47 G A-n". makes the bus state of the holder of the seat `mesh-catalog` (the catalog half's own source), read from that module's manifest on the trunk as the indexer's `manifests` first view gives it, and says each made entry as it does today, so grants binds it; every other module waits for the catalog half as A-367 says. +- **A-377** (live start, novox 22:26: grants' first views of the indexer's `modules`, `manifests`, `verdicts` "Not run: + the marks of mesh-delivery-indexer are not read yet"; the keeper's A-376 reads the same views; widens A-359 back toward + A-353; principle 7) While the catalog half is unread, the gate's start path also lets through each module's own + first-view tools (the tools its first views name, which a caller list already limits), besides the seat verbs of A-359 + and A-375. +- **A-378** (completes A-376; principle 7) The indexer's first views `modules` and `manifests` name the bus module (`nats`) + among their callers, so its keeper reads the catalog holder's manifest. From c1065d9868387491ef9b9ed92f608ceebf389f9f Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 23:15:17 +0100 Subject: [PATCH 10/70] Answer A-379: the runner reaches a module's old objects by the name its membership gives, beside bindings Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 1a151b13..e33d7a6f 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -800,3 +800,9 @@ the principle that settles it, cited as "design 47 G A-n". and A-375. - **A-378** (completes A-376; principle 7) The indexer's first views `modules` and `manifests` name the bus module (`nats`) among their callers, so its keeper reads the catalog holder's manifest. +- **A-379** (replaces A-376 and A-378 for the start: the indexer's `catalog-revisions` is declared in its manifest's + old `objects` section, which grants creates (records.go objectsOf, assertions.go), while the tool runner reaches an + object store only by a new-form binding (node-tools internal/bus/bindings.go objectStore), so nothing binds it; + principle 7: what exists) The tool runner reaches a module's object store by the binding when one is bound, and + otherwise by the old `objects` entry its membership names, under the bus name grants created for it + (`OBJ__`); a name neither names stays refused as today. From a95c0d6d98dc34f5e0a8d3130a65166752bab1b2 Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 23:18:26 +0100 Subject: [PATCH 11/70] Answer A-380: the runner's old-objects fallback uses the name grants creates Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index e33d7a6f..0f63f70d 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -806,3 +806,7 @@ the principle that settles it, cited as "design 47 G A-n". principle 7: what exists) The tool runner reaches a module's object store by the binding when one is bound, and otherwise by the old `objects` entry its membership names, under the bus name grants created for it (`OBJ__`); a name neither names stays refused as today. +- **A-380** (corrects A-379's source of the name: grants issues no `objects` map in a membership; principle 7) With no + binding of that local name, the runner reaches the store under the name grants creates for a module's old `objects` + entry, `_` (stream `OBJ__`); the bus's grants to the module's account decide whether it + may, and a refusal is said with the store's name. From be264026b5dc66e38f245239f4c7c0c82caaadde Mon Sep 17 00:00:00 2001 From: jochen Date: Fri, 13 Nov 2026 23:59:02 +0100 Subject: [PATCH 12/70] Answer A-381: grants' own account may list stream names, which its stream assertion starts with Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 0f63f70d..6bef9ed9 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -810,3 +810,8 @@ the principle that settles it, cited as "design 47 G A-n". binding of that local name, the runner reaches the store under the name grants creates for a module's old `objects` entry, `_` (stream `OBJ__`); the bus's grants to the module's account decide whether it may, and a refusal is said with the store's name. +- **A-381** (live start, novox 23:42-23:58: grants is "Permissions Violation for Publish to $JS.API.STREAM.NAMES" while the + loaded list grants it STREAM.CREATE/INFO of each kept seat stream, so its assertion of the seats' kept events never + reaches the create and SEAT_mesh-conditions_findings-asked stays missing; every bundle with a finding writer exits; + principle 7) Grants' own account carries `$JS.API.STREAM.NAMES` (the read its assertion of kept streams starts with), + composed with the create rights of A-364. From 2c67b2e53bd6a5684da71f645069c32ed605abf9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 00:06:50 +0100 Subject: [PATCH 13/70] Answer A-382: every account may list stream names, which hearing an event starts with Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 6bef9ed9..6aa32edc 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -815,3 +815,8 @@ the principle that settles it, cited as "design 47 G A-n". reaches the create and SEAT_mesh-conditions_findings-asked stays missing; every bundle with a finding writer exits; principle 7) Grants' own account carries `$JS.API.STREAM.NAMES` (the read its assertion of kept streams starts with), composed with the create rights of A-364. +- **A-382** (widens A-381 to its kind, met a second time: live 00:02, every G bundle with a finding writer exits "no stream + on the bus carries mesh-conditions.findings-asked", because the tool runner's SubscribeNew finds a stream by subject + through `$JS.API.STREAM.NAMES`, which novox.node-tools may not publish, while EVENTS carries `mesh.seat.*.event.>`; + principles 7 and 6) Every account grants composes carries `$JS.API.STREAM.NAMES`, the read of stream names by subject + that hearing an event starts with; it lists names only. From 8af69b208251de20359e97bc8a42a094e2ea3974 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 00:22:48 +0100 Subject: [PATCH 14/70] Answer A-383: a right every account carries reaches a kept account too Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 6aa32edc..88c34fa4 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -820,3 +820,8 @@ the principle that settles it, cited as "design 47 G A-n". through `$JS.API.STREAM.NAMES`, which novox.node-tools may not publish, while EVENTS carries `mesh.seat.*.event.>`; principles 7 and 6) Every account grants composes carries `$JS.API.STREAM.NAMES`, the read of stream names by subject that hearing an event starts with; it lists names only. +- **A-383** (completes A-382; live 00:21: list revision 274 loaded, yet novox.node-tools still lacks + `$JS.API.STREAM.NAMES` (1805 publish rights, unchanged), since grants keeps an account it holds "beyond this pass" as + the list in force while the catalog half is unread; principles 7 and 3) A right every account carries (A-382) is added + to every account grants writes, a kept one included: keeping an account in force never withholds what every account + is given. A pass that only adds still never takes from a loaded user. From 9e619006c7ff0994cf052548c600391539f4bdb1 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 00:43:18 +0100 Subject: [PATCH 15/70] Answer A-384: a runner may make the ordered consumers its bundles hear new events on Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 88c34fa4..0ce92004 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -825,3 +825,9 @@ the principle that settles it, cited as "design 47 G A-n". the list in force while the catalog half is unread; principles 7 and 3) A right every account carries (A-382) is added to every account grants writes, a kept one included: keeping an account in force never withholds what every account is given. A pass that only adds still never takes from a loaded user. +- **A-384** (completes A-382/A-383 for the whole hearing path, met a third time: live 00:35 "an ordered consumer of + mesh-conditions.findings-asked on EVENTS: context deadline exceeded", the runner account holds only INFO of named durables + on EVENTS; principles 6 and 7) Every tool runner account carries what the runner's SubscribeNew (an ordered consumer from + the next message, mesh-tools node-tools internal/bus/subscribenew.go) asks of the stream that carries the events its + bundles hear: the create of an unnamed consumer filtered to those events' subjects, its next-message fetch, its info and + its delete, on EVENTS and on every kept seat stream; the same form for every runner, composed in one place. From 77a6a9aa6819aac165e2702622ac2a0129c79a71 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 01:06:35 +0100 Subject: [PATCH 16/70] Answer A-385: a kept account is the union of the list in force and this pass's composition Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 0ce92004..4790b16a 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -831,3 +831,9 @@ the principle that settles it, cited as "design 47 G A-n". the next message, mesh-tools node-tools internal/bus/subscribenew.go) asks of the stream that carries the events its bundles hear: the create of an unnamed consumer filtered to those events' subjects, its next-message fetch, its info and its delete, on EVENTS and on every kept seat stream; the same form for every runner, composed in one place. +- **A-385** (generalizes A-383, met a fourth time: live 01:00 "mesh-delivery-gate's bundle asked mesh/ledger.get and it + failed after 10s", the gate's ledger `records` exists and is bound, and novox.node-tools holds no right on + KV_mesh-delivery-gate_records_state, since a held runner account is copied whole from the list in force; principles 7 + and 3; A-363's union) An account grants keeps beyond a pass, a runner's included, is written as the union of the list + in force and what this pass composes for it (its carried modules' grants from the trunk's manifests and their + bindings), never the list in force alone; a pass that only adds still never takes from a loaded user. From 240f6401ce70fb0139ac0ab06b2e0122b07cc564 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 01:32:07 +0100 Subject: [PATCH 17/70] Answer A-386: a runner kept as it runs still gains the runner grants of what it carries Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 4790b16a..4448c3d8 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -837,3 +837,9 @@ the principle that settles it, cited as "design 47 G A-n". and 3; A-363's union) An account grants keeps beyond a pass, a runner's included, is written as the union of the list in force and what this pass composes for it (its carried modules' grants from the trunk's manifests and their bindings), never the list in force alone; a pass that only adds still never takes from a loaded user. +- **A-386** (completes A-385 for runners kept as they run; live 01:31: grants 3c582b1b in, novox.node-tools unchanged + (2004 publish rights, none on KV_mesh-delivery-gate_records_state), since `runnerUsersKept` keeps a runner whose running + manifest does not say it is the tool runner whole (ADR 0601 §4); principles 7 and 3) A runner kept as it runs is written + as the union of the list in force and the runner grants its carried modules' bindings and events give (the ledger + readers, the new-event rights of A-384, the streams' names of A-382): what a carrying runner is given, never what a + plain module is given, so ADR 0601 §4 stands. From 8dffde7f33f466aed54ddb466ef87773acf0c9ed Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 02:20:39 +0100 Subject: [PATCH 18/70] Answer A-387: before the catalog half is read, a read verb of a held definition runs; git is bootstrapped Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 4448c3d8..bc1d388f 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -843,3 +843,12 @@ the principle that settles it, cited as "design 47 G A-n". as the union of the list in force and the runner grants its carried modules' bindings and events give (the ledger readers, the new-event rights of A-384, the streams' names of A-382): what a carrying runner is given, never what a plain module is given, so ADR 0601 §4 stands. +- **A-387** (generalizes A-353, A-359 and A-375, met a fourth time: live 02:16 the first take-in took in none of 18 + repositories, "the seat git did not answer pull: Not run: the definition of the seat git is not yet read by this tool + runner's seat list", and the runner's own `mesh-catalog.seat-definitions` is refused "the marks of + mesh-delivery-indexer are not read yet"; principles 7 and 3) Before the catalog half is read, the gate lets through + every verb that the seat definition the runner holds classes `read` and does not mark needs-approval, and judges every + other call as before; the hand-kept list `startReads` goes. The bootstrapped definitions carry every seat the first + take-in reaches: `git` joins them, a byte-for-byte copy of its contracts file with its row in the bootstrap test. The + catalogue seat's contract classes `modules`, `module`, `provides`, `dependents` and `seat-definitions` as `read`, and + its bootstrapped copy follows. From c1a647e9bba64f340ed23361ab3c500c0c356640 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 02:22:16 +0100 Subject: [PATCH 19/70] Answer A-388: the start path takes only an explicit read class; the broker's four reads are classed Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index bc1d388f..d5fd7076 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -852,3 +852,8 @@ the principle that settles it, cited as "design 47 G A-n". take-in reaches: `git` joins them, a byte-for-byte copy of its contracts file with its row in the bootstrap test. The catalogue seat's contract classes `modules`, `module`, `provides`, `dependents` and `seat-definitions` as `read`, and its bootstrapped copy follows. +- **A-388** (completes A-387; the developer's question: seatdef callers.go reads a verb with no class as a read, which + would let unclassed acts such as `mesh-delivery-checker.try` and `operator-channel.tell` through before the catalog + half is read; principles 3 and 7) A-387's start path takes a verb whose definition names the class `read` explicitly, + never one that names none. The broker seat's contract classes `list`, `show`, `check` and `orphans` as `read`, and its + bootstrapped copy follows, so A-375's `mesh-broker.list` still passes. From 5aa4510f0f152a71086e6a97d0bf967aff3bae1c Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 02:36:55 +0100 Subject: [PATCH 20/70] Answer A-389: before the catalog half is read, a module's call of another module's tool runs unmarked, logged Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index d5fd7076..2ea6a6d7 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -857,3 +857,11 @@ the principle that settles it, cited as "design 47 G A-n". half is read; principles 3 and 7) A-387's start path takes a verb whose definition names the class `read` explicitly, never one that names none. The broker seat's contract classes `list`, `show`, `check` and `orphans` as `read`, and its bootstrapped copy follows, so A-375's `mesh-broker.list` still passes. +- **A-389** (completes A-387 for module tools, met a fifth time: live 02:32 the take-in's + `mesh-delivery-forge-bridge.bridge_merged_message` is refused "the marks of mesh-delivery-forge-bridge are not read + yet"; a module tool names no class, and its marks live only in the catalog half's entry the take-in has not made yet; + principles 7 and 3) Before the catalog half is read, a module tool whose proven caller is another module's account (never + a session's or the console's) runs unmarked, and the runner logs each such call once per tool with its caller ("run + unmarked before the catalog half is read"); a module tool called otherwise waits and is judged as before. A module + tool's mark is read again, and holds, from the call after the half is read. Today the one marked module tool, + `gitea_branch_protection_loosen`, has no module among its callers. From 5d7a96fe66cccd91c32a3133b7836d840dc9cb52 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 03:19:13 +0100 Subject: [PATCH 21/70] Answer A-390: the verb revision's callers count an invokes of a single *, as grants reads it Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 2ea6a6d7..ecd335c6 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -865,3 +865,9 @@ the principle that settles it, cited as "design 47 G A-n". unmarked before the catalog half is read"); a module tool called otherwise waits and is judged as before. A module tool's mark is read again, and holds, from the call after the half is read. Today the one marked module tool, `gitea_branch_protection_loosen`, has no module among its callers. +- **A-390** (live 03:17 on novox: the tool runner's first view of the catalog half is refused "mesh-catalog.revision is + refused to novox.node-tools: the tool answers only mesh-delivery-builder"; node-tools declares `invokes: ["*"]`, and + the verb revision's callers rule (ADR 0663 §2) matches `seat:mesh-catalog.revision` by its exact text alone, while the + grants part reads a single `*` as every seat verb; principles 7 and 3) The verb revision's callers are the parts whose + entry in the newest trunk revision declares `seat:mesh-catalog.revision` or a single `*` in invokes, as the grants part + reads invokes; the holder stays off the list. From 19f5ad86d21af4fe0fb7ce8bb616d2bb113a392d Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 04:03:00 +0100 Subject: [PATCH 22/70] Answer A-391: the indexer's start replay writes the view once, and says its length Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index ecd335c6..34170f21 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -871,3 +871,8 @@ the principle that settles it, cited as "design 47 G A-n". grants part reads a single `*` as every seat verb; principles 7 and 3) The verb revision's callers are the parts whose entry in the newest trunk revision declares `seat:mesh-catalog.revision` or a single `*` in invokes, as the grants part reads invokes; the holder stays off the list. +- **A-391** (live on novox: the indexer's start ran 50 minutes of CPU in its first hour without reaching its take-ins + watch, so the seed was never asked; it wrote the whole catalog view again after each finished build of the build log, + though none changed a module; principles 7 and 3) A finished build writes the view again only when it changed a module; + at the start the build log's finished builds are applied first and the view is written once, the replay said in one + line at its start and one at its end with its count and duration. From 087e17c799fcf1454a0eebea0c067a7137845ff6 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 11:24:49 +0100 Subject: [PATCH 23/70] Answer A-392: a seed asks a silent build seat once, and says so Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 34170f21..a0168d02 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -876,3 +876,7 @@ the principle that settles it, cited as "design 47 G A-n". though none changed a module; principles 7 and 3) A finished build writes the view again only when it changed a module; at the start the build log's finished builds are applied first and the view is written once, the replay said in one line at its start and one at its end with its count and duration. +- **A-392** (live on novox: the seed asked every artifact's build seat for its steps one by one, each call to a seat with + no holder retried for 30 seconds, so a seed of 178 entries ran for hours before refusing; principles 3 and 7) Within one + seed, a build seat that did not answer is not asked again for its later artifacts; they stay unanswered, the seed refuses + with the same words, and the seat's first silence is said in one line. From 5f04a5e3afbbc5316db2f95f1ebf23df40c062dd Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 11:31:09 +0100 Subject: [PATCH 24/70] Answer A-393: a node seat's verb asked with no machine is answered by any one holder Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index a0168d02..7eb16874 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -880,3 +880,8 @@ the principle that settles it, cited as "design 47 G A-n". no holder retried for 30 seconds, so a seed of 178 entries ran for hours before refusing; principles 3 and 7) Within one seed, a build seat that did not answer is not asked again for its later artifacts; they stay unanswered, the seed refuses with the same words, and the seat's first silence is said in one line. +- **A-393** (live: the build runtimes serve `steps` only on `mesh.seat.node-build-go.tool.steps.`, and the seed asks + `seat:node-build-go.steps` naming no machine, since it cannot know the holders before the assigner's view; principles 7 and 1) + A verb of a node-scoped seat asked with no machine is answered by any one holder: each holder's runtime also serves the verb + on the subject without the machine (tool and call forms), in one queue group per seat and verb, and the grants part grants + each holder those subjects. From 6bc258db0de1ddbc58bebd02a38ac4246e6472de Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 12:00:53 +0100 Subject: [PATCH 25/70] Answer A-395: every trunk part and the tool runner may read the catalog half Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 7eb16874..f46182d7 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -885,3 +885,7 @@ the principle that settles it, cited as "design 47 G A-n". A verb of a node-scoped seat asked with no machine is answered by any one holder: each holder's runtime also serves the verb on the subject without the machine (tool and call forms), in one queue group per seat and verb, and the grants part grants each holder those subjects. +- **A-395** (live: novox's tool runner was refused `mesh-catalog.revision` 54 times, the verb answering only parts that + declare it in invokes, while the runner reads the catalog half for every module it serves; principles 7 and 4) Every part + the newest trunk revision holds may read the verb revision, and so may the tool runner; the holder stays refused. ADR 0663 + §2's rule that a part reads it only by declaring it is proposed for its end. From 525a9590cd479d0f967d1fd25a3fba78d761f00a Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 12:09:52 +0100 Subject: [PATCH 26/70] Answer A-396: every module is composed as invoking the tool runner's own reads Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index f46182d7..4d0bd4ff 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -889,3 +889,7 @@ the principle that settles it, cited as "design 47 G A-n". declare it in invokes, while the runner reads the catalog half for every module it serves; principles 7 and 4) Every part the newest trunk revision holds may read the verb revision, and so may the tool runner; the holder stays refused. ADR 0663 §2's rule that a part reads it only by declaring it is proposed for its end. +- **A-396** (live: the shanks build runtimes' seat list and catalog-half reads were refused on their caller-named subjects, + since no build module's manifest invokes them; principles 7 and 4) Every module is composed as invoking the tool runner's + own reads (the seat list's verb, the catalog half's revision and registrations, the delivery seat's source), so each + account the runner serves a module on may ask them. From ed95207361db0b65efe15137ceaab6f6cc589b73 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:02:11 +0100 Subject: [PATCH 27/70] Answer A-397: every process that hears events has a durable consumer of its own, named constantly; a shared one split the first registrations between the assigner's program and its tool runner --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 4d0bd4ff..e3701472 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -893,3 +893,13 @@ the principle that settles it, cited as "design 47 G A-n". since no build module's manifest invokes them; principles 7 and 4) Every module is composed as invoking the tool runner's own reads (the seat list's verb, the catalog half's revision and registrations, the delivery seat's source), so each account the runner serves a module on may ask them. +- **A-397** (live, ace 2026-11-14: the assigner's program and its tool runner both bound the durable consumer + `ace_mesh-delivery-assigner` on `SEAT_mesh-catalog_registration-changed`; the runner pulled all 178 events of the first + registrations and the program, which acts on them, heard none and said nothing; the operator decided, 2026-11-14 about + 18:10: "a constant name for each separate process"; principles 1 and 7) Every process of a module that hears events + hears them on a durable consumer of its own, named constantly across restarts: the module's program `_`, + its tool runner `__tools`, any other process its manifest names `__` (A-340). A + durable name holds no dot (design 19 *The consumer*). Only a work queue's consumer is shared, by the processes its + `bus.queues` names. The grants part composes and makes each of them, with the hear of exactly that process's events; a + process that binds a consumer composed for another process is refused at its start, said in its log. This amends + design 19's *one durable consumer per module*, written when a module was one process. From 98e8bc395b88e99b72ffbf7f888aa4a33d9c9d01 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:03:19 +0100 Subject: [PATCH 28/70] A-397: the operator's decision time read from the clock --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index e3701472..1aff7b0b 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -896,7 +896,7 @@ the principle that settles it, cited as "design 47 G A-n". - **A-397** (live, ace 2026-11-14: the assigner's program and its tool runner both bound the durable consumer `ace_mesh-delivery-assigner` on `SEAT_mesh-catalog_registration-changed`; the runner pulled all 178 events of the first registrations and the program, which acts on them, heard none and said nothing; the operator decided, 2026-11-14 about - 18:10: "a constant name for each separate process"; principles 1 and 7) Every process of a module that hears events + 18:00: "a constant name for each separate process"; principles 1 and 7) Every process of a module that hears events hears them on a durable consumer of its own, named constantly across restarts: the module's program `_`, its tool runner `__tools`, any other process its manifest names `__` (A-340). A durable name holds no dot (design 19 *The consumer*). Only a work queue's consumer is shared, by the processes its From f6f82721d5d4deec586619c8feb65555f27ccf35 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:17:34 +0100 Subject: [PATCH 29/70] Answer A-398: a seat-form read resolves to the assigned claimant when no holder is on record --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 1aff7b0b..7f7934a3 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -903,3 +903,9 @@ the principle that settles it, cited as "design 47 G A-n". `bus.queues` names. The grants part composes and makes each of them, with the hear of exactly that process's events; a process that binds a consumer composed for another process is refused at its start, said in its log. This amends design 19's *one durable consumer per module*, written when a module was one process. +- **A-398** (live, shanks 2026-11-14 18:13: the G builder was refused `KV_mesh-build-go_steps` and the image and node steps, + since its reads `seat:node-build-{go,image,node}.steps` resolved to no holder: no assignments holds the build seats; the + operator decided, 2026-11-14 about 18:16: "yes, do it", after their word of 16:45 that who holds a seat follows from the + module graph and the assignments; principles 1 and 7) A seat-form read, view or view tool resolves to the holder on + record, else to the first module assigned to a node (nodes and modules in name order) whose manifest claims the seat. + Holds keep heldWherePlaced's rule. The whole question of holders stays with the post-G remarks. From f55a6e7927906ab32aef3918084a7f250fe58cea Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:39:47 +0100 Subject: [PATCH 30/70] Answer A-399: a seat pulled by kind's holder says the seat's own events --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 7f7934a3..283be323 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -909,3 +909,10 @@ the principle that settles it, cited as "design 47 G A-n". module graph and the assignments; principles 1 and 7) A seat-form read, view or view tool resolves to the holder on record, else to the first module assigned to a node (nodes and modules in name order) whose manifest claims the seat. Holds keep heldWherePlaced's rule. The whole question of holders stays with the post-G remarks. +- **A-399** (live, shanks 2026-11-14 18:32: the Go build seat was refused `toolchain-reported.shanks`, and `step-ended` too: a + seat pulled by kind is composed by the seat-traffic rules, which grant an event only under a kind or a caller's name, and + the held-seat rule skips such a seat, so its own events were granted to nobody and the builder heard no toolchain; + principle 7, and who-may-is-not-the-operators-question) The holder of a seat pulled by kind (not kinded) says each of the + seat's events no caller names: on its own machine in its account where the definition's subject names `` + (machineEvent now reads `` from any node seat's event subject, not the node-engine's alone), and with any machine in + its membership, since the runtime carrying it checks the membership; the account is therefore granted any machine's too. From 232454cf762985586df33d21b8834cae6d6136bb Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 18:51:53 +0100 Subject: [PATCH 31/70] A-397: the rule is the developer's judgement (share a durable only for shared work), not an operator ruling --- .../47-milestones/G-22-lead-answers-2.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 283be323..23486625 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -895,14 +895,14 @@ the principle that settles it, cited as "design 47 G A-n". account the runner serves a module on may ask them. - **A-397** (live, ace 2026-11-14: the assigner's program and its tool runner both bound the durable consumer `ace_mesh-delivery-assigner` on `SEAT_mesh-catalog_registration-changed`; the runner pulled all 178 events of the first - registrations and the program, which acts on them, heard none and said nothing; the operator decided, 2026-11-14 about - 18:00: "a constant name for each separate process"; principles 1 and 7) Every process of a module that hears events - hears them on a durable consumer of its own, named constantly across restarts: the module's program `_`, - its tool runner `__tools`, any other process its manifest names `__` (A-340). A - durable name holds no dot (design 19 *The consumer*). Only a work queue's consumer is shared, by the processes its - `bus.queues` names. The grants part composes and makes each of them, with the hear of exactly that process's events; a - process that binds a consumer composed for another process is refused at its start, said in its log. This amends - design 19's *one durable consumer per module*, written when a module was one process. + registrations and the program, which acts on them, heard none and said nothing; principles 1 and 7) A durable name is + shared only where the work is meant to be shared: a work queue, each item to one taker, as NATS shares one durable among + its pullers. Every other reader needs every message, so each process of a module that hears events has a durable consumer + of its own, named constantly across restarts: the module's program `_`, its tool runner + `__tools`, any other process its manifest names `__` (A-340). A durable name holds no + dot (design 19 *The consumer*). The grants part composes and makes each, with the hear of exactly that process's events. + This is a builder's judgement no design line overrode (the operator, 2026-11-14: "the developer should use his brains"); + design 19's *one durable consumer per module* was written when a module was one process. - **A-398** (live, shanks 2026-11-14 18:13: the G builder was refused `KV_mesh-build-go_steps` and the image and node steps, since its reads `seat:node-build-{go,image,node}.steps` resolved to no holder: no assignments holds the build seats; the operator decided, 2026-11-14 about 18:16: "yes, do it", after their word of 16:45 that who holds a seat follows from the From d5e7d42d172a27045a785a34ae88d948a61a660b Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 20:21:29 +0100 Subject: [PATCH 32/70] Answer A-400: seat-holders names the assigned claimant of a seat no assignments holds --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 23486625..811db822 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -916,3 +916,12 @@ the principle that settles it, cited as "design 47 G A-n". seat's events no caller names: on its own machine in its account where the definition's subject names `` (machineEvent now reads `` from any node seat's event subject, not the node-engine's alone), and with any machine in its membership, since the runtime carrying it checks the membership; the account is therefore granted any machine's too. +- **A-400** (live, the control-node 2026-11-14 19:12: the indexer waited for ever on the view `seat:mesh-module-assigner.assignments` + for a holder of the seat, since the assigner's state seat-holders is written from the assignments' holds alone and no + assignments holds mesh-module-assigner; its versions fill stayed undone and no build began; the operator, 2026-11-14 about + 16:45 and 18:16, as for A-398; principles 1 and 7) The assigner writes seat-holders from the assignments' holds and, for + each seat no holding names (a seat held once: on no node; a seat of every node: on that node), the first module assigned + to a node (nodes and modules in name order) whose manifest of the trunk claims it: the same rule as A-398, in the + writer every reader of the holders reads. It says each key so derived once, and when it stops being derived. The + assignment graph's requirement resolution and the order waits keep reading holders from the holds alone; the post-G + remarks take that up with the rest of the holders question. From de9f6d33539209cb2028f1c35c65af51afaf516d Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:05:17 +0100 Subject: [PATCH 33/70] Answer A-401: a newly watched branch starts from the forge at its head, as a clone does --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 811db822..f9576357 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -925,3 +925,17 @@ the principle that settles it, cited as "design 47 G A-n". writer every reader of the holders reads. It says each key so derived once, and when it stops being derived. The assignment graph's requirement resolution and the order waits keep reading holders from the holds alone; the post-G remarks take that up with the rest of the holders question. +- **A-401** (live, the control-node 2026-11-14 21:5x: the assigner ended every proposal, since f1-circuits (watched on + master), link2pay and photos (watched on nox-mesh) are held in no catalog graph of their branch; the gate writes + `source.` only on a take-in of a merge on that branch (A-34), so a newly watched branch is never started; the + operator, 2026-11-14 about 22:00: "by doing a git clone"; principles 2, 4 and 7, §15, §430, A-85, A-93) A watched branch + starts from the forge, as a clone does. The gate, at its start and on each `registration-changed` of the seat + `mesh-catalog`, writes `source.` for every watched branch the registrations name that no source key holds yet + (§430, which wrote the default branch alone): each repository registered on it at the branch's head, asked of the seat + `git`'s verb `branch`, the group left empty, and says `source-moved`; a repository whose head cannot be read is left out + and said, and is added at the next registration change or by hand. Its tool `gate_source_start` (branch, why) does the + same by hand through the hand-act log. A key it holds is never rewritten this way: from then on only a take-in moves it + (A-34). The indexer takes a head the source names in from that head's merged message as before; a head with no merged + message is read whole at that commit through the seat `git` (its tree and files), taken in as a merge whose changed + files are every file of that tree, and computed as any other (A-93). So the branch keeps its first revision + `branch..1`, and its later merges follow the designed path. From dbe9d711ea5bfc2628d46c60a0e72b7927a51f23 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:08:11 +0100 Subject: [PATCH 34/70] Answer A-402: a head is read whole on any failure to read its merged message --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index f9576357..30343288 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -939,3 +939,7 @@ the principle that settles it, cited as "design 47 G A-n". message is read whole at that commit through the seat `git` (its tree and files), taken in as a merge whose changed files are every file of that tree, and computed as any other (A-93). So the branch keeps its first revision `branch..1`, and its later merges follow the designed path. +- **A-402** (A-401; principles 7 and 3) The indexer reads a head whole through the seat `git` on any failure to read its + merged message, not only on the forge bridge's "no merged pull request": the read at the same commit gives the same + tree, so no typed error is added to the bridge; each such read is logged with its cause, and a head neither way reads + stays unread, as before. From b6380d0958226677b27272e35d4bac4876de75d3 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:08:40 +0100 Subject: [PATCH 35/70] Answer A-403: the gate adds a registered repository a held source key lacks, and changes no head it holds --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 30343288..9dc40ed8 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -943,3 +943,8 @@ the principle that settles it, cited as "design 47 G A-n". merged message, not only on the forge bridge's "no merged pull request": the read at the same commit gives the same tree, so no typed error is added to the bridge; each such read is logged with its cause, and a head neither way reads stays unread, as before. +- **A-403** (A-401; principles 2 and 7) "A key it holds is never rewritten" means no head it holds is changed: at its start, + on each registration change and by its tool, the gate adds to a held `source.` every registered repository the + key does not name yet, at the branch's head, and says `source-moved` only when it added one; the heads it holds move by + a take-in alone (A-34). So a repository left out once, or registered later on a branch already watched, comes in the + same way. From 634b4ea49e98207b8c393b8abb99b3056d6f350c Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:16:04 +0100 Subject: [PATCH 36/70] Answer A-404: a source the gate started from the forge names no group in its source-moved --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 9dc40ed8..1b61a0c2 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -948,3 +948,6 @@ the principle that settles it, cited as "design 47 G A-n". key does not name yet, at the branch's head, and says `source-moved` only when it added one; the heads it holds move by a take-in alone (A-34). So a repository left out once, or registered later on a branch already watched, comes in the same way. +- **A-404** (A-401, A-403; principles 7 and 3) A `source-moved` the gate says for heads it started from the forge, on a new + key or added to a held one, names no group, as A-401's new key does: no group moved it, so nothing times it as a + group's; the key keeps the group a take-in last wrote. From 4b2eb0bcf4e3bb49cd45722b18d900ab3c0becd9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:42:00 +0100 Subject: [PATCH 37/70] Answer A-405 and A-406: a node composes around a running build with no entry; the pipeline's manifest passes the judge and is built once by hand --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 1b61a0c2..66d1193e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -951,3 +951,15 @@ the principle that settles it, cited as "design 47 G A-n". - **A-404** (A-401, A-403; principles 7 and 3) A `source-moved` the gate says for heads it started from the forge, on a new key or added to a held one, names no group, as A-401's new key does: no group moved it, so nothing times it as a group's; the key keeps the group a take-in last wrote. +- **A-405** (live, the control-node 2026-11-14 22:34: its node-engine refused every candidate, "nothing provides" postgres-database, + secret, route, s3-bucket, document-server and mcp-endpoint, since its catalogue holds only modules whose wanted build has a + catalog entry, and the providers' wants name the builds running from before G, which have none, their new builds waiting + for a pipeline that cannot be placed while the node refuses; the operator, 2026-11-14 about 22:40: "yes, go ahead"; + principles 2 and 7, §421) A module the node runs whose wanted build has no catalog entry stays in the node's catalogue as + the build it runs, from the manifest of that build the node keeps: it provides, claims and requires what that manifest + says, so the node resolves around it. Its want stays held with `entry-missing` (§421) and nothing new of it is composed; + when its new build's entry comes, it is composed as any other. +- **A-406** (live, the control-node 2026-11-14 22:34: the pipeline's manifest at its build was refused by the manifest judge on + 2026-11-13, and its candidate carried no parts; the operator, as for A-405; principles 5 and 7) The pipeline's manifest is + made to pass the judge, as any module's; its first build is asked of the builder once by hand, the way a run on request + asks it, since only a pipeline asks builds and none runs yet. From 706e76b566a1c391af57407f846c7f99e98d20d8 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:46:19 +0100 Subject: [PATCH 38/70] Answer A-407: a running build with no entry is described for resolving by the entry of the build its want says is being built --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 66d1193e..5272694d 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -963,3 +963,8 @@ the principle that settles it, cited as "design 47 G A-n". 2026-11-13, and its candidate carried no parts; the operator, as for A-405; principles 5 and 7) The pipeline's manifest is made to pass the judge, as any module's; its first build is asked of the builder once by hand, the way a run on request asks it, since only a pipeline asks builds and none runs yet. +- **A-407** (A-405; principles 7 and 2: the node keeps no manifest of a build that has no entry, and the running event + carries only a digest) A running module whose wanted build has no entry is described from the catalog entry of the build + its want says is being built (the newest of its first watched branch), read through the seat `mesh-catalog`'s `entry` as + any entry: what it provides, claims and requires there stands for the running build, for resolving the node alone. A + want that names no newer build leaves the module as today (a name alone), said once. From 46b6b741485d03c0201e6cb02398307bff4bb134 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:47:32 +0100 Subject: [PATCH 39/70] Answer A-408: the builder reads the kept versions-filled at its start --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 5272694d..1017c2d2 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -968,3 +968,8 @@ the principle that settles it, cited as "design 47 G A-n". its want says is being built (the newest of its first watched branch), read through the seat `mesh-catalog`'s `entry` as any entry: what it provides, claims and requires there stands for the running build, for resolving the node alone. A want that names no newer build leaves the module as today (a name alone), said once. +- **A-408** (live, the build node 2026-11-14 22:45: the builder held every build "wait-held, the catalog has not said + versions-filled", while the indexer said it once at 01:33 UTC and keeps it as said; the builder keeps the mark in memory + alone and its durable consumer took the event once, so a restart lost it; principles 1 and 3, §369, §372) The builder + reads at its start the last `versions-filled` the seat's stream keeps (it is kept with no age limit, §372) by a direct + read of the last message on its subject, and takes it as heard; the event heard later sets it as before. From 11054da2407ebd680191afd37b499b3423c3a1d0 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 22:51:41 +0100 Subject: [PATCH 40/70] Answer A-409: a consumed seat event matches by name and filters on the seat's subject; the revision's id names its branch --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 1017c2d2..d6402843 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -973,3 +973,11 @@ the principle that settles it, cited as "design 47 G A-n". alone and its durable consumer took the event once, so a restart lost it; principles 1 and 3, §369, §372) The builder reads at its start the last `versions-filled` the seat's stream keeps (it is kept with no age limit, §372) by a direct read of the last message on its subject, and takes it as heard; the event heard later sets it as before. +- **A-409** (live 2026-11-14: the assigner's and the builder's durable consumers filter only + `mesh.mod.mesh-catalog.event.catalog-revision`, so neither hears a catalog revision after its first view; the seat + definition says the event `catalog-revision` with the subject `catalog-revision.`, and the grants part, finding + no match for the consumed `mesh-catalog.catalog-revision`, fell back to a module's event without a word; principles 1 + and 3) A consumed seat event matches the seat's event of that name whatever its subject's further tokens, and its filter + is the seat event's subject with each `<...>` token as `*` (a trailing one also as the rest); a consume naming a seat + that says no such event is refused aloud by the grants part, never turned into a module's event. The indexer's + `catalog-revision` duplicate id names the branch, and it is published with the bus's acknowledgement. From 842071859a532bd85759ebd6801594f64bb0da0d Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 23:14:41 +0100 Subject: [PATCH 41/70] Answer A-410: a running module the node cannot fingerprint is held, never counted as removed --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index d6402843..56fbba76 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -981,3 +981,10 @@ the principle that settles it, cited as "design 47 G A-n". is the seat event's subject with each `<...>` token as `*` (a trailing one also as the rest); a consume naming a seat that says no such event is refused aloud by the grants part, never turned into a module's event. The indexer's `catalog-revision` duplicate id names the branch, and it is published with the bus's acknowledgement. +- **A-410** (live, the control-node 2026-11-14 about 22:55: proposals placing the pipeline were answered "differs", with + fail2ban, pacman and mesh-mail-reader counted as removed, while all three run and their assignments hold them; a module + started before the node-engine wrote fingerprints has none in what it runs, and none can be made for it, so its + comparison is skipped, and a skipped comparison was counted as a removal; principles 2 and 3) A module the node runs + whose fingerprint it cannot read or make is held: it is kept as it runs and said as held, with why, in the node's + answer, never counted as removed and never stopped for it. Only a module the node runs that no assignment names is + removed. From 7981d72d9b4febc87709fc42da0b5d223254cef9 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 23:37:07 +0100 Subject: [PATCH 42/70] Answer A-411: the builder reads the last versions-filled from the seat event's kept stream, not EVENTS --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 56fbba76..56d36d0e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -988,3 +988,8 @@ the principle that settles it, cited as "design 47 G A-n". whose fingerprint it cannot read or make is held: it is kept as it runs and said as held, with why, in the node's answer, never counted as removed and never stopped for it. Only a module the node runs that no assignment names is removed. +- **A-411** (A-408; live, the build node 2026-11-14 23:27-23:34: the builder's read of the stream `EVENTS` is refused, since + no module is granted that stream's details, by design; `versions-filled` is a kept seat event on its own stream, which the + builder consumes and is granted; principles 1 and 7) The builder reads the last `versions-filled` at its start from the + seat event's own kept stream, through the SDK's hearing of a kept event read from its first message, as any kept event + is heard; it reads nothing of `EVENTS` and needs no new grant. From ee543b86011c1661d4bdcd3b789af2343cf2e0c6 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 23:44:11 +0100 Subject: [PATCH 43/70] Answer A-412: the builder takes the entry's manifest digest bare, and a look that writes nothing says why --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 56d36d0e..71931431 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -993,3 +993,10 @@ the principle that settles it, cited as "design 47 G A-n". builder consumes and is granted; principles 1 and 7) The builder reads the last `versions-filled` at its start from the seat event's own kept stream, through the SDK's hearing of a kept event read from its first message, as any kept event is heard; it reads nothing of `EVENTS` and needs no new grant. +- **A-412** (live, the build node 2026-11-14 23:40-23:41: the builder's claim of every build is refused, "is not a manifest + digest, 64 lowercase hex digits", since the indexer's catalog entry now says its manifest digest as `sha256:` and hex, + and the builder passes it on as it reads it, while its builds and its manifests are keyed by bare hex; a build asked + again then answers "wrote nothing … its log says why" with no why; principles 3, 7 and 8) The builder takes a catalog + entry's manifest digest in its bare form, through the contract's own reading of it, wherever it plans, claims or keys + a build; the form the entry says is the entry's. A look that writes nothing says why in the builder's log, for each + of its ends, and the answer to a build asked again carries that why. From 16f4fd869650dc5d8ebe6ff217d715c583cf3712 Mon Sep 17 00:00:00 2001 From: jochen Date: Sat, 14 Nov 2026 23:44:50 +0100 Subject: [PATCH 44/70] Answer A-412a: the entry's digest readings live in the mesh-catalog contract --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 71931431..cc6a57bd 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1000,3 +1000,6 @@ the principle that settles it, cited as "design 47 G A-n". entry's manifest digest in its bare form, through the contract's own reading of it, wherever it plans, claims or keys a build; the form the entry says is the entry's. A look that writes nothing says why in the builder's log, for each of its ends, and the answer to a build asked again carries that why. +- **A-412a** (A-412; principles 1 and 7: the form of a seat's entry is its contract's) Both readings of an entry's + manifest digest (the entry's form and the bare one) move into the seat `mesh-catalog`'s contract package; the indexer + and the builder use them from there, and neither keeps its own. From 8b9b45085510b0c6b2fb685f5ca6613f694ff786 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 00:03:35 +0100 Subject: [PATCH 45/70] Answer A-413: named asks are unused only while no account the part composes may publish one --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index cc6a57bd..4d474380 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1003,3 +1003,9 @@ the principle that settles it, cited as "design 47 G A-n". - **A-412a** (A-412; principles 1 and 7: the form of a seat's entry is its contract's) Both readings of an entry's manifest digest (the entry's form and the bare one) move into the seat `mesh-catalog`'s contract package; the indexer and the builder use them from there, and neither keeps its own. +- **A-413** (§544 as G-12 answered it, A-170, A-231; live, the bus 2026-11-14 23:49: the builder of G asked 113 builds on + `accept.delivery.`, and no named worker exists to take them, since the grants part counts named asks unused while + no entry of the revision invokes a build seat's queue, and in the start no entry of G is in the revision yet; principles + 3 and 2) Named asks are unused only when no entry of the revision invokes a build seat's queue and no account the part + composes is granted to publish a named ask; while either holds, each build seat's queue keeps its named worker, made at + the part's next pass. The purge at a revert stays as §544 says, for a revision whose accounts ask no named ask. From 9da181e12d9157879e6047491f2fb0c6783ca3a5 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 00:23:25 +0100 Subject: [PATCH 46/70] Answer A-414: the grants part composes a module whose running build has no entry from its newest entry, as A-407 does for the node --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 4d474380..d8e78f12 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1009,3 +1009,10 @@ the principle that settles it, cited as "design 47 G A-n". 3 and 2) Named asks are unused only when no entry of the revision invokes a build seat's queue and no account the part composes is granted to publish a named ask; while either holds, each build seat's queue keeps its named worker, made at the part's next pass. The purge at a revert stays as §544 says, for a revision whose accounts ask no named ask. +- **A-414** (A-407, A-413; live, the bus 2026-11-15 00:17: after A-413 the grants part still made no named worker, since the + holders of the build seats, and the builder, run builds from before G with no catalog entry, so the part composes none of + them and carries their last memberships unchanged; the operator, 2026-11-15 about 00:20: "yes"; principles 2 and 7) The + grants part composes a running module whose wanted build has no catalog entry as A-407 describes it for the node: from + the catalog entry of the build its want says is being built (the newest of its first watched branch), read through the + seat `mesh-catalog`'s `entry` as any entry, for its account's grants, membership and seat traffic alone. A want that + names no newer build leaves its membership carried as today, said once. From 3d56f25942fc3af21734a3528b304ddac295163e Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 02:05:05 +0100 Subject: [PATCH 47/70] Answer A-415: a published heard before the build's digests is kept on its reservation and marks it when the digests land --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index d8e78f12..905941c0 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1016,3 +1016,11 @@ the principle that settles it, cited as "design 47 G A-n". the catalog entry of the build its want says is being built (the newest of its first watched branch), read through the seat `mesh-catalog`'s `entry` as any entry, for its account's grants, membership and seat traffic alone. A want that names no newer build leaves its membership carried as today, said once. +- **A-415** (§588, A-73; read from the code 2026-11-15 by the developer, the live proof waits on its new log lines: the + builder records a trunk build's digests on its reservation only after the build's claim is finished, while the registry + publishes during the build, so a registry seat's `published` heard before then marks nothing, is acknowledged and is + lost, and package-published is never said, as for 0.1.6; principles 1, 3 and 7) A `published` that marks no artifact + of its reservation yet is kept on that reservation, in the builder's own kept state, as heard (name, version, digest); + when the build records its digests, each kept `published` whose digest matches marks its artifact and package-published + is said then, in the same way as for one heard after. Nothing asks the registry; a kept `published` whose digest never + matches is said in the builder's log when the build records its digests. From 6c5f8aabb0372b45aeff52a0ba3b887e66ed8ddb Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 02:16:18 +0100 Subject: [PATCH 48/70] Answer A-416: the builder knows a registry seat's holder through FollowSeat, not from running events since its start --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 905941c0..fcc1116e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1024,3 +1024,10 @@ the principle that settles it, cited as "design 47 G A-n". when the build records its digests, each kept `published` whose digest matches marks its artifact and package-published is said then, in the same way as for one heard after. Nothing asks the registry; a kept `published` whose digest never matches is said in the builder's log when the build records its digests. +- **A-416** (§588, A-302, A-415; live, the build node 2026-11-15 02:02 and 02:16: `builder_publish_again` for + mesh-delivery-pipeline 0.1.6 queued nothing, "no module running that claims the registry seat oci-artifact-registry + is known to the builder since its start", since the builder learns a registry seat's holder only from node-engine + `running` events heard since it started, and that knowledge dies with every restart; principles 1, 4 and 7) The + builder knows each registry seat's holder through the SDK's FollowSeat, as A-302 has the indexer follow its seats, + from its start; a `running` heard still queues the versions waiting on that holder, as §588 says, but is no longer + how the holder is known. A publish again whose seat has no holder said by FollowSeat says so, naming the seat. From 39ab7efb6b32e8b6763faf69ef55dab1333b4b76 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 02:17:33 +0100 Subject: [PATCH 49/70] Answer A-416a: the builder reads a registry seat's holder from the catalog's seat holders, not FollowSeat --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index fcc1116e..baff782b 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1031,3 +1031,8 @@ the principle that settles it, cited as "design 47 G A-n". builder knows each registry seat's holder through the SDK's FollowSeat, as A-302 has the indexer follow its seats, from its start; a `running` heard still queues the versions waiting on that holder, as §588 says, but is no longer how the holder is known. A publish again whose seat has no holder said by FollowSeat says so, naming the seat. +- **A-416a** (A-416, A-298; principles 1 and 7: one source of who holds a seat, and nothing followed that nobody reads) + FollowSeat follows a state of a holder, and the registry seats keep none the builder reads; so the builder knows a + registry seat's holder from the seat-holders reading A-298 names (`SeatHolders` of the catalog client), the one its + FollowSeat of the assignments already takes, read from its start. Its manifest and grants do not change. A-416 is + read with "the SDK's FollowSeat" as this reading. From 2ce9268504c3431132b1f17fe8cf566db6f120b8 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 02:37:16 +0100 Subject: [PATCH 50/70] Answer A-417: a registry holder tags a version on the artifact it holds by digest, else takes it from the artifact store --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index baff782b..d5263087 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1036,3 +1036,12 @@ the principle that settles it, cited as "design 47 G A-n". registry seat's holder from the seat-holders reading A-298 names (`SeatHolders` of the catalog client), the one its FollowSeat of the assignments already takes, read from its start. Its manifest and grants do not change. A-416 is read with "the SDK's FollowSeat" as this reading. +- **A-417** (A-73, A-50, §588; live, the control-node 2026-11-15 01:57 and 02:28: the build node's publish of + mesh-delivery-pipeline 0.1.6 stores each artifact untagged, as A-73 has it, and the registry holds it, under the + artifact digest the builder reserved; the builder's publish of the version with that digest and no parts is then + refused, since the holder of `oci-artifact-registry` says published only for a tag it already holds and otherwise + opens a transfer with no parts; principles 3 and 7) A registry holder given a publish with a version, a digest and no + parts tags that version on the manifest it holds of that artifact digest under the name, and says published; when it + holds none, it takes the bytes from the artifact store by that digest, as A-73 and A-50 say, and stores and tags them; + when neither has it, it refuses as not stored, naming the digest. The builder's publish again names its transfer in + the transfer form the build's own step uses. From 1088d86e5c4a186f002d720326cc85984bf5a59d Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 02:59:19 +0100 Subject: [PATCH 51/70] Answer A-418: a bundle's or archive's name for reserved is / from its entry's artifact reference --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index d5263087..aa5236cf 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1045,3 +1045,10 @@ the principle that settles it, cited as "design 47 G A-n". holds none, it takes the bytes from the artifact store by that digest, as A-73 and A-50 say, and stores and tags them; when neither has it, it refuses as not stored, naming the digest. The builder's publish again names its transfer in the transfer form the build's own step uses. +- **A-418** (§478, §676, §694, A-417; live, the control-node 2026-11-15 02:57: the tag of mesh-delivery-pipeline 0.1.6 is + refused since the builder's `reserved` answers "no entry carries the name mesh-delivery-pipeline/program": it matches a + name only against an artifact's `package`, which a bundle or an archive has none of, so no bundle is ever found; + principles 7 and 8) A bundle's or an archive's name for `reserved` is `/`, read from its catalog + entry's artifact reference (`:`), the name the build step and the builder publish it under; the + entry stays the one source of the name, and no `package` is added to it. A name that matches no entry is said in the + builder's log with the entries looked at. From 1de67e76ed71e047f20bde58fe4f55817de7c7b4 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 03:14:06 +0100 Subject: [PATCH 52/70] Answer A-419 (release matched by the fingerprint's source) and A-420 (a message given up is said) --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index aa5236cf..0250e72b 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1052,3 +1052,14 @@ the principle that settles it, cited as "design 47 G A-n". entry's artifact reference (`:`), the name the build step and the builder publish it under; the entry stays the one source of the name, and no `package` is added to it. A name that matches no entry is said in the builder's log with the entries looked at. +- **A-419** (A-96, A-67; read from the code 2026-11-15: the assigner finds a trunk build's released version and parts by + its module and the source revision of the kept assignment graph, so after any merge that does not rebuild a module, + its wants and candidates carry no version and no parts; principles 2 and 7) A trunk build's release is matched by its + module and the source revision its fingerprint was built at, read from its catalog entry's `fp-src`, which is + `version-released.source` for that build; A-96's "matched to `version-released.source`" is read so. A want or a + candidate whose entry's release is not heard says so, naming the module, the fingerprint and that source. +- **A-420** (principle 3; the builder and the indexer hear their events with five deliveries, and the bus drops a message + after the fifth without either saying so) On the last delivery its consumer allows, the builder and the indexer each + say in their log that they give the message up, naming its subject, the artifact and version it carries, and the + last refusal. (Quick fix, said: the same silence holds for every part that hears an event; the thorough fix is the + SDK's hearing saying it once for every part, noted on the issue of the hand start.) From 9a60a312a031ef5aa8216faa457ea48d7f655533 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 03:17:45 +0100 Subject: [PATCH 53/70] Answer A-421: a trunk entry with no fp-src is matched to its release by the digests its build made --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 0250e72b..c841f2d0 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1063,3 +1063,8 @@ the principle that settles it, cited as "design 47 G A-n". say in their log that they give the message up, naming its subject, the artifact and version it carries, and the last refusal. (Quick fix, said: the same silence holds for every part that hears an event; the thorough fix is the SDK's hearing saying it once for every part, noted on the issue of the hand start.) +- **A-421** (A-419, ADR 0601 §1; read live 2026-11-15: six entries of trunk revision 225 carry no `fp-src`, since a + fingerprint that moves without a merge clears it, so A-419 finds no release for them; principles 2, 3 and 7) A trunk + entry with no `fp-src` is matched to the release whose parts' digests are the digests its fingerprint's `build.ended` + made, as the assigner already hears it; an entry with `fp-src` is matched as A-419 says. An entry neither finds is + said as A-419 says, with which of the two was tried. From 17ab2d028e5aea2497be76f5610edd54ecaff3d6 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 03:48:47 +0100 Subject: [PATCH 54/70] Answer A-422: the SDK's event hub binds the kept seat streams in its own start --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index c841f2d0..e13b2c03 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1068,3 +1068,11 @@ the principle that settles it, cited as "design 47 G A-n". entry with no `fp-src` is matched to the release whose parts' digests are the digests its fingerprint's `build.ended` made, as the assigner already hears it; an entry with `fp-src` is matched as A-419 says. An entry neither finds is said as A-419 says, with which of the two was tried. +- **A-422** (A-397; live, the bus 2026-11-15 03:45: the indexer, the assigner, the checker, the teller, the forge bridge, + the view, distribution and nats each have a durable on a kept seat stream their manifest consumes that was never + delivered, since only the builder binds its kept streams; the indexer never heard a package-published; principles 1, + 3 and 7) The SDK's event hub binds a part's kept seat streams in its own start, after the stream `EVENTS`, so every + part hears each kept event its manifest consumes on its own durable there, as A-397 says, with no call of its own; + a stream it cannot bind is said in its log and its start goes on. The replay of what waited is heard as any event; + a part whose handler cannot take its backlog is a finding of the change, read before its delivery. (Thorough fix, + said: the indexer's own call, b0242f68, is the quick fix placed meanwhile.) From f0b9c73a9f2efa3cffc6a287ea22166672e1aa4f Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 03:52:41 +0100 Subject: [PATCH 55/70] Answer A-423: one reader per durable through the hub; a consumed kept event with no route is said --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index e13b2c03..558c6db8 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1076,3 +1076,10 @@ the principle that settles it, cited as "design 47 G A-n". a stream it cannot bind is said in its log and its start goes on. The replay of what waited is heard as any event; a part whose handler cannot take its backlog is a finding of the change, read before its delivery. (Thorough fix, said: the indexer's own call, b0242f68, is the quick fix placed meanwhile.) +- **A-423** (A-397, A-422; read from the code 2026-11-15: the assigner reads machine-away and machine-back, and the forge + bridge branch-moved, with readers of their own on the durable the hub now binds too, so each message would reach one + of the two; and the checker, the forge bridge, the view and distribution consume registration-changed in their + manifests with no route, so its durable fills unread; principles 1, 3 and 7) One reader per durable: the hub is the + only reader of a part's kept streams, and a part that read one itself hands its handler to the hub, which gives each + event to every handler it has for it. A kept event a part's manifest consumes and no route takes is said at its start, + naming the event, as a fault of the part to be fixed in its manifest or its code. From fd45f0192971f09fc12baa023ed1782a265b731b Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 15:49:03 +0100 Subject: [PATCH 56/70] Answer A-424: the operator channel keeps no limit of open asks per asker (the operator, 2026-11-15) --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 558c6db8..26053882 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1083,3 +1083,8 @@ the principle that settles it, cited as "design 47 G A-n". only reader of a part's kept streams, and a part that read one itself hands its handler to the hub, which gives each event to every handler it has for it. A kept event a part's manifest consumes and no route takes is said at its start, naming the event, as a fault of the part to be fixed in its manifest or its code. +- **A-424** (§394, §450, A-423; the operator, 2026-11-15 about 15:50 CET: "there is no limit for the amount of asks in my + telegram", said many times before; live: the teller held the pipeline's proposal ask behind two week-old asks, since + an asker may have at most three asks open; principles 3 and 7) The operator channel keeps no count of open asks per + asker and holds none back for room: every ask is offered when it is raised. The router's limit, the teller's own and + the ask-again for a held-back ask (§394, §450) go; an ask still lapses at its expiry or ends at its answer. From f988c23d1e4852423e972f28980d22e72d97497b Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 15:54:46 +0100 Subject: [PATCH 57/70] Answer A-425: a passing placement proposal is applied without the operator's ask (the operator, 2026-11-15) --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 26053882..fb8429a5 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1088,3 +1088,11 @@ the principle that settles it, cited as "design 47 G A-n". an asker may have at most three asks open; principles 3 and 7) The operator channel keeps no count of open asks per asker and holds none back for room: every ask is offered when it is raised. The router's limit, the teller's own and the ask-again for a held-back ask (§394, §450) go; an ask still lapses at its expiry or ends at its answer. +- **A-425** (the operator, 2026-11-15 about 15:57 CET: "yes, remove the per-placement approve", after the lead proposed + it under propose-removing-a-wrong-rule: a person's yes for every placement holds work on a form, against "merges and + deliveries need no approval"; principles 3 and 7) A proposal whose verdict passes is applied by the assigner at once, + with no ask of the operator, when it only places, pins, unpins, holds, unholds, decides or configures. A proposal + that takes a module off a node, removes a node, or whose verdict says a node would stop or remove a module or its data, + is still asked of the operator, as are the asks of a module whose moves a person takes. Each applied proposal is said + as an event and in the assigner's log, naming who proposed it and why. The decision record that made every proposal + wait on the operator's yes gets a new record saying so once the knowledge base admits callers again. From 8abbb539fd886aabb149c4527ca3903083a73d61 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 15:55:34 +0100 Subject: [PATCH 58/70] Answer A-425a: which proposals are asked is the assigner's config key ask-operator-for --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index fb8429a5..5d89cc6e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1096,3 +1096,11 @@ the principle that settles it, cited as "design 47 G A-n". is still asked of the operator, as are the asks of a module whose moves a person takes. Each applied proposal is said as an event and in the assigner's log, naming who proposed it and why. The decision record that made every proposal wait on the operator's yes gets a new record saying so once the knowledge base admits callers again. +- **A-425a** (A-425; the operator, 2026-11-15 about 16:00 CET: "this is all configuration, a simple, single mesh mcp + call"; read live: the assigner declares only `outside-settle-seconds` and `outside-wait-minutes`, and asks every + passing proposal in its code; principles 4 and 7) Which proposals the assigner asks of the operator is the assigner's + declared config key `ask-operator-for`, a list of change kinds (`place`, `take-off`, `pin`, `unpin`, `hold`, + `unhold`, `decide`, `config`, `add-node`, `remove-node`, and `stops` for a verdict that stops or removes a module or + its data), set at mesh level with `mesh-config.config`; its default is A-425's: `take-off`, `remove-node`, `stops`. + A proposal none of whose changes is listed is applied at once. The asks of a module whose moves a person takes stay + as they are. A change of the key is said in the assigner's log at its next pass. From b20b382cd979f926847e31134d571f711b42af29 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 15:56:51 +0100 Subject: [PATCH 59/70] Answer A-426 (an acting wait ends on any running build that serves the edge) and A-427 (a put may hold the running build) --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 5d89cc6e..ae2d6774 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1104,3 +1104,12 @@ the principle that settles it, cited as "design 47 G A-n". its data), set at mesh level with `mesh-config.config`; its default is A-425's: `take-off`, `remove-node`, `stops`. A proposal none of whose changes is listed is applied at once. The asks of a module whose moves a person takes stay as they are. A change of the key is said in the assigner's log at its next pass. +- **A-426** (§268, A-323, A-330; live, the build node and ace 2026-11-15 15:52-15:56: the pipeline's want on novox + waited for an assigner build not yet built, while a working assigner ran, and only a hand release moved it; the + operator: "then our design is stupid"; principles 2, 3 and 7) An acting wait waits only while its acting part runs + nothing that serves the edge: an acting part that runs a build serving the edge's seat or verb ends the wait at + once, whatever version its newest is, and the wait says which build it took. A wait on a version not yet built is + never held for that alone. (This replaces the node-engine exemption of A-323 and A-330 with a rule for every part.) +- **A-427** (A-426; live: the builder refuses a put of a version it did not build, so a part started by hand cannot be + held, and the trunk's newest build of it would replace it; principles 2 and 4) A put may name the build a node + runs now, read from the node's running statement, and holds the want there; the builder's store is not asked for it. From aad8f7c921680a1677b5879a40c2d6bdb29e75fb Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:03:56 +0100 Subject: [PATCH 60/70] Answer A-428: with no pipeline runner running, wants do not wait for a passed pipeline --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index ae2d6774..473c0550 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1113,3 +1113,10 @@ the principle that settles it, cited as "design 47 G A-n". - **A-427** (A-426; live: the builder refuses a put of a version it did not build, so a part started by hand cannot be held, and the trunk's newest build of it would replace it; principles 2 and 4) A put may name the build a node runs now, read from the node's running statement, and holds the want there; the builder's store is not asked for it. +- **A-428** (§29, A-328; read from the code 2026-11-15 16:05: a want follows a passed pipeline, and no pipeline can + pass while no holder of the seat `mesh-pipeline-runner` runs, so the runner itself, and every module whose + fingerprint moved, never gets a want; the gate returned before the want rules without a word; principles 3 and 7) + While no module holding `mesh-pipeline-runner` runs on any node, a want does not wait for a passed pipeline: the + assigner writes wants from the trunk's entries by its other rules, and says once that it does and why. As soon as a + runner runs, wants follow passed pipelines again, from the next pass. (Whether a want waits for a passed pipeline at + all is a gate for the generic gating research to make configured.) From cac334e749b8890b74972ae915b5b66072fdec0e Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:04:05 +0100 Subject: [PATCH 61/70] Narrow A-428: only the pipeline runner's own want skips the passed-pipeline gate while no runner runs --- .../01-to-be/47-milestones/G-22-lead-answers-2.md | 13 +++++++------ 1 file changed, 7 insertions(+), 6 deletions(-) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 473c0550..4971e8fa 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1114,9 +1114,10 @@ the principle that settles it, cited as "design 47 G A-n". held, and the trunk's newest build of it would replace it; principles 2 and 4) A put may name the build a node runs now, read from the node's running statement, and holds the want there; the builder's store is not asked for it. - **A-428** (§29, A-328; read from the code 2026-11-15 16:05: a want follows a passed pipeline, and no pipeline can - pass while no holder of the seat `mesh-pipeline-runner` runs, so the runner itself, and every module whose - fingerprint moved, never gets a want; the gate returned before the want rules without a word; principles 3 and 7) - While no module holding `mesh-pipeline-runner` runs on any node, a want does not wait for a passed pipeline: the - assigner writes wants from the trunk's entries by its other rules, and says once that it does and why. As soon as a - runner runs, wants follow passed pipelines again, from the next pass. (Whether a want waits for a passed pipeline at - all is a gate for the generic gating research to make configured.) + pass while no holder of the seat `mesh-pipeline-runner` runs, so the runner itself never gets a want; the gate + returned before the want rules without a word; principles 3 and 7) While no module holding `mesh-pipeline-runner` + runs on any node, a want of a module whose manifest claims `mesh-pipeline-runner` does not wait for a passed + pipeline: the assigner writes it from the trunk's entry by its other rules, and says once that it does and why. + Every other module still waits for a passed pipeline, so nothing else moves before a runner runs; once one runs, + A-328 has the runner's own changes pass on it. (Whether a want waits for a passed pipeline at all is a gate for the + generic gating research to make configured.) From 14c3e90332f11b10d14af16ce17a70fdefe45681 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:13:29 +0100 Subject: [PATCH 62/70] Answer A-429: a released build is done for rule 1 --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 4971e8fa..22940906 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1121,3 +1121,9 @@ the principle that settles it, cited as "design 47 G A-n". Every other module still waits for a passed pipeline, so nothing else moves before a runner runs; once one runs, A-328 has the runner's own changes pass on it. (Whether a want waits for a passed pipeline at all is a gate for the generic gating research to make configured.) +- **A-429** (§379, A-421; live 2026-11-15 16:07: the assigner's rule 1 said a released build "is being built", since + it knew build ends only from a stream it read from its start on, kept by age, not one per subject as the builder's + manifest declares; principles 2 and 7) A build whose version is released (`version-released` heard for its + fingerprint's parts) is done for rule 1, as §379 takes its parts from that event; `build.ended` counts for a build + not released (another watched branch, a kept build). The assigner reads the builder's build ends whole at its start. + That the bus keeps that stream by age, not one per subject as declared, is a fault of the grants part, noted. From ee80b4d84bf1936be3dd62098e60910bee11c0a8 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:17:01 +0100 Subject: [PATCH 63/70] Answer A-426a: every rule waiting on a serving part counts any healthy running build that serves it --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 22940906..e2787a88 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1127,3 +1127,10 @@ the principle that settles it, cited as "design 47 G A-n". fingerprint's parts) is done for rule 1, as §379 takes its parts from that event; `build.ended` counts for a build not released (another watched branch, a kept build). The assigner reads the builder's build ends whole at its start. That the bus keeps that stream by age, not one per subject as declared, is a fault of the grants part, noted. +- **A-426a** (A-426, ADR 0614 §2; live 2026-11-15 16:15: rule 8 holds the pipeline runner's want, "the verb + seat:mesh-hand-acts.hand-act mesh-delivery-pipeline invokes is served by no running build", while mesh-hand-acts runs + on the control-node and serves that verb with a build from before G; principles 2, 3 and 7) A-426 holds for every + rule that waits on another part, the acting waits and rule 8 (an invoked verb served) alike: a part counts as + serving when a node runs a build of it that serves the seat or verb and is healthy, from its running statement and + the tool runner's announcement, whatever its version and whether or not the catalog lists that build. The rule says + which build it counted. From d2094f657e3667ef8b15aa2db358804fb3b89617 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:43:23 +0100 Subject: [PATCH 64/70] Answer A-430: a want names the module version; the node-engine fetches the artifacts by that version (the operator) --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index e2787a88..04b8478f 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1134,3 +1134,10 @@ the principle that settles it, cited as "design 47 G A-n". serving when a node runs a build of it that serves the seat or verb and is healthy, from its running statement and the tool runner's announcement, whatever its version and whether or not the catalog lists that build. The rule says which build it counted. +- **A-430** (§379, §525, §526; the operator, 2026-11-15 about 16:45 CET: "the artifacts simply carry the module + version of course, why would a module have a version otherwise"; principles 6 and 7) A want names the module and its + released version (and the kept-on node for a kept build), never its artifacts' digests: the node-engine fetches each + artifact the module's catalog entry names under that version from the registry seat that holds it, as the registry + tags it, and the registry's answer is what it applies. §379's digests in the want, and the assigner's check whether + a node's node-engine reads them (`want-parts`), go. A build of another watched branch, which has no released + version, is named by the version the builder numbered it under. From 547eec3373fecfa4544d51975434da7da613c790 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:44:17 +0100 Subject: [PATCH 65/70] Answer A-430a: every wanted build has a version; the node-engine resolves artifacts by version through the registry's versions verb --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 04b8478f..08cf63a9 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1141,3 +1141,11 @@ the principle that settles it, cited as "design 47 G A-n". tags it, and the registry's answer is what it applies. §379's digests in the want, and the assigner's check whether a node's node-engine reads them (`want-parts`), go. A build of another watched branch, which has no released version, is named by the version the builder numbered it under. +- **A-430a** (A-430; principles 7 and 8) Every build a want names has a version: a released trunk build its released + version, a build of another watched branch the version the builder numbered it under (A-430), and a kept build its + numbered version with `kept-on` naming the node that keeps it (§526); a want never names a fingerprint's artifacts + or digests. The node-engine resolves each artifact the catalog entry names at that version through the seat that + holds its kind (`oci-artifact-registry` for a bundle or archive, `container-image-registry` for an image), by its + verb `versions` with the artifact's registry name `/`, and fetches the bytes as today over the + artifact store by the digest that answer gives; an image is pulled by name and version. The node-engine's manifest + invokes those `versions` verbs; no registry verb is added. From 09cf7d609da7aef807c8682dee4dd327eff510c3 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 16:48:29 +0100 Subject: [PATCH 66/70] Answer A-430b: a branch build is named by the version the builder reserved; build.ended carries it and the registry tags it unreleased --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 08cf63a9..43dfbf48 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1149,3 +1149,11 @@ the principle that settles it, cited as "design 47 G A-n". verb `versions` with the artifact's registry name `/`, and fetches the bytes as today over the artifact store by the digest that answer gives; an image is pulled by name and version. The node-engine's manifest invokes those `versions` verbs; no registry verb is added. +- **A-430b** (A-430a, §52, §53, §371; principles 7 and 8) The version a build of another watched branch is numbered + under is the one the builder reserved when its build started (§52), never released: `build.ended` names it as + `version` for every build that reserved one, and the registry seat that holds each artifact tags a branch build's + artifact at that reserved version without releasing it, so the node-engine resolves it through `versions` like a + released one. §371's and §53's "stored by digest with no version" becomes "tagged at its reserved version, + unreleased"; the `package-published` comparison by digest stays. Order within G: the node-engine's resolution by + version first (it unblocks every released build), then the builder and registry tagging; until those land, a want + for a branch build keeps its digests for a node whose node-engine reads them, and that form goes with them. From 2829a47ea0fdd102a41e7ad875ad14661255d288 Mon Sep 17 00:00:00 2001 From: jochen Date: Sun, 15 Nov 2026 17:51:01 +0100 Subject: [PATCH 67/70] Answer A-431: a take-in names the source revision it makes, one above the newest seen or said --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 43dfbf48..e6ae70d3 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1157,3 +1157,10 @@ the principle that settles it, cited as "design 47 G A-n". unreleased"; the `package-published` comparison by digest stays. Order within G: the node-engine's resolution by version first (it unblocks every released build), then the builder and registry tagging; until those land, a want for a branch build keeps its digests for a node whose node-engine reads them, and that form goes with them. +- **A-431** (§476, §493, §648, A-34; live 2026-11-15 17:44: the pipeline runner heard eight `take-in.taken` with no + branch and no source revision, started no pipeline and asked each again for ever; principle 7) The source revision a + take-in names is one above the newest the indexer has seen of that branch (the gate's `source-moved`) or named in an + earlier `take-in.taken`; the gate's `source.` then moves to it (A-34). Every taken event of one take-in carries + the same `branch`, `source` and `entries`, so a reader keyed by branch and source revision (the runner, the gate) + acts once; a taken event that took nothing in (a group's end, one said before G) carries none, and the runner writes + it in its journal and lets it go (§493). From d9dd5dab67a2cba74d58e10cd160340e53d0ec2d Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 01:00:35 +0100 Subject: [PATCH 68/70] =?UTF-8?q?Answer=20A-432:=20a=20runtime=20of=20its?= =?UTF-8?q?=20own=20runs=20the=20tool=20runner's=20program,=20which=20?= =?UTF-8?q?=C2=A7524's=20check=20of=20the=20module's=20parts=20leaves=20ou?= =?UTF-8?q?t?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index e6ae70d3..177a8b2e 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1164,3 +1164,8 @@ the principle that settles it, cited as "design 47 G A-n". the same `branch`, `source` and `entries`, so a reader keyed by branch and source revision (the runner, the gate) acts once; a taken event that took nothing in (a group's end, one said before G) carries none, and the runner writes it in its journal and lets it go (§493). +- **A-432** (§524, ADR 0259 §8; principle 7) A module of its own account is run by a runtime of its own, a process + whose program is the tool runner's build, not the module's: the check of §524 leaves that process out, and the tool + runner's own want checks its program. Every other archive, process and container of the module's composition is + checked against its want's `parts` as §524 says. (novox, 2026-11-16 01:00 CET: the new indexer was held + "parts-differ: fetched and not in the want's parts" for the tool runner's program.) From 4169ded5cdcdf86f12fb7e8bc9895ebf560bc2dc Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 02:34:22 +0100 Subject: [PATCH 69/70] Answer A-433: before the catalog half is read, a module account's call runs unmarked, seat verbs too --- 03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 177a8b2e..91be2137 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -1169,3 +1169,9 @@ the principle that settles it, cited as "design 47 G A-n". runner's own want checks its program. Every other archive, process and container of the module's composition is checked against its want's `parts` as §524 says. (novox, 2026-11-16 01:00 CET: the new indexer was held "parts-differ: fetched and not in the want's parts" for the tool runner's program.) +- **A-433** (A-389, §19; principle 6) While its catalog half is unread, a tool runner runs unmarked every call whose proven + caller is a module's account, a seat verb as a module tool, and a module's own call in a runtime of its own; it holds the + console's account (the one sessions and agents call as), a person, the controller and an unproven caller as before. + Approval marks are for agent calls; inside the mesh a module may do everything. (novox, 2026-11-16 02:35 CET: the + indexer's runtime of its own refused its own `mesh-catalog.revision`, the very first view it waits on, so every reader + of the catalog waited for ever.) From 91f60c707526deab95e2a9fe2d4abf1a03cc6163 Mon Sep 17 00:00:00 2001 From: jochen Date: Mon, 16 Nov 2026 09:24:19 +0100 Subject: [PATCH 70/70] Use the glossary's words in lead answers 31, so the words test passes --- .../47-milestones/G-22-lead-answers-2.md | 28 +++++++++---------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md index 91be2137..ab0cda64 100644 --- a/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md +++ b/03-DESIGN/01-to-be/47-milestones/G-22-lead-answers-2.md @@ -802,7 +802,7 @@ the principle that settles it, cited as "design 47 G A-n". among their callers, so its keeper reads the catalog holder's manifest. - **A-379** (replaces A-376 and A-378 for the start: the indexer's `catalog-revisions` is declared in its manifest's old `objects` section, which grants creates (records.go objectsOf, assertions.go), while the tool runner reaches an - object store only by a new-form binding (node-tools internal/bus/bindings.go objectStore), so nothing binds it; + object store only by a new-form binding (`node-tools` internal/bus/bindings.go objectStore), so nothing binds it; principle 7: what exists) The tool runner reaches a module's object store by the binding when one is bound, and otherwise by the old `objects` entry its membership names, under the bus name grants created for it (`OBJ__`); a name neither names stays refused as today. @@ -817,10 +817,10 @@ the principle that settles it, cited as "design 47 G A-n". composed with the create rights of A-364. - **A-382** (widens A-381 to its kind, met a second time: live 00:02, every G bundle with a finding writer exits "no stream on the bus carries mesh-conditions.findings-asked", because the tool runner's SubscribeNew finds a stream by subject - through `$JS.API.STREAM.NAMES`, which novox.node-tools may not publish, while EVENTS carries `mesh.seat.*.event.>`; + through `$JS.API.STREAM.NAMES`, which `novox.node-tools` may not publish, while EVENTS carries `mesh.seat.*.event.>`; principles 7 and 6) Every account grants composes carries `$JS.API.STREAM.NAMES`, the read of stream names by subject that hearing an event starts with; it lists names only. -- **A-383** (completes A-382; live 00:21: list revision 274 loaded, yet novox.node-tools still lacks +- **A-383** (completes A-382; live 00:21: list revision 274 loaded, yet `novox.node-tools` still lacks `$JS.API.STREAM.NAMES` (1805 publish rights, unchanged), since grants keeps an account it holds "beyond this pass" as the list in force while the catalog half is unread; principles 7 and 3) A right every account carries (A-382) is added to every account grants writes, a kept one included: keeping an account in force never withholds what every account @@ -828,16 +828,16 @@ the principle that settles it, cited as "design 47 G A-n". - **A-384** (completes A-382/A-383 for the whole hearing path, met a third time: live 00:35 "an ordered consumer of mesh-conditions.findings-asked on EVENTS: context deadline exceeded", the runner account holds only INFO of named durables on EVENTS; principles 6 and 7) Every tool runner account carries what the runner's SubscribeNew (an ordered consumer from - the next message, mesh-tools node-tools internal/bus/subscribenew.go) asks of the stream that carries the events its + the next message, mesh-tools `node-tools` internal/bus/subscribenew.go) asks of the stream that carries the events its bundles hear: the create of an unnamed consumer filtered to those events' subjects, its next-message fetch, its info and its delete, on EVENTS and on every kept seat stream; the same form for every runner, composed in one place. - **A-385** (generalizes A-383, met a fourth time: live 01:00 "mesh-delivery-gate's bundle asked mesh/ledger.get and it - failed after 10s", the gate's ledger `records` exists and is bound, and novox.node-tools holds no right on + failed after 10s", the gate's ledger `records` exists and is bound, and `novox.node-tools` holds no right on KV_mesh-delivery-gate_records_state, since a held runner account is copied whole from the list in force; principles 7 and 3; A-363's union) An account grants keeps beyond a pass, a runner's included, is written as the union of the list in force and what this pass composes for it (its carried modules' grants from the trunk's manifests and their bindings), never the list in force alone; a pass that only adds still never takes from a loaded user. -- **A-386** (completes A-385 for runners kept as they run; live 01:31: grants 3c582b1b in, novox.node-tools unchanged +- **A-386** (completes A-385 for runners kept as they run; live 01:31: grants 3c582b1b in, `novox.node-tools` unchanged (2004 publish rights, none on KV_mesh-delivery-gate_records_state), since `runnerUsersKept` keeps a runner whose running manifest does not say it is the tool runner whole (ADR 0601 §4); principles 7 and 3) A runner kept as it runs is written as the union of the list in force and the runner grants its carried modules' bindings and events give (the ledger @@ -850,7 +850,7 @@ the principle that settles it, cited as "design 47 G A-n". every verb that the seat definition the runner holds classes `read` and does not mark needs-approval, and judges every other call as before; the hand-kept list `startReads` goes. The bootstrapped definitions carry every seat the first take-in reaches: `git` joins them, a byte-for-byte copy of its contracts file with its row in the bootstrap test. The - catalogue seat's contract classes `modules`, `module`, `provides`, `dependents` and `seat-definitions` as `read`, and + catalog seat's contract classes `modules`, `module`, `provides`, `dependents` and `seat-definitions` as `read`, and its bootstrapped copy follows. - **A-388** (completes A-387; the developer's question: seatdef callers.go reads a verb with no class as a read, which would let unclassed acts such as `mesh-delivery-checker.try` and `operator-channel.tell` through before the catalog @@ -861,12 +861,12 @@ the principle that settles it, cited as "design 47 G A-n". `mesh-delivery-forge-bridge.bridge_merged_message` is refused "the marks of mesh-delivery-forge-bridge are not read yet"; a module tool names no class, and its marks live only in the catalog half's entry the take-in has not made yet; principles 7 and 3) Before the catalog half is read, a module tool whose proven caller is another module's account (never - a session's or the console's) runs unmarked, and the runner logs each such call once per tool with its caller ("run + a session's or the mesh MCP server's) runs unmarked, and the runner logs each such call once per tool with its caller ("run unmarked before the catalog half is read"); a module tool called otherwise waits and is judged as before. A module tool's mark is read again, and holds, from the call after the half is read. Today the one marked module tool, `gitea_branch_protection_loosen`, has no module among its callers. - **A-390** (live 03:17 on novox: the tool runner's first view of the catalog half is refused "mesh-catalog.revision is - refused to novox.node-tools: the tool answers only mesh-delivery-builder"; node-tools declares `invokes: ["*"]`, and + refused to `novox.node-tools`: the tool answers only mesh-delivery-builder"; `node-tools` declares `invokes: ["*"]`, and the verb revision's callers rule (ADR 0663 §2) matches `seat:mesh-catalog.revision` by its exact text alone, while the grants part reads a single `*` as every seat verb; principles 7 and 3) The verb revision's callers are the parts whose entry in the newest trunk revision declares `seat:mesh-catalog.revision` or a single `*` in invokes, as the grants part @@ -926,7 +926,7 @@ the principle that settles it, cited as "design 47 G A-n". assignment graph's requirement resolution and the order waits keep reading holders from the holds alone; the post-G remarks take that up with the rest of the holders question. - **A-401** (live, the control-node 2026-11-14 21:5x: the assigner ended every proposal, since f1-circuits (watched on - master), link2pay and photos (watched on nox-mesh) are held in no catalog graph of their branch; the gate writes + `master`), link2pay and photos (watched on nox-mesh) are held in no catalog graph of their branch; the gate writes `source.` only on a take-in of a merge on that branch (A-34), so a newly watched branch is never started; the operator, 2026-11-14 about 22:00: "by doing a git clone"; principles 2, 4 and 7, §15, §430, A-85, A-93) A watched branch starts from the forge, as a clone does. The gate, at its start and on each `registration-changed` of the seat @@ -952,16 +952,16 @@ the principle that settles it, cited as "design 47 G A-n". key or added to a held one, names no group, as A-401's new key does: no group moved it, so nothing times it as a group's; the key keeps the group a take-in last wrote. - **A-405** (live, the control-node 2026-11-14 22:34: its node-engine refused every candidate, "nothing provides" postgres-database, - secret, route, s3-bucket, document-server and mcp-endpoint, since its catalogue holds only modules whose wanted build has a + secret, route, s3-bucket, document-server and mcp-endpoint, since its catalog holds only modules whose wanted build has a catalog entry, and the providers' wants name the builds running from before G, which have none, their new builds waiting for a pipeline that cannot be placed while the node refuses; the operator, 2026-11-14 about 22:40: "yes, go ahead"; - principles 2 and 7, §421) A module the node runs whose wanted build has no catalog entry stays in the node's catalogue as + principles 2 and 7, §421) A module the node runs whose wanted build has no catalog entry stays in the node's catalog as the build it runs, from the manifest of that build the node keeps: it provides, claims and requires what that manifest says, so the node resolves around it. Its want stays held with `entry-missing` (§421) and nothing new of it is composed; when its new build's entry comes, it is composed as any other. - **A-406** (live, the control-node 2026-11-14 22:34: the pipeline's manifest at its build was refused by the manifest judge on 2026-11-13, and its candidate carried no parts; the operator, as for A-405; principles 5 and 7) The pipeline's manifest is - made to pass the judge, as any module's; its first build is asked of the builder once by hand, the way a run on request + made to pass the validator, as any module's; its first build is asked of the builder once by hand, the way a run on request asks it, since only a pipeline asks builds and none runs yet. - **A-407** (A-405; principles 7 and 2: the node keeps no manifest of a build that has no entry, and the running event carries only a digest) A running module whose wanted build has no entry is described from the catalog entry of the build @@ -1171,7 +1171,7 @@ the principle that settles it, cited as "design 47 G A-n". "parts-differ: fetched and not in the want's parts" for the tool runner's program.) - **A-433** (A-389, §19; principle 6) While its catalog half is unread, a tool runner runs unmarked every call whose proven caller is a module's account, a seat verb as a module tool, and a module's own call in a runtime of its own; it holds the - console's account (the one sessions and agents call as), a person, the controller and an unproven caller as before. + mesh MCP server's account (the one sessions and agents call as), a person, the controller and an unproven caller as before. Approval marks are for agent calls; inside the mesh a module may do everything. (novox, 2026-11-16 02:35 CET: the indexer's runtime of its own refused its own `mesh-catalog.revision`, the very first view it waits on, so every reader of the catalog waited for ever.)