mesh-delivery

Files

T

jschoubben f0b51bfc29 The indexer keeps its catalog graph revisions in its object bucket catalog-revisions, each entry once by digest (milestone 47/G W4.2)

Design 47 (Two graphs) keeps each revision as the list of its entries' digests and each entry as one object, so an
unchanged entry is stored once. The bucket is declared in the old objects section with a 512 MiB cap (ADR 0619 §2:
the indexer is the foundation), opened at its first use; a revision's list is written only after its entries, and a
revision read back with an entry lost is an error naming the module.

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)