docs: no user doc promises a launched session, a launch script or a fourth security layer
README claimed four security layers including scoped per-child tool access (gone with the launched children), an auto-dispatched Phase 7.6 recovery session and a launch template; architecture.md still pointed at launch.sh. They now describe what 6.0.0 does: session specs plus orders.md, a recovery order for a session the user opens, three layers. operations.md gets a status note instead of a rewrite (decision record). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
1636124152
commit
f5bbae7afd
6 changed files with 18 additions and 15 deletions
|
|
@ -58,7 +58,7 @@ protocol, thresholds, and the exact commands in
|
|||
| `--quick` | Plan directly (no agent swarm) |
|
||||
| `--min-brief-version <ver>` | (S18) Warn — never block — if the brief declares a version below `<ver>` (e.g. `2.2`), i.e. sidesteps framing enforcement |
|
||||
| `--export headless <plan>` | Legacy alias for `--decompose` — the only remaining export format (the `pr` / `issue` / `markdown` variants were removed; Claude reformats a plan ad-hoc on request) |
|
||||
| `--decompose <plan>` | Split plan into self-contained headless sessions |
|
||||
| `--decompose <plan>` | Split plan into self-contained session specs + `orders.md` (one starter line per session) |
|
||||
| `--gates {true\|false}` | (v3.4.0) Boolean autonomy-gate flag; present → gating on. Policy (`gates_mode`) detailed under `## Autonomy mode` in `docs/operations.md`. |
|
||||
| `--profile <name>` | (v4.1.0) Model profile for the plan phase (and others, since plan emits `profile:` to plan.md frontmatter). |
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue