Design 47 H: H-A-10 is the order inside the one pipeline, tier by tier on running

Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
2026-11-20 01:43:20 +01:00
parent dae41a142f
commit 5f49bfd818
@@ -46,11 +46,12 @@ A question no principle settles goes to the operator or to a record; it is marke
pipeline's delivery order, written by the assigner from `pipeline-ended`; the node-engine applies a pipeline's wants
on its machine by rank and consumes no event of the runner. The apply-order read tool is the node-engine's.
Principles 9 and 12.
- **H-A-10 Order across machines** (ADR 0666 §14's "delivered before" edge between machines): no want is held for it
(the operator, 2026-11-17: every machine that places the module installs the latest version); a consumer whose
provider on another machine has not moved yet holds its own entry, says it, and reverts after its bound; the
composition step composed the whole graph before any want was written. ADR 0682 changes §14 so (asked of the record
writer, 01:46). Principles 3 and 7.
- **H-A-10 Order across machines** (ADR 0666 §14's "delivered before" edge between machines): the order lives inside the
one pipeline, never as a hold of a want on another delivery (A-478 b: "the order between modules moves into the
pipeline"): the assigner writes one pipeline's wants tier by tier in §14's order, a later tier once the earlier
movers report `running` on their machines, with a bound per tier (a setting) whose end fails the pipeline loudly; the
composition step composed the whole graph before any want was written. ADR 0682 says it (the record writer, 01:50).
Principles 3 and 7.
- **H-A-11 Publishing an event family stays the producer's**: every account may call every verb (ADR 0682), but a
module publishes only the events its manifest declares, as ADR 0666 §21 has it for a step's result; the mechanism
stays whole, who is on which side is not asked (who-may-is-not-the-operators-question). An enrolling node's account