Approval
Your approval is read, not judged
The word is matched against a pattern, and the author must have write access on that
repository. No model decides whether you meant yes, and the bot is filtered out so it can't approve itself.
How it is enforced
Authorship
One commit per approved task
Rookery ticks the checkbox and writes the commit, one for each task. Task sessions
run with git push and gh denied outright, so the agent
cannot publish.
How it is enforced
Limits
A daily limit, checked before every call
Each repository has a limit of model calls and of dollars for each day. Rookery
checks it before each call, and a run that reaches it stops with its work committed.
How it is enforced
Cost
Task 15 costs what task 1 did
Every task gets its own session, so context never snowballs across a long issue.
decisions.md is the only thing that crosses between tasks.
Isolation
One worktree per issue
Each issue gets its own branch and its own checkout, so two repositories can share an
issue number and never meet.
Throughput
Repos in parallel, one job per repo
Each repository drains its own queue, so a long run on one never blocks another.
Within a repo it is one job at a time, on purpose — two jobs on one issue would race
on its worktree and labels.