mesh-delivery

Files

T

jschoubben a732cb0cb2 The indexer declares no modules or graph state: its view of the trunk is the catalog graph revisions (milestone 47/G W4.3, the manifest)

The states modules and graph leave the manifest and the names the indexer keeps; their first views and read tools are
answered from the newest revision, whose changes catalog-revision says. The contract keeps the modules type until its
readers moved (the lead's ruling). The manifest validator, built at mesh-delivery's trunk, accepts the indexer in both
cases, change and trunk, and no verdict differs.

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

2026-11-11 11:46:55 +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)