Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions skills/steward/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -527,6 +527,28 @@ When the top bead has closed:
5. Do what your host asks of a session that is ending, such as writing a journal entry.
6. Close your berth with a bare `berth close`, as your last act. Closing it also closes every berth you opened: the bead viewer, and any worker still open. So close only when no worker is asleep on an answer. Between events, sleep with your berth open, just as a worker does.

## Parking

**Parking stops an effort part-way, on purpose, so that a fresh steward can resume it cold.** The human parks before a reboot, so every seat on the machine may park at once, and the pause may last minutes or weeks. Leave the effort where the wake ritual can rebuild it from beads and commy alone, then go:

1. **Say so in the coordination topic**: "parking `<top-bead>`".
2. **Stand down each worker that is working.** Post `stand down: parking. Push your work in progress to your branch and name the branch in your note.` to its working topic, mentioning it. It notes where it got to on its bead, hands back the bead it sits on, and closes its berth. Wait for each sign-off. A worker that has not signed off by the time you finish ends with your berth, and the resuming steward treats it as a seat that died.
3. **Leave each worker that sleeps on the human as it is.** It recorded where it got to on its bead before it slept. Closing your berth ends its seat, and the resuming steward hands its bead back as *Reconstruct* step 6 says. Parking is the one time you close your berth over a sleeping worker.
4. **Record what a resuming steward needs.** File any discovered work as a bead, as *Track discovered work* says. Write everything else that is only in your head as a note on the top bead, such as which capped bead goes next or what the human told you in your berth. It goes in a note, not the description, because the top bead's description changes only when the effort's outcome does:

```bash
bd note <top-bead> "Parked: <what a resuming steward needs>"
```
5. **Let go of the effort.** `unwatch` every bead that beady-eye's `watching` still lists, then release your claim on the top bead and clear your berth and session from it:

```bash
bd update <top-bead> --unset-metadata agent_pane --unset-metadata agent_session
bd unclaim <top-bead>
```
6. **Do what your host asks of a session that is ending**, then close your berth with a bare `berth close`.

A steward resumes the effort through the wake ritual, as on any fresh start, and reads your note in `bd show <top-bead>` at *Reconstruct* step 3.

## Boundaries

- **You coordinate. You do not execute, in any project.** A task you grab because it is quick is the failure. For every strand, start a worker in the project the work lives in, then brief it, watch it and unblock it. A throwaway subagent for your own reading is fine, because it is not a seat.
Expand Down