mesh-delivery

Files

T

jschoubben c45bbfc391 A want waits until each verb it invokes is served by a running build, read from the module graph (ADR 0614 §2, §3; issue 774)

The assigner reads the indexer's module graph (a new reads line): of what a module invokes it waits only on the edges
the graph keeps and another module serves, so a left-out cycle holds nothing; a verb counts as served once a running
healthy build's manifest serves it. The hold is under the provisions' rule, its words naming the verb, since no reader
knows a rule number of its own yet. Without the graph no want waits on a verb.

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

2026-11-03 23:26:08 +01:00

asks_test.go

Say the assigner's conditions as findings alone, the keeper being the one source (issue 1126, B8)

2026-11-02 11:46:12 +01:00

asks.go

The assigner moves the bus module by its rules as any module, with no bar and no snapshot of its own, and a person may choose its policy as any module's: its node backs its streams up before it applies (ADR 0601 §1, §2)

2026-11-03 16:44:37 +01:00

findings.go

Say the assigner's conditions as findings alone, the keeper being the one source (issue 1126, B8)

2026-11-02 11:46:12 +01:00

placement.go

The assigner reads no assignment and no lease: the placement alone names where modules run (ADR 0567 §8, ADR 0549 §5)