Issue 208: the bus's objects asserted on every send #131

2026-10-06T09:46:35Z

mesh-admin commented

2026-10-06 09:46:35 +00:00

Issue 208 (status located) gets its fix pointer, novox/mesh-controller#81 (b853439). Its status flips to resolved once that merges and is live.

Seen again, 2026-10-06: the module half of the same gap. A module carried by the runtime, assigned after the controller started, had no consumer, because a push created one only when it minted a credential.
Fix: the bus's objects are asserted, by the start's own derivation, whenever a declaration is sent. A failure is said in the send's output and raised as bus.objects.unasserted, and the send goes on. The section also says how this is checked.
Phase 3 note: H3's repair is now exactly the send's assertion, so one healer can cover D6's missing consumer and D3's missing worker. Noted, not built.

records.py, index.py and cycle.py all pass.

Issue 208 (status `located`) gets its fix pointer, `novox/mesh-controller#81 (b853439)`. Its status flips to `resolved` once that merges and is live. - **Seen again, 2026-10-06:** the module half of the same gap. A module carried by the runtime, assigned after the controller started, had no consumer, because a push created one only when it minted a credential. - **Fix:** the bus's objects are asserted, by the start's own derivation, whenever a declaration is sent. A failure is said in the send's output and raised as `bus.objects.unasserted`, and the send goes on. The section also says how this is checked. - **Phase 3 note:** H3's repair is now exactly the send's assertion, so one healer can cover D6's missing consumer and D3's missing worker. Noted, not built. records.py, index.py and cycle.py all pass.

mesh-admin added 1 commit 2026-10-06 09:46:35 +00:00

Issue 208: the bus's objects asserted on every send; fix pointer, the module half, Phase 3 note e6e9d4dcc3

mesh-admin merged commit 95c024b7c6 into main

2026-10-06 09:47:02 +00:00

mesh-admin deleted branch issues/208-bus-objects-asserted-on-every-send

2026-10-06 09:47:02 +00:00

mesh-admin commented

2026-10-06 23:07:43 +00:00

Delivery novox/hq@95c024b7c61f — 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 nothing: the change touches no module of the mesh's graph

Transitions

2026-10-06 23:05 (new) → proposed (announced): novox/hq#131 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/hq@95c024b7c61f` — **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 nothing: the change touches no module of the mesh's graph **Transitions** - 2026-10-06 23:05 (new) → proposed (announced): novox/hq#131 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/hq#131