Say again what was last applied when the mesh asks (hq to-be 45 Phase 3, the report verb) #37

2026-10-06T12:28:23Z

mesh-admin commented

2026-10-06 12:28:23 +00:00

hq to-be 45 Phase 3, ADR 0231 (hq PR on the same branch).

The node-engine hears mesh.node.<self>.ask.report (core NATS) and enqueues a reconcile whose account is said whether or not it is news; a delivery waiting is applied and reported instead. The answer is the ordinary report on its own subject — nothing new published, no inbox answered. This is what the controller's healer H1 asks before sending a machine again.
examples/foundation-first-node-nats.lock: the genesis controller is granted mesh.seat.mesh-controller.event.healer-acted, which the controller now composes (mesh-controller's genesis test holds them equal).

Tests: internal/link/asked_test.go (queue, link→queue, and against a real nats:2.11). Full suite -race green.

Merge order: with or before the mesh-controller PR on the same branch (its genesis test reads this lock). Rollout in any order: a node-engine without this is simply sent again by H1; the node's grant to hear the question comes from the controller's composed user list (push of the bus's machine).

hq to-be 45 Phase 3, ADR 0231 (hq PR on the same branch). - The node-engine hears `mesh.node.<self>.ask.report` (core NATS) and enqueues a reconcile whose account is said whether or not it is news; a delivery waiting is applied and reported instead. The answer is the ordinary report on its own subject — nothing new published, no inbox answered. This is what the controller's healer H1 asks before sending a machine again. - `examples/foundation-first-node-nats.lock`: the genesis controller is granted `mesh.seat.mesh-controller.event.healer-acted`, which the controller now composes (mesh-controller's genesis test holds them equal). Tests: `internal/link/asked_test.go` (queue, link→queue, and against a real nats:2.11). Full suite `-race` green. Merge order: with or before the mesh-controller PR on the same branch (its genesis test reads this lock). Rollout in any order: a node-engine without this is simply sent again by H1; the node's grant to hear the question comes from the controller's composed user list (push of the bus's machine).

mesh-admin added 1 commit 2026-10-06 12:28:23 +00:00

Say again what was last applied when the mesh asks (hq to-be 45 Phase 3, the report verb) 6e1bcdbde4

The controller's healer H1 answers a send that went unreported by asking the
machine first: a report lost on its way (issue 264) needs no second send. The
node-engine now hears mesh.node.<self>.ask.report on core NATS and enqueues a
reconcile whose account is said whether or not it is news; a delivery waiting
meanwhile is applied and reported instead. The answer is an ordinary report on
its own subject, so the node publishes nothing new and answers nobody's inbox.

The genesis lock grants the controller the healer-acted seat event, which it
now composes; the genesis test in mesh-controller holds the two equal.

mesh-admin merged commit 280d3b2e1e into main

2026-10-06 12:29:15 +00:00

mesh-admin deleted branch feat/a-core-that-cannot-fail-silently-phase-3

2026-10-06 12:29:15 +00:00

mesh-admin commented

2026-10-06 23:10:35 +00:00

Delivery novox/mesh-host@280d3b2e1e37 — held since 2026-10-06T23:05:28Z

Held for a person: merged without a passing check: only a person decides that it goes on — mesh-delivery.release with why lets it go on.

Delivery plan — builds mesh-host → ace, g14, novox, shanks; no bus step

tier 0: mesh-host
ace: receives mesh-host
g14: receives mesh-host
novox: receives mesh-host
shanks: receives mesh-host

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#37 merged; its head was not heard by this owner, so it is made from the forge's word
2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on

The commit's note under refs/notes/mesh-plan keeps every transition: git log --notes=mesh-plan.

**Delivery** `novox/mesh-host@280d3b2e1e37` — **held** since 2026-10-06T23:05:28Z Held for a person: merged without a passing check: only a person decides that it goes on — `mesh-delivery.release` with why lets it go on. **Delivery plan** — builds mesh-host → ace, g14, novox, shanks; no bus step - tier 0: mesh-host - ace: receives mesh-host - g14: receives mesh-host - novox: receives mesh-host - shanks: receives mesh-host **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/mesh-host#37 merged; its head was not heard by this owner, so it is made from the forge's word - 2026-10-06 23:05 proposed → held (merged-unchecked): merged without a passing check — a verdict known with it is taken first: only a person decides that it goes on The commit's note under `refs/notes/mesh-plan` keeps every transition: `git log --notes=mesh-plan`.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/mesh-host#37