mesh-delivery

Files

T

jschoubben 3076aabbe0 D3: the teller keeps an assigner ask whose publish failed waiting, and asks it at the next end and at its start (issue 1966, ADR 0668 §1)

A failed publish deleted the kept record for "the next writing of the key", which nothing made.
The ask now joins the teller's wait for room, kept on the bus, which asks again at the next end
and at the start. The gate's asks are left as they are (ADR 0666 §6 replaces them).

Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ

2026-11-10 03:17:50 +01:00

mesh-delivery-assigner

D2: assigner_ask_again asks one of the assigner's asks of the operator again by hand (issue 1966, ADR 0668 §5)

2026-11-10 03:16:28 +01:00

mesh-delivery-builder

D1: the assigner, builder and indexer call every node's manifest-reads again at their consumer's bind (issue 1966, ADR 0668 §4)

2026-11-10 02:59:53 +01:00

mesh-delivery-checker

F1, F7: the asker drops an ask only on a withdrawal cause (superseded, taken out, asked again by hand), not on the check bound; the checker's drop on Forget is asserted; a step's own run count and a failed drop are said (ADR 0664 §4, issue 1748 review 1)

2026-11-09 23:37:51 +01:00

mesh-delivery-forge-bridge

A lost take-in hold passes the take-in event's check, so it is said (issue 1966)