boss: done-state is not a milestone close
Reference the single-source gate; a /boss done-state means the queue is empty, not that the tracker milestone may be closed.
This commit is contained in:
+6
-2
@@ -118,8 +118,12 @@ For each dispatched skill's result, decide:
|
|||||||
- **Bounce-back** — one of the four named triggers fired (see
|
- **Bounce-back** — one of the four named triggers fired (see
|
||||||
"Notifications" below). Send a notify, stop the loop.
|
"Notifications" below). Send a notify, stop the loop.
|
||||||
- **Done-state** — queue is empty AND the cycle is fully
|
- **Done-state** — queue is empty AND the cycle is fully
|
||||||
ratified (audit clean, fieldtest clean if applicable). Go to
|
ratified (audit drift-clean, fieldtest clean if applicable).
|
||||||
Step 5.
|
Go to Step 5. A `/boss` done-state means this run has nothing
|
||||||
|
left to dispatch; it is not an automatic milestone close —
|
||||||
|
closing a tracker milestone needs its end-to-end milestone
|
||||||
|
fieldtest green and stays a deliberate manual act (see
|
||||||
|
`../docs/pipeline.md` § Milestone-close gate).
|
||||||
|
|
||||||
### Step 5 — On done-state: Notify
|
### Step 5 — On done-state: Notify
|
||||||
|
|
||||||
|
|||||||
Reference in New Issue
Block a user