Issue 526; ADR 0305 (proposed, needs the operator's Approve; do not merge before it is accepted).
What changes
catalogue: an offer may say "credential": {"issued-by": "software", "tool": "<tool>"} (no own secret); the parser refuses both, another issuer, or no tool. IssuedCredentialOf.
New verb issued (secret issued <provision>): carries no value, answers none. For each machine providing the provision to a pair the mesh holds, it asks the provider's named tool on that machine in the controller's own name (the caller-named call subject, issue 365) with a one-time sealing key, opens the answer, seals it to every pair that does not hold it yet under one stamp of its fingerprint (and to the operator), and sends the provider's and those consumers' machines. A pair that already holds the value is not touched, so an hourly ask restarts nothing.
terminalOnly: secret issued <provision> joins rotate and the desk's ask as the secret lines a verb runs (ADR 0305 §10).
rotate of such a provision is refused (§9). Hand-act table: secret issued is a decision, not a repair (§8). take shows an issued pair as carried in.
link.AskModuleToolOnAs: a module tool asked on the subject that names its caller.
No migration: secret.origin takes issued, secret.generation holds the stamp (both columns exist).
Tests (fail on main: they do not compile there): internal/catalogue TestAnOfferMaySayItsSoftwareIssuesTheCredential; cmd/mesh-controller issued_test.go (verb line, terminal rule, sealed-to-call only, unchanged sends nobody, rotate refused, hand-act decision, manifest serves every verb); store test ./internal/inventory TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain, listed in testdata/store-tests — not run here (no store); the build seat's repo-check runs it.
Run here: gofmt, go vet ./..., go test -race -count=1 ./... green (store tests skip without a store).
Order: this first; then mesh-media-catalog's plex change (its manifest says issued-by, which today's controller refuses). The verb needs node-tools that serve the call subjects (mesh-tools #27) on the provider's machine.
Reviewer checklist: no value or fingerprint in any answer, log or hand-act; the verb's argv is exactly secret issued <provision>; only stale pairs are resealed; rotate refusal; the store test's SQL against the secret table.
Issue 526; ADR 0305 (proposed, needs the operator's Approve; do not merge before it is accepted).
**What changes**
- `catalogue`: an offer may say `"credential": {"issued-by": "software", "tool": "<tool>"}` (no own secret); the parser refuses both, another issuer, or no tool. `IssuedCredentialOf`.
- New verb `issued` (`secret issued <provision>`): carries no value, answers none. For each machine providing the provision to a pair the mesh holds, it asks the provider's named tool on that machine **in the controller's own name** (the caller-named `call` subject, issue 365) with a one-time sealing key, opens the answer, seals it to every pair that does not hold it yet under one stamp of its fingerprint (and to the operator), and sends the provider's and those consumers' machines. A pair that already holds the value is not touched, so an hourly ask restarts nothing.
- `terminalOnly`: `secret issued <provision>` joins `rotate` and the desk's `ask` as the `secret` lines a verb runs (ADR 0305 §10).
- `rotate` of such a provision is refused (§9). Hand-act table: `secret issued` is a decision, not a repair (§8). `take` shows an issued pair as carried in.
- `link.AskModuleToolOnAs`: a module tool asked on the subject that names its caller.
- No migration: `secret.origin` takes `issued`, `secret.generation` holds the stamp (both columns exist).
**Tests** (fail on main: they do not compile there): `internal/catalogue` TestAnOfferMaySayItsSoftwareIssuesTheCredential; `cmd/mesh-controller` issued_test.go (verb line, terminal rule, sealed-to-call only, unchanged sends nobody, rotate refused, hand-act decision, manifest serves every verb); store test `./internal/inventory TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain`, listed in `testdata/store-tests` — **not run here (no store)**; the build seat's repo-check runs it.
Run here: gofmt, `go vet ./...`, `go test -race -count=1 ./...` green (store tests skip without a store).
**Order:** this first; then mesh-media-catalog's plex change (its manifest says `issued-by`, which today's controller refuses). The verb needs node-tools that serve the `call` subjects (mesh-tools #27) on the provider's machine.
**Reviewer checklist:** no value or fingerprint in any answer, log or hand-act; the verb's argv is exactly `secret issued <provision>`; only stale pairs are resealed; `rotate` refusal; the store test's SQL against the `secret` table.
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
A token a media server got from its vendor reached its consumers only as a value the mesh minted, which
the server refused, or as a copy typed by hand. An offer may now say its software issues the credential;
the new issued verb carries no value and asks the provider's tool, in the controller's own name, for the
value sealed to one call, then seals it to every pair that does not hold it yet.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
mesh-controller on novox: passed — healthy 3 times over 4m7s
mesh-controller on the rest running it: sent
build-agent on ace: passed — healthy 3 times over 3m31s
build-agent on the rest running it: sent
route-proxy on ace: passed — healthy 3 times over 3m12s
route-proxy on the rest running it: sent
Transitions
2026-10-11 23:21 (new) → proposed (announced): novox/mesh-controller#239's head announced
2026-10-11 23:28 proposed → checked (checked): the verdict names this commit
2026-10-11 23:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
2026-10-11 23:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
2026-10-11 23:30 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
2026-10-11 23:46 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.
<!-- mesh-delivery:view -->
**Delivery** `novox/mesh-controller@4ee131e990dd` — **delivered** since 2026-10-11T23:46:58Z
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
**Group** `feat/526-a-provider-delivers-what-its-software-issued`, in order: novox/hq@a0291235a2e0 → novox/mesh-controller@4ee131e990dd → novox/mesh-media-catalog@8702f007e7fb
- novox/mesh-controller@4ee131e990dd before novox/mesh-media-catalog@8702f007e7fb: built by
**Machines**
- mesh-controller on novox: passed — healthy 3 times over 4m7s
- mesh-controller on the rest running it: sent
- build-agent on ace: passed — healthy 3 times over 3m31s
- build-agent on the rest running it: sent
- route-proxy on ace: passed — healthy 3 times over 3m12s
- route-proxy on the rest running it: sent
**Transitions**
- 2026-10-11 23:21 (new) → proposed (announced): novox/mesh-controller#239's head announced
- 2026-10-11 23:28 proposed → checked (checked): the verdict names this commit
- 2026-10-11 23:28 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
- 2026-10-11 23:30 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
- 2026-10-11 23:30 published → delivering (go): its walk started: let go by this owner in its group's order, by a person, or on the controller's own path — not a failed walk that carried a later commit for it, after which it waits for a walk of its own commit
- 2026-10-11 23:46 delivering → delivered (done): its walk is done, carrying its own commit: every machine of its deploy plan passed, or was left as its policy says
The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.
mesh/merge-gate pass: builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step; every machine composes with the change as it did without …
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
read by no module's build: cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go, testdata/store-tests
Run by the build seat on g14 as build-1791760068422135812 (builds --log build-1791760068422135812).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 57 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T22:42:09Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T22:42:09Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go and testdata/store-tests read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 229.671s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.146s
ok github.com/novox/mesh-controller/internal/artifacts 1.049s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.897s
ok github.com/novox/mesh-controller/internal/builder 13.979s
ok github.com/novox/mesh-controller/internal/catalogue 6.510s
ok github.com/novox/mesh-controller/internal/conditions 2.353s
ok github.com/novox/mesh-controller/internal/envfile 1.033s
ok github.com/novox/mesh-controller/internal/facts 1.036s
ok github.com/novox/mesh-controller/internal/identity 4.101s
ok github.com/novox/mesh-controller/internal/inventory 79.106s
ok github.com/novox/mesh-controller/internal/lease 17.600s
ok github.com/novox/mesh-controller/internal/licences 3.737s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 58.107s
ok github.com/novox/mesh-controller/internal/lint 2.120s
ok github.com/novox/mesh-controller/internal/outward 1.036s
ok github.com/novox/mesh-controller/internal/overlay 1.027s
ok github.com/novox/mesh-controller/internal/secrets 1.420s
ok github.com/novox/mesh-controller/internal/store 3.264s
ok github.com/novox/mesh-controller/internal/testbus 1.173s
ok github.com/novox/mesh-controller/internal/token 1.017s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.36s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.34s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.34s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.32s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.30s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.37s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.20s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.21s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.21s)
**Merge check** at `db86dd52`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
- read by no module's build: cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go, testdata/store-tests
Run by the build seat on g14 as `build-1791760068422135812` (`builds --log build-1791760068422135812`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 57 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T22:42:09Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T22:42:09Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go and testdata/store-tests read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.038s
ok github.com/novox/mesh-controller/cmd/mesh-controller 229.671s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.014s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.026s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.146s
ok github.com/novox/mesh-controller/internal/artifacts 1.049s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.897s
ok github.com/novox/mesh-controller/internal/builder 13.979s
ok github.com/novox/mesh-controller/internal/catalogue 6.510s
ok github.com/novox/mesh-controller/internal/conditions 2.353s
ok github.com/novox/mesh-controller/internal/envfile 1.033s
ok github.com/novox/mesh-controller/internal/facts 1.036s
ok github.com/novox/mesh-controller/internal/identity 4.101s
ok github.com/novox/mesh-controller/internal/inventory 79.106s
ok github.com/novox/mesh-controller/internal/lease 17.600s
ok github.com/novox/mesh-controller/internal/licences 3.737s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.010s
ok github.com/novox/mesh-controller/internal/link 58.107s
ok github.com/novox/mesh-controller/internal/lint 2.120s
ok github.com/novox/mesh-controller/internal/outward 1.036s
ok github.com/novox/mesh-controller/internal/overlay 1.027s
ok github.com/novox/mesh-controller/internal/secrets 1.420s
ok github.com/novox/mesh-controller/internal/store 3.264s
ok github.com/novox/mesh-controller/internal/testbus 1.173s
ok github.com/novox/mesh-controller/internal/token 1.017s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.36s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.34s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.34s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.32s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.30s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.37s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.20s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.21s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.21s)
```
mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
mesh/repo-check: PASS — its merge-check.sh passed
Delivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
tier 0: mesh-controller
tier 1: build-agent
ace: receives build-agent
g14: receives build-agent
novox: receives mesh-controller, build-agent
shanks: receives build-agent
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
read by no module's build: cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go, testdata/store-tests
Run by the build seat on shanks as build-1791760193318553689 (builds --log build-1791760193318553689).
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 57 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T22:42:09Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T22:42:09Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go and testdata/store-tests read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.045s
ok github.com/novox/mesh-controller/cmd/mesh-controller 254.638s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.037s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.043s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.199s
ok github.com/novox/mesh-controller/internal/artifacts 1.078s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.150s
ok github.com/novox/mesh-controller/internal/builder 18.871s
ok github.com/novox/mesh-controller/internal/catalogue 7.888s
ok github.com/novox/mesh-controller/internal/conditions 2.648s
ok github.com/novox/mesh-controller/internal/envfile 1.048s
ok github.com/novox/mesh-controller/internal/facts 1.040s
ok github.com/novox/mesh-controller/internal/identity 5.063s
ok github.com/novox/mesh-controller/internal/inventory 99.992s
ok github.com/novox/mesh-controller/internal/lease 17.730s
ok github.com/novox/mesh-controller/internal/licences 4.530s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.050s
ok github.com/novox/mesh-controller/internal/link 61.746s
ok github.com/novox/mesh-controller/internal/lint 2.498s
ok github.com/novox/mesh-controller/internal/outward 1.082s
ok github.com/novox/mesh-controller/internal/overlay 1.066s
ok github.com/novox/mesh-controller/internal/secrets 1.529s
ok github.com/novox/mesh-controller/internal/store 3.620s
ok github.com/novox/mesh-controller/internal/testbus 1.222s
ok github.com/novox/mesh-controller/internal/token 1.015s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.46s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.41s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.39s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
**Merge check** at `faf8b76b`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- ace: receives build-agent
- g14: receives build-agent
- novox: receives mesh-controller, build-agent
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent is judged on its first machine
- read by no module's build: cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go, testdata/store-tests
Run by the build seat on shanks as `build-1791760193318553689` (`builds --log build-1791760193318553689`).
```
--- the gate: build-agent, mesh-controller
mesh-controller: ok, 57 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T22:42:09Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T22:42:09Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 2 module(s) in 2 tier(s): build-agent, mesh-controller
notes:
- cmd/mesh-controller/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go and testdata/store-tests read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.045s
ok github.com/novox/mesh-controller/cmd/mesh-controller 254.638s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.037s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.043s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.024s
ok github.com/novox/mesh-controller/examples/route-proxy 1.199s
ok github.com/novox/mesh-controller/internal/artifacts 1.078s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 3.150s
ok github.com/novox/mesh-controller/internal/builder 18.871s
ok github.com/novox/mesh-controller/internal/catalogue 7.888s
ok github.com/novox/mesh-controller/internal/conditions 2.648s
ok github.com/novox/mesh-controller/internal/envfile 1.048s
ok github.com/novox/mesh-controller/internal/facts 1.040s
ok github.com/novox/mesh-controller/internal/identity 5.063s
ok github.com/novox/mesh-controller/internal/inventory 99.992s
ok github.com/novox/mesh-controller/internal/lease 17.730s
ok github.com/novox/mesh-controller/internal/licences 4.530s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.050s
ok github.com/novox/mesh-controller/internal/link 61.746s
ok github.com/novox/mesh-controller/internal/lint 2.498s
ok github.com/novox/mesh-controller/internal/outward 1.082s
ok github.com/novox/mesh-controller/internal/overlay 1.066s
ok github.com/novox/mesh-controller/internal/secrets 1.529s
ok github.com/novox/mesh-controller/internal/store 3.620s
ok github.com/novox/mesh-controller/internal/testbus 1.222s
ok github.com/novox/mesh-controller/internal/token 1.015s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.46s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.47s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.46s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.43s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.41s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.39s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.46s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.27s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.28s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.29s)
```
mesh/merge-gate pass: builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step; every machine composes with the change as it…
The bus left the controller out of the caller-named grants, so issued could never reach plex's tool; the
controller is now granted exactly the tools of offers whose software issues the credential, composed from
the records, so the installer's first user list is unchanged. A pair remade on a key change or accepted by
hand kept the issued stamp and was never sealed again; those writes now clear it.
build-agent keeps data (ADR 0233): what it holds is backed up before it moves
route-proxy provides route: its consumers are sent again after it
route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
read by no module's build: cmd/mesh-controller/issued_test.go, internal/broker/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go, testdata/store-tests
Run by the build seat on g14 as build-1791760890494531042 (builds --log build-1791760890494531042).
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 57 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T22:42:09Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T22:42:09Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/issued_test.go, internal/broker/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go and testdata/store-tests read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.041s
ok github.com/novox/mesh-controller/cmd/mesh-controller 229.812s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/route-proxy 1.151s
ok github.com/novox/mesh-controller/internal/artifacts 1.051s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.903s
ok github.com/novox/mesh-controller/internal/builder 13.913s
ok github.com/novox/mesh-controller/internal/catalogue 6.662s
ok github.com/novox/mesh-controller/internal/conditions 2.377s
ok github.com/novox/mesh-controller/internal/envfile 1.034s
ok github.com/novox/mesh-controller/internal/facts 1.038s
ok github.com/novox/mesh-controller/internal/identity 4.192s
ok github.com/novox/mesh-controller/internal/inventory 79.565s
ok github.com/novox/mesh-controller/internal/lease 17.702s
ok github.com/novox/mesh-controller/internal/licences 3.841s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.009s
ok github.com/novox/mesh-controller/internal/link 58.623s
ok github.com/novox/mesh-controller/internal/lint 2.151s
ok github.com/novox/mesh-controller/internal/outward 1.038s
ok github.com/novox/mesh-controller/internal/overlay 1.024s
ok github.com/novox/mesh-controller/internal/secrets 1.471s
ok github.com/novox/mesh-controller/internal/store 3.229s
ok github.com/novox/mesh-controller/internal/testbus 1.179s
ok github.com/novox/mesh-controller/internal/token 1.018s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.33s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.33s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.33s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.32s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.29s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.35s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.21s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.20s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.23s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.20s)
**Merge check** at `4ee131e9`
- `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)
- `mesh/repo-check`: **PASS** — its merge-check.sh passed
**Delivery plan** — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
- tier 0: mesh-controller
- tier 1: build-agent
- tier 2: route-proxy
- ace: receives build-agent, route-proxy
- g14: receives build-agent
- novox: receives mesh-controller, build-agent, route-proxy
- shanks: receives build-agent
- build-agent keeps data (ADR 0233): what it holds is backed up before it moves
- route-proxy provides route: its consumers are sent again after it
- route-proxy keeps data (ADR 0233): what it holds is backed up before it moves
- grants step: if this changes what the bus's user list says (a new tool, subject or user), novox is sent that list alone, every build there kept, before build-agent, route-proxy is judged on its first machine
- read by no module's build: cmd/mesh-controller/issued_test.go, internal/broker/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go, testdata/store-tests
Run by the build seat on g14 as `build-1791760890494531042` (`builds --log build-1791760890494531042`).
```
--- the gate: build-agent, mesh-controller, route-proxy
mesh-controller: ok, 57 tool(s); WARNING: merge-window ask(s) for a setting and do(es) not say whether it is trusted, so it counts as trusted: set at the terminal alone; say "trusted" false where nothing trusts it (novox/hq issue 339); WARNING: controller stay(s) up and say(s) not how it is ready — judged by liveness alone, refused from 2026-11-18 (ADR 0240 rule 8)
long-running resources without health: 1
files asking for a setting without saying whether it is trusted: 1
1 manifest(s) checked. Judged against the seats this binary carries; a claim on one of the mesh's own seats is judged fully at registration, and a seat declared by a module not given here reads as unknown. Identities judged on a 6-character machine name, against the bounds of the providers given here
judging 1 module(s) changed against 4 machine(s), as the snapshot of 2026-10-11T22:42:09Z says they run
composing every machine as the mesh is
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
composing every machine with the change
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
the bus's user list leaves out 5 user(s) the mesh has minted no credential for: controller, node.f35, node.idt, node.ygcyr, node.yvbpsm. Each is a user that cannot connect until one is issued
merge gate: PASS — every machine composes with the change as it did without (4 of 4 compose)
judged by controller development build against the facts of 2026-10-11T22:42:09Z
modules the change moves:
- mesh-controller (changed)
machines:
- a machine (f35): composes
- holds mesh-dns-resolver (idt): composes
- holds git, holds mesh-artifact-store, holds mesh-broker, holds mesh-catalog, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-store, holds mesh-vault, holds npm-package-registry, the control node, the hub (ygcyr): composes
- a machine (yvbpsm): composes
a merge would rebuild 3 module(s) in 3 tier(s): build-agent, mesh-controller, route-proxy
notes:
- cmd/mesh-controller/issued_test.go, internal/broker/issued_test.go, internal/catalogue/issued_credential_test.go, internal/inventory/issued_test.go and testdata/store-tests read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok github.com/novox/mesh-controller/cmd/mesh-builder 1.041s
ok github.com/novox/mesh-controller/cmd/mesh-controller 229.812s
ok github.com/novox/mesh-controller/examples/objectstore-provisioner 1.020s
ok github.com/novox/mesh-controller/examples/postgres-provisioner 1.023s
ok github.com/novox/mesh-controller/examples/redis-provisioner 1.011s
ok github.com/novox/mesh-controller/examples/route-proxy 1.151s
ok github.com/novox/mesh-controller/internal/artifacts 1.051s
? github.com/novox/mesh-controller/internal/beside [no test files]
ok github.com/novox/mesh-controller/internal/broker 2.903s
ok github.com/novox/mesh-controller/internal/builder 13.913s
ok github.com/novox/mesh-controller/internal/catalogue 6.662s
ok github.com/novox/mesh-controller/internal/conditions 2.377s
ok github.com/novox/mesh-controller/internal/envfile 1.034s
ok github.com/novox/mesh-controller/internal/facts 1.038s
ok github.com/novox/mesh-controller/internal/identity 4.192s
ok github.com/novox/mesh-controller/internal/inventory 79.565s
ok github.com/novox/mesh-controller/internal/lease 17.702s
ok github.com/novox/mesh-controller/internal/licences 3.841s
ok github.com/novox/mesh-controller/internal/licences/adapters 1.009s
ok github.com/novox/mesh-controller/internal/link 58.623s
ok github.com/novox/mesh-controller/internal/lint 2.151s
ok github.com/novox/mesh-controller/internal/outward 1.038s
ok github.com/novox/mesh-controller/internal/overlay 1.024s
ok github.com/novox/mesh-controller/internal/secrets 1.471s
ok github.com/novox/mesh-controller/internal/store 3.229s
ok github.com/novox/mesh-controller/internal/testbus 1.179s
ok github.com/novox/mesh-controller/internal/token 1.018s
store tests, each run against the store:
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeWalksTheOthersAgain (0.33s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeEndsTheMergesThatContainIt (0.35s)
./cmd/mesh-controller --- PASS: TestAStopWalksTheOthersAgainInTheOpenBatch (0.33s)
./cmd/mesh-controller --- PASS: TestAStopNamesWhatStaysOnTheMachinesAndWhatStillCarriesIt (0.33s)
./cmd/mesh-controller --- PASS: TestAStopWithoutAMergeLeavesItOutOfABatch (0.32s)
./cmd/mesh-controller --- PASS: TestSavingPlansAndMovingMergesIsOneAct (0.29s)
./cmd/mesh-controller --- PASS: TestNodeShowAndStatusReadTheLastSendFromTheStore (0.35s)
./internal/inventory --- PASS: TestTheLastSendSaysWhatTheMachineAnswered (0.21s)
./internal/inventory --- PASS: TestAReportIsTheLastSendsAnswerOnlyWhenItIsAboutThatSend (0.20s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain (0.23s)
./internal/inventory --- PASS: TestAnIssuedValueIsSealedAgainAfterAKeyChangeOrAnAcceptance (0.20s)
```
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Issue 526; ADR 0305 (proposed, needs the operator's Approve; do not merge before it is accepted).
What changes
catalogue: an offer may say"credential": {"issued-by": "software", "tool": "<tool>"}(no own secret); the parser refuses both, another issuer, or no tool.IssuedCredentialOf.issued(secret issued <provision>): carries no value, answers none. For each machine providing the provision to a pair the mesh holds, it asks the provider's named tool on that machine in the controller's own name (the caller-namedcallsubject, issue 365) with a one-time sealing key, opens the answer, seals it to every pair that does not hold it yet under one stamp of its fingerprint (and to the operator), and sends the provider's and those consumers' machines. A pair that already holds the value is not touched, so an hourly ask restarts nothing.terminalOnly:secret issued <provision>joinsrotateand the desk'saskas thesecretlines a verb runs (ADR 0305 §10).rotateof such a provision is refused (§9). Hand-act table:secret issuedis a decision, not a repair (§8).takeshows an issued pair as carried in.link.AskModuleToolOnAs: a module tool asked on the subject that names its caller.secret.origintakesissued,secret.generationholds the stamp (both columns exist).Tests (fail on main: they do not compile there):
internal/catalogueTestAnOfferMaySayItsSoftwareIssuesTheCredential;cmd/mesh-controllerissued_test.go (verb line, terminal rule, sealed-to-call only, unchanged sends nobody, rotate refused, hand-act decision, manifest serves every verb); store test./internal/inventory TestAnIssuedValueIsSealedToEveryHolderOnceAndNotAgain, listed intestdata/store-tests— not run here (no store); the build seat's repo-check runs it.Run here: gofmt,
go vet ./...,go test -race -count=1 ./...green (store tests skip without a store).Order: this first; then mesh-media-catalog's plex change (its manifest says
issued-by, which today's controller refuses). The verb needs node-tools that serve thecallsubjects (mesh-tools #27) on the provider's machine.Reviewer checklist: no value or fingerprint in any answer, log or hand-act; the verb's argv is exactly
secret issued <provision>; only stale pairs are resealed;rotaterefusal; the store test's SQL against thesecrettable.Delivery
novox/mesh-controller@4ee131e990dd— delivered since 2026-10-11T23:46:58ZDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Group
feat/526-a-provider-delivers-what-its-software-issued, in order: novox/hq@a0291235a2 → novox/mesh-controller@4ee131e990 → novox/mesh-media-catalog@8702f007e7Machines
Transitions
The commit's note under
refs/notes/mesh-plankeeps every transition:git log --notes=mesh-plan.Merge check at
db86dd52mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791760068422135812(builds --log build-1791760068422135812).Merge check at
faf8b76bmesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller → ace, g14, novox, shanks; no bus step
Run by the build seat on shanks as
build-1791760193318553689(builds --log build-1791760193318553689).Merge check at
4ee131e9mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: build-agent, mesh-controller, route-proxy)mesh/repo-check: PASS — its merge-check.sh passedDelivery plan — builds build-agent, mesh-controller, route-proxy → ace, g14, novox, shanks; no bus step
Run by the build seat on g14 as
build-1791760890494531042(builds --log build-1791760890494531042).