Answer A-352: a bus module's running build counts while its newer build waits for the operator's yes
mesh/delivery merged: source.main moved to novox/hq@0bbcf98baa96
mesh/check checking 328ca1b32047 on 0bbcf98baa96

Claude-Session: https://claude.ai/code/session_01NcbgfGKaxw984XyAPfLm4h
This commit is contained in:
2026-11-13 13:09:39 +01:00
parent 258de07806
commit 328ca1b320
@@ -711,3 +711,7 @@ the principle that settles it, cited as "design 47 G A-n".
version the builder gave a number, numbered or published, since that is the version the module was built against; a
filled version or edge whose number the builder kept no digest for carries none (the fill needs only the number to
count above it, and a filled edge is stale until the module's next build).
- **A-352** (ADR 0614 §5 and §2; principle 3) The assigner's bus-state rule counts a build that offers `bus-state` and
runs healthy from the holder's have, also while a newer build of the bus module waits for the operator's yes: the
running build serves the bus state, so a consumer that needs none of the new build's forms is not held; a consumer
whose new form only the new build reads still waits for it by its edge of kind 4 (§50).