mesh-delivery

Files

T

jschoubben bd067ae779 The indexer keeps a catalog graph revision at each merge and each moved fingerprint, and says catalog-revision (milestone 47/G W4.3, its writing part)

Design 47 (Two graphs) keeps a catalog graph revision for each source revision taken in and for a fingerprint moved
with no merge. The recompute that writes the module graph now keeps the revision it makes, numbered after the newest
kept trunk revision, and says the seat mesh-catalog's event catalog-revision naming the changed modules; a recompute
that moves no entry keeps none, and objects not yet on the bus keep none, said in the log.

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

2026-11-11 11:45:07 +01:00

mesh-delivery-assigner

S4: the assigner's wants step proves a restatement heard while ace's ask runs is asked once more (issue 1966 note 170)

2026-11-10 11:36:02 +01:00

mesh-delivery-builder

BL15: the gate's source is watched by every watched branch's key; SourceMainKey retired

2026-11-11 11:28:36 +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)