jschoubben
8501968154
No pause between two failed asks runs past the bound (two minutes): the ask at the bound raises first-view-unanswered and releases the held events, well inside the events consumer's five deliveries of 30 s. An answer's binding is taken as it lists it, with no fallback to an event's types (§4). Checks: the unit start row requires the raise at exactly the bound; the whole test says the created before the bound and requires the condition raised when it is applied (fails without the process's hold), and waits on the kept first-views status for the held answer instead of a sleep. Builds: design 25 bindings-first-view §3, §4, §5, §8 (hq d0760629, PR 543) Claude-Session: https://claude.ai/code/session_01JG73KEq4zoDfM9WtYpcQgZ
mesh-delivery
Novox Mesh — delivery: the parts that build, check and deliver a change by watching and writing keys on the bus (ADR 0429).
Made by the mesh from the gitea module's config value repositories (novox/hq ADR 0428). Main takes no push: a change reaches it by a pull request whose mesh/repo-check (this repository's merge-check.sh) and mesh/merge-gate passed.