mesh-delivery

Files

T

jschoubben 95e2427553 WM6 (§269): the watchman consumes the seat mesh-grants' wait-held and wait-ended, so a granting wait past its bound is acting-part-late

Its handler already takes any seat's wait events; the manifest's consumes gain the two. Not run here: the watchman does not build
against mesh-contracts' meshconditionsclient as it stands (the findings writer's migration is another developer's).

Builds: design 47 G §266, §269, G-20 A-12

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

2026-11-11 21:45:10 +01:00

mesh-delivery-assigner

CT15 (take-in bodies, none-yet): the seat mesh-catalog's bodies give take-in.taken and take-in.pending; revision answers none-yet in a field

2026-11-11 21:44:21 +01:00

mesh-delivery-builder

The builder, checker, view and watchman read a step key as SD4 has it: ParseStepKey answers asker, node and id

2026-11-11 21:16:18 +01:00

mesh-delivery-checker

CT15 (take-in bodies, none-yet): the seat mesh-catalog's bodies give take-in.taken and take-in.pending; revision answers none-yet in a field

2026-11-11 21:44:21 +01:00

mesh-delivery-forge-bridge

FB3, FB4, FB5: the bridge performs what the gate owes through the seat git and says each outcome, reads groups from the seat, and its owed tools