Design 47 H: H-A-10's bound ends the record failed, the pipeline's outcome stays
Claude-Session: https://claude.ai/code/session_01JG73KHUnBze48rdua8u2sy
This commit is contained in:
@@ -49,7 +49,8 @@ A question no principle settles goes to the operator or to a record; it is marke
|
||||
- **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
|
||||
movers report `running` on their machines, with a bound per tier (a setting) whose end ends the delivery record `failed` with the finding `tier-late`,
|
||||
the pipeline's own outcome staying what its steps said; 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
|
||||
|
||||
Reference in New Issue
Block a user