@erclx/aitk 0.75.0 → 0.76.0
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/docs/agents/tasks.md
CHANGED
|
@@ -90,7 +90,7 @@ aitk tasks validate
|
|
|
90
90
|
aitk tasks validate --json
|
|
91
91
|
```
|
|
92
92
|
|
|
93
|
-
Four checks run. Plan and Collisions
|
|
93
|
+
Four checks run. Plan and Collisions reach one half each of the `## Run now` test the board standard states, and the second reaches only the collision reason that half names, since the other blocker kinds put no fact on disk to check against. Mapping and Grouping test the folder contract and hold for every group:
|
|
94
94
|
|
|
95
95
|
| Check | What it reports |
|
|
96
96
|
| ---------- | --------------------------------------------------------------------------------- |
|
package/package.json
CHANGED
package/standards/tasks.md
CHANGED
|
@@ -48,13 +48,15 @@ Group tasks by readiness rather than by status, one row per task, under the colu
|
|
|
48
48
|
|
|
49
49
|
Readiness is three groups under fixed headings, `## Run now`, `## Up next`, and `## Needs a plan`, in that order. The names are the contract rather than a suggestion, because a board grouped by readiness under names of its own satisfies every other rule here and still reads as empty to anything counting rows under a heading. Add no fourth group. A task belongs to exactly one, and the tests are read in order.
|
|
50
50
|
|
|
51
|
-
- `## Run now`: a written plan covers every open outcome, and the
|
|
52
|
-
- `## Up next`: a written plan exists, and the task
|
|
51
|
+
- `## Run now`: a written plan covers every open outcome, and the task carries no reason it cannot start. A collision against the files something already running touches is one such reason, and the `Touches` column is what states it. A worker is handed a task from this group alone.
|
|
52
|
+
- `## Up next`: a written plan exists, and the task carries a stated reason it cannot start. The `Waiting on` column names that reason.
|
|
53
53
|
- `## Needs a plan`: everything else. The task has no plan, or the plan it carries no longer describes the work.
|
|
54
54
|
|
|
55
|
-
Each group fixes its own columns, which follow from the test above it rather than from preference. Neither half of the `## Run now` test is checkable without the file set and the plan sitting beside the task. The
|
|
55
|
+
Each group fixes its own columns, which follow from the test above it rather than from preference. Neither half of the `## Run now` test is checkable without the file set and the plan sitting beside the task. The `Waiting on` column under `## Up next` carries that reason in one of three forms. `## Needs a plan` states no file set at all, because a task with no plan has no bounded one to state. A group with no rows keeps its heading and its header row.
|
|
56
56
|
|
|
57
|
-
|
|
57
|
+
Under `## Up next` a collision names the file held by the task already running, a sibling task names that task, and an external condition names both the condition and what would satisfy it. Naming what would satisfy it is what separates a blocked row from one nobody has examined, so a cell stating a condition with no way out of it fails the test. The header text is the contract the way the group names are, because anything reading the cell resolves the column by header rather than by position.
|
|
58
|
+
|
|
59
|
+
`aitk tasks validate` reads those columns and reports where a row's claim and the tree disagree: a plan pointer resolving to no file, a row and a task file that do not map one to one, a task in two groups, and two `## Run now` rows touching a path in common. It does not read the `Waiting on` cell, so that test holds on reading alone. Run it when the readiness claim is made rather than on a schedule, since the board is gitignored per-machine scratch and no shared moment exists to hang it on. It reports and never writes, so a session fixes the row it names.
|
|
58
60
|
|
|
59
61
|
```markdown
|
|
60
62
|
---
|