mesh-delivery

Files

T

jschoubben 8b41346466 GR4 (§386, §644): the grants part tells catalogue.Hearing which events are defined

A seat definition's events of the seat list, and mesh-sdk's four finding events (views.FindingSubjects), so a `*` emitter before one reaches each declaring module's own stream; any other `*` entry stays the shared stream's.

Builds: design 47 G §386, §474, §644

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

2026-11-11 21:46:19 +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