Review of issue 977: keep the plan's own order for its gates, hold a group only for a composed mesh-delivery, keep mark-ready one release, compare with the batch's start, fail a lone cycle (issue 977)

2026-10-17 21:37:37 +02:00
parent aac4bae5a4
commit 07b050790e
14 changed files with 259 additions and 24 deletions
@@ -205,6 +205,10 @@ func (p Plan) Batch() bool { return p.State == PlanAssembling || p.State == Plan

 // PlanDelivery is what a walk waits for and what came of the wait (novox/hq ADR 0239).
 type PlanDelivery struct {
+	// Order are the edges the plan's own order was drawn with (novox/hq ADR 0419): verb before caller, version skew,
+	// engine before controller. Kept on the plan because the catalogue's graph does not hold them, and the plan's gates
+	// (a later tier waits for the earlier to be applied) are read from them.
+	Order []Edge `json:"order,omitempty"`
 	// Awaits is who must say the walk may start: the seat whose holder owns the delivery.
 	Awaits string `json:"awaits"`
 	// Go is when it was let go, By by whom (the seat's holder, or a person's name) and Why.