mesh-delivery

Files

T

jschoubben 64afa00457 The indexer's catch-up tool takes no arguments and is named beside its catalog graph revisions (milestone 47/G W4.14)

The node agent calls a restored part's catch-up tool with no arguments, so
indexer_take_in with neither module nor repository takes in the head the
gate's source names for every repository, as the first start's catch-up
does, and keeps the view as the next revision when an entry moved. The
manifest names it beside the catalog graph revisions, form 1 (design 47,
Reverted).

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

2026-11-11 11:47:04 +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)