kingshand design decisions
These are the records kingshand keeps about how it runs and controls workers: what was decided, what prompted it, what it costs, and what would reverse it. They are mirrored from the repository when this site is built, so they say what the repository says.
The records
- Worker control plane: stay on claude --bg
- This record's own revisit trigger fired. It is kept because the reasoning is still the reason kingshand refused a heavier control plane for as long as it did, and because the trade table below is what the replacement...
- Worker control plane: herdr
- Kingshand spawns and controls workers through herdr. Each worker is an ordinary interactive Claude Code session running in a herdr pane, in a git worktree kingshand creates itself. claude --bg --worktree is gone, and...
- The data index - an index, not a classification
- The data index - an index, not a classification: a design decision recorded in the kingshand repository and mirrored here.
- Read first is declared, not parsed
- Read first is declared, not parsed: a design decision recorded in the kingshand repository and mirrored here.
- Noticing a worker that has stopped making progress
- Two failures on the same night, both costing real time, both invisible until the King asked.
- Text in a worker's input box that nobody sent
- A worker was found sitting idle with a well-formed instruction in its input box - show me the getting started section rendered. Nothing had sent it. It appears in no transcript, no brief and no report.md, because...
Where these come from
- Source: github.com/emgee-labs/kingshand/tree/main/docs
- Mirrored from commit
a7f9e180, dated 2026-09-02. - Anything not here - the README, the skills, the tests - is in the repository itself.
What the tool these records describe actually is, and how to get going with it, is on the overview.