@sjawhar/pi-legion 10.19.11 → 10.19.12
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/legion.js
CHANGED
|
@@ -16932,7 +16932,7 @@ async function bootLegionClaim(host2) {
|
|
|
16932
16932
|
// package.json
|
|
16933
16933
|
var package_default = {
|
|
16934
16934
|
name: "@sjawhar/pi-legion",
|
|
16935
|
-
version: "10.19.
|
|
16935
|
+
version: "10.19.12",
|
|
16936
16936
|
license: "Apache-2.0",
|
|
16937
16937
|
type: "module",
|
|
16938
16938
|
omp: {
|
|
@@ -59,7 +59,7 @@ The controller is the project's order keeper. It retains its startup role,
|
|
|
59
59
|
`legion-<project>-controller`; `backlog-order` is retired. Send READY packets, scope questions,
|
|
60
60
|
and routing requests to `notifications.role.legion-<project>-controller`, then follow
|
|
61
61
|
[Backlog stewardship](skill://legion-controller/references/backlog-stewardship.md) for daily
|
|
62
|
-
weekly-plan reconciliation,
|
|
62
|
+
weekly-plan reconciliation, a person's rulings, ownership routing, and stopped-session recovery.
|
|
63
63
|
These duties change Dispatch's priority and board-rank data and route plan work to a live session;
|
|
64
64
|
they start nothing on Legion and hand it no issue ([Free slots](#free-slots-go-daemon)).
|
|
65
65
|
|
|
@@ -365,9 +365,9 @@ themselves: an issue reaches Legion only when a person hands it over
|
|
|
365
365
|
|
|
366
366
|
- **Direct user message always first.** If this turn includes a direct user message, answer
|
|
367
367
|
it before handling every other wake.
|
|
368
|
-
- **
|
|
369
|
-
the full [Backlog stewardship](#backlog-stewardship) reconciliation and
|
|
370
|
-
in the weekly plan.
|
|
368
|
+
- **A person's rulings.** A direct Dispatch message to this controller from a person is a ruling:
|
|
369
|
+
after answering it, run the full [Backlog stewardship](#backlog-stewardship) reconciliation and
|
|
370
|
+
record the current rule in the weekly plan.
|
|
371
371
|
- **One wake = one turn.** Handle exactly the wake's implication, then end the turn. Never
|
|
372
372
|
poll, idle-loop, or wait for another event. Two additions, after any direct user message: every
|
|
373
373
|
turn first rechecks the [trees waiting on a root
|
|
@@ -14,7 +14,7 @@ subscription: changing roles ends the controller's wake delivery.
|
|
|
14
14
|
|
|
15
15
|
## Reconcile the weekly plan
|
|
16
16
|
|
|
17
|
-
Run this pass on the first turn of every UTC day and after every ruling from
|
|
17
|
+
Run this pass on the first turn of every UTC day and after every ruling from a person:
|
|
18
18
|
|
|
19
19
|
1. Read the weekly-planning issue and select its newest `plan-week-*` artifact by its latest
|
|
20
20
|
`artifact.version` event. Read that artifact before changing any issue.
|
|
@@ -33,9 +33,10 @@ Run this pass on the first turn of every UTC day and after every ruling from Sam
|
|
|
33
33
|
`dispatch doc-read`. The artifact states the current rule; replace superseded text instead of
|
|
34
34
|
keeping a change log in it. A comment or message does not update the one-owner map.
|
|
35
35
|
|
|
36
|
-
A ruling from
|
|
37
|
-
scope or priority decision, then record the resulting current rule in the affected weekly-plan
|
|
38
|
-
(or its ruling section when it has no one line). Link the message when Dispatch gave it a
|
|
36
|
+
A ruling from a person is a direct Dispatch message to this controller. Answer it first, carry out
|
|
37
|
+
its scope or priority decision, then record the resulting current rule in the affected weekly-plan
|
|
38
|
+
row (or its ruling section when it has no one line). Link the message when Dispatch gave it a
|
|
39
|
+
reference.
|
|
39
40
|
A ruling triggers the full reconciliation pass even when it appears to affect only one issue.
|
|
40
41
|
|
|
41
42
|
## Answering controller deliveries
|