mesh-delivery

Files

T

jschoubben 92ce8c777c A-99: the build is every pipeline's first step, asked of mesh-builds for the module's own entry

The runner's step enum gains build; Place puts the build first, required whatever the policy names, and asks it of the
seat mesh-builds naming the module's own entry by fingerprint; the hearer takes mesh-builds' step-ended as the other
seats' ends, held to its one entry.

Builds: design 47 G §230, A-91, A-97, A-99

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

2026-11-11 23:34:17 +01:00

mesh-delivery-assigner

Merge branch 'feat/47-G-findings4' into feat/47-G-dev4-join

2026-11-11 22:25:53 +01:00

mesh-delivery-builder

G findings4 builder: the builder's findings are the seat's generated finding written through views.NewHeldWriter, its findings stream in manifest and bed

2026-11-11 22:18:58 +01:00

mesh-delivery-checker

Merge branch 'feat/47-G-findings4' into feat/47-G-dev4-join

2026-11-11 22:25:53 +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