mesh-delivery

Files

T

jschoubben fe025a3b73 A check that could not run is asked again on the node-engine seat's running of its part (milestone 47/G W6.9b, issue 1373)

The checker consumes node-engine.running (kept last per subject) through its durable
consumer and hands each running.<node>.<module> to PartRunning; a body naming no part
asks nothing and is said. Naming the not-heard part by its module (the seat git's holder,
a build seat's holder) waits on the catalog half's claims (W3.6): until then the part is
unnamed and the first running asks the check again.

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

Builds: design 47 G §253, §315

2026-11-11 14:49:20 +01:00

checkermsg

Take tidy's go.mod whole: mesh requirements at the zero version only, unused ones dropped

2026-11-06 00:52:18 +01:00

cmd

A check that could not run is asked again on the node-engine seat's running of its part (milestone 47/G W6.9b, issue 1373)

2026-11-11 14:49:20 +01:00

files

The check waits on the builder's builds of its candidate before it composes, so it composes with them (ADR 0603 §10)

2026-11-03 17:51:09 +01:00

internal/check

A check that could not run says so, releases its claim and waits for its part to run (milestone 47/G W6.9, issue 1373)