novox/mesh-catalog
8
0
Fork 0
Code Issues Pull Requests 4 Actions Packages Projects Releases Wiki Activity

Hold an ask no channel can carry now and offer it when one can (issue 926, ADR 0397) #333

Merged
mesh-tools merged 2 commits from fix/926-a-held-ask-waits-for-a-channel into main 2026-10-16 16:28:22 +00:00
Conversation 3 Commits 2 Files Changed 13
+881 -57
mesh-tools commented 2026-10-16 16:00:48 +00:00
Member
Copy Link
Copy Source

Issue 926: the router refused an approval ask at once ('no channel can carry any of its answers now: no channel') when no channel could carry it for a moment, and the knowledge base kept saying it waited for the operator. The operator chose 'hold and resend' on Telegram (2026-10-16 17:37), recorded as ADR 0397.

  • messenger: an ask that breaks no rule but that no ready channel can carry now is kept as held up to its expiry, with the true reason per kind (from the same judgement as an answer, never 'no channel'); re-judged every minute, after each read of the kinds and on a channel's standing; offered exactly as a new ask once a channel can carry it. Held counts toward the three open asks; expiry, cancel and replacement end it as before. The asks verb shows held, since and why.
  • mesh-knowledge: reads the router's held state and reason; get says the ask is held by the router and why, instead of waiting for the operator's answer.

Tests: unit tests in both modules; integration test TestAnApprovalAskIsHeldThenOfferedWhenAChannelCanCarryItOverTheBus starts the router whole on an embedded bus. messenger's go.mod moves to go 1.25.0 with nats-server for that test (same versions as mesh-knowledge).

Reviewed locally by an independent reviewer (approved at 77d751f). Follow-ups opened as a minor issue.

Issue 926: the router refused an approval ask at once ('no channel can carry any of its answers now: no channel') when no channel could carry it for a moment, and the knowledge base kept saying it waited for the operator. The operator chose 'hold and resend' on Telegram (2026-10-16 17:37), recorded as ADR 0397. - messenger: an ask that breaks no rule but that no ready channel can carry now is kept as held up to its expiry, with the true reason per kind (from the same judgement as an answer, never 'no channel'); re-judged every minute, after each read of the kinds and on a channel's standing; offered exactly as a new ask once a channel can carry it. Held counts toward the three open asks; expiry, cancel and replacement end it as before. The asks verb shows held, since and why. - mesh-knowledge: reads the router's held state and reason; get says the ask is held by the router and why, instead of waiting for the operator's answer. Tests: unit tests in both modules; integration test TestAnApprovalAskIsHeldThenOfferedWhenAChannelCanCarryItOverTheBus starts the router whole on an embedded bus. messenger's go.mod moves to go 1.25.0 with nats-server for that test (same versions as mesh-knowledge). Reviewed locally by an independent reviewer (approved at 77d751f). Follow-ups opened as a minor issue.
mesh-tools added 2 commits 2026-10-16 16:00:48 +00:00
Hold an ask no channel can carry now and offer it when one can; show held and why (issue 926, ADR 0397) c211762813 
The router refused such an ask with 'no channel', so the asker waited for an Approve nobody saw. It is now held as an open ask with the per-kind reason, judged again when the kinds or a channel's standing change and every minute, and the knowledge base says held and why.
Test the router whole over the real bus: a held ask is offered when a channel can carry it (issue 926, ADR 0397)
mesh/merge-gate head 77d751fe830d merged into trunk 08188663faff — pass: builds mesh-knowledge, messenger → novox; no bus step; every machine composes with…
Details
mesh/repo-check head 77d751fe830d merged into trunk 08188663faff — pass: its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-…
Details
mesh/delivery delivered
Details
77d751fe83
mesh-tools commented 2026-10-16 16:01:00 +00:00
Author
Member
Copy Link
Copy Source

Delivery novox/mesh-catalog@77d751fe830d — delivered since 2026-10-16T16:29:59Z

Delivery plan — builds mesh-knowledge, messenger → novox; no bus step

  • tier 0: mesh-knowledge, messenger
  • novox: receives mesh-knowledge, messenger

Machines

  • mesh-knowledge on every machine running it: sent
  • messenger on every machine running it: sent

Transitions

  • 2026-10-16 16:00 (new) → proposed (announced): novox/mesh-catalog#333's head announced
  • 2026-10-16 16:05 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit
  • 2026-10-16 16:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail
  • 2026-10-16 16:28 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move
  • 2026-10-16 16:28 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-16 16:29 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-catalog@77d751fe830d` — **delivered** since 2026-10-16T16:29:59Z **Delivery plan** — builds mesh-knowledge, messenger → novox; no bus step - tier 0: mesh-knowledge, messenger - novox: receives mesh-knowledge, messenger **Machines** - mesh-knowledge on every machine running it: sent - messenger on every machine running it: sent **Transitions** - 2026-10-16 16:00 (new) → proposed (announced): novox/mesh-catalog#333's head announced - 2026-10-16 16:05 proposed → checked (checked): a verdict names this commit and the trunk's head as its trunk commit - 2026-10-16 16:05 checked → ready (accepted): the gate passed or warned, and the repository's own check did not fail - 2026-10-16 16:28 ready → published (merged): on the trunk its modules follow: merged there, and its walk opened — or nothing for a walk to move - 2026-10-16 16:28 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-16 16:29 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-tools commented 2026-10-16 16:05:15 +00:00
Author
Member
Copy Link
Copy Source

Merge check at 77d751fe
Judged: head 77d751fe830d merged into trunk 08188663faff; read beside it: mesh-controller c7cb9f0a2cd3, mesh-controller-main c7cb9f0a2cd3, mesh-host cd13f7726ef0, mesh-tools 7412c5b6c9c5

  • mesh/merge-gate: PASS — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge, messenger)
  • mesh/repo-check: PASS — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript)

Delivery plan — builds mesh-knowledge, messenger → novox; no bus step

  • tier 0: mesh-knowledge, messenger
  • novox: receives mesh-knowledge, messenger
  • read by no module's build: modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/messenger/cmd/messenger/answers_test.go, modules/messenger/cmd/messenger/bus_test.go, modules/messenger/cmd/messenger/held_test.go

Run by the build seat on ace as build-1792166451387385683 (builds --log build-1792166451387385683).

--- the gate: mesh-knowledge, messenger
mesh-knowledge: ok, 2 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, claude-code.claude_code_judged, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s
messenger: ok, 7 tool(s), invokes seat:mesh-controller.conditions, seat:mesh-controller.root-free, seat:issue-tracker.tracking, keeps state open, sent, asks, identities, walks; WARNING: settings 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)
long-running resources without health: 0
files asking for a setting without saying whether it is trusted: 1
2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T15:55:22Z 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-16T15:55:22Z

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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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 1 tier(s): mesh-knowledge, messenger

notes:
  - modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/messenger/cmd/messenger/answers_test.go, modules/messenger/cmd/messenger/bus_test.go and modules/messenger/cmd/messenger/held_test.go read by no module's build, and rebuild nothing (issue 280)
--- its merge-check.sh (go toolchain)
ok  	git.novox.be/novox/mesh-catalog/checks/words	0.002s
words: 12 retired words and 70 daemons' lines, none in the 53622 strings of 801 files
ok  	git.novox.be/novox/mesh-catalog/checks/agenthome	0.010s
agent-home: no archive and no file written into under the agent's home
ok  	git.novox.be/novox/mesh-catalog/checks/mailstore	0.008s
mail-store: claimed only by mesh-mail
ok  	git.novox.be/novox/mesh-catalog/checks/secrets	0.012s
secrets: no setting can replace a vault secret in a mergeable file (1 known, nested)
ok  	git.novox.be/novox/mesh-catalog/checks/predefined	0.238s
predefined.json: 2 key(s), none removed that a module names
ok  	git.novox.be/novox/mesh-catalog/checks/config	0.014s
config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved)
ok  	git.novox.be/novox/mesh-catalog/checks/templates	0.010s
templates: no module keeps a file's text inline but the 0 listed
ok  	git.novox.be/novox/mesh-catalog/checks/paths	0.005s
paths: no module names another's state on its machine (3 known, listed to go)
long-running resources without health: 61, as kept
ok  	git.novox.be/novox/mesh-catalog/checks/deps	0.207s
testing modules/mesh-knowledge
ok  	mesh-knowledge/cmd/mesh-knowledge	100.912s
testing modules/messenger
ok  	messenger/cmd/messenger	4.921s
--- its merge-check-typescript.sh (typescript toolchain)
**Merge check** at `77d751fe` Judged: head `77d751fe830d` merged into trunk `08188663faff`; read beside it: mesh-controller `c7cb9f0a2cd3`, mesh-controller-main `c7cb9f0a2cd3`, mesh-host `cd13f7726ef0`, mesh-tools `7412c5b6c9c5` - `mesh/merge-gate`: **PASS** — every machine composes with the change as it did without (4 of 4 compose) (modules: mesh-knowledge, messenger) - `mesh/repo-check`: **PASS** — its merge-check.sh passed, each part in its toolchain: merge-check.sh (go), merge-check-typescript.sh (typescript) **Delivery plan** — builds mesh-knowledge, messenger → novox; no bus step - tier 0: mesh-knowledge, messenger - novox: receives mesh-knowledge, messenger - read by no module's build: modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/messenger/cmd/messenger/answers_test.go, modules/messenger/cmd/messenger/bus_test.go, modules/messenger/cmd/messenger/held_test.go Run by the build seat on ace as `build-1792166451387385683` (`builds --log build-1792166451387385683`). ``` --- the gate: mesh-knowledge, messenger mesh-knowledge: ok, 2 tool(s), invokes seat:issue-tracker.reserve, claude-code.claude_code_judge, claude-code.claude_code_judged, records.records_status, records.records_list, records.records_read, seat:operator-channel.notify, ready: keep by unit every 30s; watch by its tool knowledge_health every 1m0s messenger: ok, 7 tool(s), invokes seat:mesh-controller.conditions, seat:mesh-controller.root-free, seat:issue-tracker.tracking, keeps state open, sent, asks, identities, walks; WARNING: settings 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) long-running resources without health: 0 files asking for a setting without saying whether it is trusted: 1 2 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 0 module(s) changed against 4 machine(s), as the snapshot of 2026-10-16T15:55:22Z 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-16T15:55:22Z 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-config, holds mesh-delivery, holds mesh-dns-resolver, holds mesh-provisioner, 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 1 tier(s): mesh-knowledge, messenger notes: - modules/mesh-knowledge/cmd/mesh-knowledge/kit_test.go, modules/mesh-knowledge/cmd/mesh-knowledge/review_test.go, modules/messenger/cmd/messenger/answers_test.go, modules/messenger/cmd/messenger/bus_test.go and modules/messenger/cmd/messenger/held_test.go read by no module's build, and rebuild nothing (issue 280) --- its merge-check.sh (go toolchain) ok git.novox.be/novox/mesh-catalog/checks/words 0.002s words: 12 retired words and 70 daemons' lines, none in the 53622 strings of 801 files ok git.novox.be/novox/mesh-catalog/checks/agenthome 0.010s agent-home: no archive and no file written into under the agent's home ok git.novox.be/novox/mesh-catalog/checks/mailstore 0.008s mail-store: claimed only by mesh-mail ok git.novox.be/novox/mesh-catalog/checks/secrets 0.012s secrets: no setting can replace a vault secret in a mergeable file (1 known, nested) ok git.novox.be/novox/mesh-catalog/checks/predefined 0.238s predefined.json: 2 key(s), none removed that a module names ok git.novox.be/novox/mesh-catalog/checks/config 0.014s config: no moved module says settings, takes-settings or ${setting:<key>}, or takes a whole layer (0 not yet moved) ok git.novox.be/novox/mesh-catalog/checks/templates 0.010s templates: no module keeps a file's text inline but the 0 listed ok git.novox.be/novox/mesh-catalog/checks/paths 0.005s paths: no module names another's state on its machine (3 known, listed to go) long-running resources without health: 61, as kept ok git.novox.be/novox/mesh-catalog/checks/deps 0.207s testing modules/mesh-knowledge ok mesh-knowledge/cmd/mesh-knowledge 100.912s testing modules/messenger ok messenger/cmd/messenger 4.921s --- its merge-check-typescript.sh (typescript toolchain) ```
mesh-tools added the mesh/ready label 2026-10-16 16:27:55 +00:00
mesh-tools commented 2026-10-16 16:27:55 +00:00
Author
Member
Copy Link
Copy Source

ready at 77d751fe83

Reviewed by reviewer-926@shanks: approved against issue 926 and ADR 0397; marked by lead-926@shanks on the operator's word (2026-10-16), the reviewer's own mark was refused by the permission check. Marked through mesh-delivery.mark-ready (novox/hq issue 913).

ready at 77d751fe830d4358728714572bf8869f196aaf9d Reviewed by reviewer-926@shanks: approved against issue 926 and ADR 0397; marked by lead-926@shanks on the operator's word (2026-10-16), the reviewer's own mark was refused by the permission check. Marked through mesh-delivery.mark-ready (novox/hq issue 913).
mesh-tools merged commit 6268f8f94b into main 2026-10-16 16:28:22 +00:00
mesh-tools deleted branch fix/926-a-held-ask-waits-for-a-channel 2026-10-16 16:28:22 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
Clear labels
mesh/ready
Reviewed and ready: mesh-delivery merges at the marked head once its checks pass (hq ADR 0364)
No labels mesh/ready
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jschoubben mesh-tools miel.truyen
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: novox/mesh-catalog#333