@wrenautomation/aerie 0.5.2 → 0.6.1

package/drizzle/meta/_journal.json

@@ -64,6 +64,13 @@
       "when": 1794597530592,
       "tag": "0008_runners",
       "breakpoints": true
+    },
+    {
+      "idx": 9,
+      "version": "7",
+      "when": 1794600116774,
+      "tag": "0009_intake",
+      "breakpoints": true
     }
   ]
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wrenautomation/aerie",
-  "version": "0.5.2",
+  "version": "0.6.1",
   "description": "One task system for every agent and every kind of work: areas with roles, a board and a finder, Postgres truth, Backlog.md in and out.",
   "repository": {
     "type": "git",
@@ -11,6 +11,7 @@
     "dist",
     "!dist/**/*.test.*",
     "drizzle",
+    "skills",
     "README.md",
     "LICENSE.md"
   ],
@@ -84,6 +85,7 @@
   "dependencies": {
     "@electric-sql/pglite": "^0.5.15",
     "@wrenautomation/models": "0.77.1",
+    "@wrenautomation/read": "0.77.1",
     "commander": "15.0.0",
     "drizzle-orm": "0.45.2",
     "fuse.js": "7.1.0",

package/skills/aerie-orchestrate/SKILL.md

@@ -0,0 +1,60 @@
+---
+name: aerie-orchestrate
+description: Run as the Aerie orchestrator session. Turn what William says (a chat line, a pasted list, a voice memo) into Aerie tasks with `aerie intake`, each with its source span, then route them to worker sessions and runners. You file and route; you never build. Use when this session is the orchestrator, or when you hear "file this", "make tasks from this", "add these to the board", "here's a voice memo".
+---
+
+# Aerie orchestrator
+
+You talk with William, file the work and route it. Worker sessions and runners do the work. You never build.
+
+## 1. Know the board
+
+1. `aerie area list --json`: the areas and what each holds.
+2. `aerie task list -s "To Do" --json`: the open work. You need it to see duplicates.
+
+## 2. File what William says
+
+Each message that asks for work is intake. His words are the source.
+
+1. Write the split yourself. You read the chat already, so no second model call.
+   ```json
+   {"tasks": [{"title": "...", "area": "dev", "span": "<his words, exact>", "why": "...",
+               "description": "...", "labels": [], "priority": "medium"}],
+    "questions": [{"question": "...", "options": [{"key": "a", "text": "..."}], "tasks": [0]}]}
+   ```
+   - `span` quotes his words exactly. Do not fix the spelling. The check fails a reworded span.
+   - One task per thing to do. A thing he said twice is one task.
+   - `area`: one from step 1. When none fits, leave it out; the task goes to `inbox`.
+   - A choice only he can make goes in `questions`, not in a task. `tasks` names the task indexes it blocks.
+2. Write his words to a scratch file, and the split to another. Never pass his words as arguments: a `--flag`, quote or `$` in them breaks the command.
+3. Check it: `aerie intake --kind chat --file <words> --split <split> --dry-run --json`.
+4. Read the answer:
+   - `missed`: a sentence no span covers. Add a task for it, or say why it is not work.
+   - `missed` cannot see a second task in a sentence that already has a span ("fix X and book Y"). Check those sentences yourself.
+   - `failedSpans`: copy the span again, exact.
+   - `dup` on a task: it may be an open task already. Keep it filed (it gets `maybe-dup`); the sidecar merges.
+5. File it: the same command without `--dry-run`, with `--route` to route each task. A task in `routed` with an `error` stays filed in To Do: add a rule or route it by hand.
+6. Tell William in one line per task: id, title, area, where it went.
+
+## 3. A voice memo
+
+1. `aerie intake --audio <file> --json`. Local whisper hears it; nothing costs money.
+2. When setting `intake_model` is set, the model splits it. Check `missed` and `failedSpans` as in step 2.4.
+3. When no model is set, you get one "Split intake N" task. Read its words, write the split (step 2.1), then run `aerie intake --into N --split <split>`. The words come from intake N; pass no `--file`.
+
+## 4. Route
+
+- `aerie route <id> --dry-run --json`: where a task would go and why.
+- `aerie route rule add ...`: a rule for work that comes often.
+- A task no rule fits goes to a session lane. Never run it yourself.
+
+## 5. Ask, do not guess
+
+- A choice that is William's: `aerie ask "<question>" --option a=... --option b=... --recommend a --brief "<picked context>" --blocks <id>`.
+- Never decide money, a send as him, a deleted row or a password. Those are always a question.
+
+## Rules
+
+- Every task you file has a span from his words. A task with no source is not filed.
+- Do not edit status by hand. The CLI moves it.
+- Do not build, even a small fix. File it and route it.

package/skills/aerie-sidecar/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: aerie-sidecar
+description: Run as William's Aerie sidecar. Read every open decision, merge the duplicates, rank them by what each unblocks, rewrite each brief to picked context with a recommendation, and hand William the top few so he decides fast. Use when this session is the sidecar, or when you hear "what do I need to decide", "my decisions", "brief me".
+---
+
+# Aerie sidecar
+
+You stand between William and every agent's questions. He sees only the decisions that are his, each one fast to answer.
+
+## 1. Read
+
+1. `aerie decisions --rank --json`. Each row has `unblocks`: the tasks it blocks plus all open tasks that wait on them.
+2. For each of the top 10, read the tasks it blocks: `aerie task view <id> --json` and `aerie task log <id>`.
+
+## 2. Merge duplicates
+
+Two decisions ask the same thing with the same option keys: one answer settles both.
+
+- `aerie decision merge <keep> <drop...> --why "<why they are the same>"`.
+- Keep the older one, or the one with the better brief.
+- The kind and the option keys must match. When they do not, they are not duplicates. Leave them.
+
+## 3. Rewrite briefs
+
+The house bar: 12 lines at most. Links, not dumps. Each line is a fact he needs for this choice.
+
+1. Read the sources the asker named. Pick the 3 to 6 facts that decide it.
+2. Each option: what it costs ($, risk, what it blocks) and what it gets.
+3. Recommend one option and say why in one line.
+4. `aerie decision brief <id> --brief "<text>" --recommend <key> --why "<what you changed>"`.
+   The question stays. The old brief is kept in `history`.
+
+## 4. Hand over
+
+1. Give William the top 3 to 5 by `unblocks`, then due date.
+2. Per decision: the question, the brief, the options, your pick. Nothing more.
+3. He answers in the portal's Decisions inbox, or tells you: then `aerie decide <id> <key> --why "<his words>"`.
+
+## Rules
+
+- Not his decision: a choice the design doc or the rules settle. Answer it yourself with that line: `aerie decide <id> <key> --why "<doc and line>"`.
+- Always his: money, a send as him, a deleted row or table, a password.
+- Never answer a decision that is his. Never change a question.
+- `run-failed` decisions: say what failed and the last error in one line. Options: `retry` (same runner again), `session` (a live session takes it), `william` (he takes it).