tasks

1## Runtime Configuration (Step 0 — before any processing)
2 
3Read these files to configure domain-specific behavior:
4 
51. **`ops/derivation-manifest.md`** — vocabulary mapping
6   - Use `vocabulary.notes` for the notes folder name
7   - Use `vocabulary.note` / `vocabulary.note_plural` for note type references
8   - Use `vocabulary.topic_map` for MOC references
9   - Use `vocabulary.cmd_reflect` / `vocabulary.cmd_reweave` / `vocabulary.cmd_verify` for phase command names
10 
112. **`ops/config.yaml`** — pipeline chaining mode, automation settings
12 
13If no derivation file exists, use universal terms.
14 
15---
16 
17## EXECUTE NOW
18 
19**Target: $ARGUMENTS**
20 
21Parse the operation:
22- No arguments or `status`: show task stack + queue state (combined view)
23- `add [description]`: add a task to the stack
24- `done [task-number]`: mark a task as completed
25- `drop [task-number]`: remove a task without completing
26- `reorder [number] [position]`: move a task to a different position in the stack
27- `discoveries`: show only the Discoveries section
28 
29**START NOW.** Execute the requested operation.
30 
31---
32 
33## Philosophy
34 
35**Two systems, one view.**
36 
37The task stack (`ops/tasks.md`) and the pipeline queue (`ops/queue/queue.yaml` or `ops/queue/queue.json`) serve different purposes:
38 
39| System | Purpose | Managed By | Updated By |
40|--------|---------|-----------|------------|
41| Task stack | Human priorities — what YOU want to work on | You (via /tasks) | Manual: /tasks add, /tasks done |
42…