atris 3.31.0 → 3.33.3

package/README.md

@@ -12,6 +12,14 @@ Computer = workspace + files + tools + secrets + memory + agents + validation lo
 
 A computer can be personal or shared by a business. It can run a job like code, research, CRM, reporting, event ops, support, or business ops.
 
+## Quick Start
+
+```bash
+npm install -g atris
+cd your-project
+atris init && atris
+```
+
 ## For Coding Agents
 
 **Read [`FOR_AGENTS.md`](FOR_AGENTS.md) first** — why agents adopt Atris, 60-second start, spread-it instructions.
@@ -47,6 +55,7 @@ Then read the workspace's `atris/atris.md` and follow it exactly. `atris.md` is
 | `atris/features/` | Feature packs with `idea.md`, `build.md`, `validate.md` |
 | `atris/skills/` | Reusable skills for agents |
 | `atris/team/` | Team member specs and local context |
+| `atris/wiki/` | Repo memory, briefs, concepts, and wiki health |
 
 ```text
 atris/
@@ -56,7 +65,8 @@ atris/
 ├── logs/
 ├── features/
 ├── skills/
-└── team/
+├── team/
+└── wiki/
 ```
 
 ## Install
@@ -81,7 +91,7 @@ atris
 
 `atris init` scaffolds the workspace, including `atris/wiki/`. `atris` loads context and hands the workflow off to `atris/atris.md`.
 
-If you're still shaping the idea, use `atris brainstorm`. If you want Atris to keep cycling, use `atris run` or `atris autopilot`. If you want project memory checked for stale pages and missing context, use `atris loop`. `atris activate` surfaces wiki state from `atris/wiki/STATUS.md` when it exists.
+If you're still shaping the idea, use `atris brainstorm`. If you want one bounded mission pursued to proof, use `atris run "<objective>"`. If you want Atris to keep picking the next mission or member until you say stop, use `atris autopilot`. If you want project memory checked for stale pages and missing context, use `atris loop`. `atris activate` surfaces wiki state from `atris/wiki/STATUS.md` when it exists.
 
 Core loop: `plan` -> `do` -> `review`
 
@@ -186,14 +196,14 @@ atris business record atris/reports/2026-04-12-operator-recap.md --outcome mixed
 | `atris plan` | Create the plan/spec |
 | `atris do` | Execute work |
 | `atris review` | Validate work and capture learnings |
-| `atris run` | Auto-chain `plan -> do -> review` |
+| `atris run` | One bounded mission pursuit: start or resume, tick, complete (`--legacy` for the old plan/do/review chain) |
 | `atris run logs` | Browse glass run logs (phase reasoning persisted to disk) |
 | `atris run prune-logs` | Prune old run logs, keeping only the most recent N |
 | `atris run search` | Search phase reasoning across all run logs by keyword |
 | `atris run stats` | Show run log stats: phase counts, avg durations |
 | `atris run export` | Export all run logs as a JSON bundle |
 | `atris run diff` | Compare two run logs side by side |
-| `atris autopilot` | Guided loop with approvals |
+| `atris autopilot` | Keep the workspace moving: mission/member legs until `atris autopilot stop` (`--legacy` for the old approval loop) |
 | `atris pulse` | Install or run the durable overnight heartbeat |
 | `atris log` | Add inbox items to today's journal |
 | `atris now` | Show the current operating truth |
@@ -232,6 +242,38 @@ atris business record atris/reports/2026-04-12-operator-recap.md --outcome mixed
 - `atris pull` and `atris push` sync cloud workspaces and journals
 - `atris live` keeps a business brain fresh by checking/fixing the workspace, pushing local state, pulling cloud state, and pushing again after local changes go quiet
 
+## Engines
+
+An engine is the intelligence that builds a mission. Every installed headless coding CLI is a swappable worker behind one contract: a bounded prompt goes in, verified proof comes out, and engines never self-certify their own work. The house default is `atris-fast` (`ax`); the roster also covers `claude`, `codex`, `cursor`, and `devin` when their CLIs are installed.
+
+Show the roster and the current default:
+
+```bash
+atris engine
+```
+
+Flip the default for this workspace (persists to `.atris/engine.json`):
+
+```bash
+atris engine cursor
+atris engine reset   # back to the house default (atris-fast)
+```
+
+Ride a different engine for one run only, without changing the default. `--engine <name>` works on `mission run`, `autopilot`, and `run`. Per-run flags and `ATRIS_RUNNER_PROFILE` always beat the saved file.
+
+```bash
+atris mission run "fix the flaky login test" --engine codex
+```
+
+### Fleet Flight
+
+`atris mission run --fleet` staffs every idle installed engine on the board's claimable safe-lane tasks — one mission per task, one worktree per engine. Builds run in parallel; arrivals land serially with rebase-before-ship, so a rebase conflict pauses that landing (never auto-resolved) and keeps its worktree instead of orphaning work. Each flight writes a receipt to `atris/runs/fleet-<stamp>.json`.
+
+```bash
+atris mission run --fleet --slots 3          # staff up to 3 engines
+atris mission run --fleet --dry-run          # preview the staffing only
+```
+
 ## Verifiable Feedback Loop
 
 Under the hood, Atris can keep score on real repo work.

package/atris/CLAUDE.md

@@ -90,6 +90,14 @@ release/publish work; clean old merged worktrees with `atris worktree cleanup`.
 
 If the task produces durable project knowledge, update `atris/wiki/` or run the local wiki flow (`atris ingest`, `atris query`, `atris lint`).
 
+## How to Report
+
+The human approves work by reading, so how you report IS the product.
+
+- **Results are capabilities.** State what someone can do now that they couldn't before, then what it means for them or the business. Tests are one word ("verified"). Shape: "We did X, so you can now Y." Detail stays under the hood; the reader asks if they want more.
+- **Three results, air between them, rest on ask.** A report fits one screen with no scrolling.
+- **Stake first, then the move.** "Agents burn tokens hand-rolling parsers: add one shared view." Flags, ids, and identifiers belong in the body, never the headline.
+
 ## Rules (Non‑Negotiable)
 
 - Plan = ASCII visualization + approval gate. Do not execute during planning.

package/atris.md

@@ -80,6 +80,14 @@ The same discipline for words. Output stays sharp no matter how bloated the cont
 - **Cut filler.** Drop "it's worth noting", "in order to", "leverage", "seamless", "robust", "delve", stacked hedges, and em dashes. `atris slop` flags the prose tells (em-dash, hype-copy) too.
 - **Bound verbosity by information, not context.** Say the load-bearing thing and stop. Length tracks what the reader needs to act, nothing more.
 - **Match the register.** The operator wants the next move; a spec wants the contract; a journal wants one line. Jargon is a lever only when shared: use the reader's precise terms, define a new one once.
+- **Specific AND workable.** Vocabulary carries both: precise enough that another agent can act on it, plain enough that the operator gets it on a phone. A sentence only one of those audiences can use is half-written.
+- **Every queue item earns its surface.** Anything an operator might see (task title, mission objective, roadmap item, tick summary) carries its own why in the same sentence: what it costs to skip, or what it buys. "Agents burn tokens hand-rolling state parsers: add one shared inspect view" surfaces; "novel goal-chain demo" does not. Digests refuse raw titles that can't explain themselves.
+- **Day-one PM test.** Every sentence that reaches an operator must make sense to a PM who joined the company this morning: no internal codenames, no problem-titles standing in for results. If they'd have to ask "what does that mean?", the sentence is unfinished. Detail stays one ask away, always.
+- **Results are capabilities, not test counts.** When work lands, the sentence states what someone can do now that they couldn't before, then what it means for them or the business. Tests are one word ("verified"); the meaning is the sentence. Copy these shapes:
+  - "One word now runs the work: `atris autopilot` picks the next mission and keeps going until you say stop. Autonomy stopped being a setup and became a feature."
+  - "Missions survive everything: one engine starts the work, another picks it up cold, a third lands it. Work is no longer tied to a chat window, a session, or a vendor."
+  - "The system reports in plain English: one daily message with what landed, what waits on you, and who should own what's next. One person can supervise many projects."
+- **Fit the screen.** An operator-facing report shows three results, air between them, and holds the rest on ask. No scrolling: reading it is one glance, and the reader asks for more if they want more.
 
 `expected`: this is how an Atris agent writes and builds. Shipping slop or rambling is a failure smell, same as drift or a stale task.