mesh-delivery

Files

T

jschoubben c2e7249897 Keep every binding the bus module says created, and never acknowledge one not kept

distribution's membership carried 4 of its 8 bindings and mesh-knowledge's 3
of 6 (issue 1966). The grants part wrote a module's kept bindings with a blind
put, so two created heard at once lost one, and acknowledged every seat event
whatever its handler answered, while the log said it would come again. The
bindings are now written at the revision read and read again once on a
conflict, and an event not applied is left unacknowledged (a delayed nak).

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

2026-11-09 14:01:41 +01:00

mesh-delivery-assigner

The assigner, the indexer and the grants part tell their followers when the bus made their consumer (issue 1966, recovery)

2026-11-09 02:27:38 +01:00

mesh-delivery-builder

The builder's build log has a cap that holds its 30 days (issue 1966, recovery)

2026-11-09 09:45:37 +01:00

mesh-delivery-checker

The checker's tools and the assigner's put ask the indexer's tools instead of reading its state (issue 1966, recovery)

2026-11-08 11:58:42 +01:00

mesh-delivery-forge-bridge

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