Who may run it

Part of team remove — the owner, the orchestrator, the operator and the approved delegate — and the caller-role refusals shown.

A file with a delegates section also admits one more caller: the approved delegate, a pane the owner named in that section as <session>/<pane id>, outside the team. When the ordinary rule above refuses and the file names a delegate, the delegate gate decides — it re-reads the live file and the approval in force, never a remembered copy — and a caller it passes runs this command as that delegate. The delegated remove is the ordinary removal of a named seat: --keep, --abandon, --session and --file stay the owner's, the orchestrator's and the operator's seats stay the owner's, and a delegated remove never re-signs the approval — the one signing a --keep does is closed to it. A --file or --session a non-owner aims is the gate's too, once the file names a delegate: the gate refuses it before the flagged file or the flag's session is read, on the eligibility of the default live file alone — the flagged file is never opened. With no delegates section nothing changes: the same refusals, the same words, the same exit codes, those two flags' included. A delegated run that proceeds is attributed in the log before its effects, as <time> delegate [delegate] <session>/<pane id> remove.

The ordinary rule this delegate gate defers to — the owner, the orchestrator and the operator, and the placement it proves — is on the team remove page.

The caller rules, shown

Anyone else — the orchestrator, the operator, or the approved delegate — meeting a seat herdr reports idle or done takes the seat out and leaves the pane as it is instead; the example below shows that removal, and a seat herdr reports working is refused to them too, with their own way out named.

The leave this names — the removal a caller other than the owner makes — is on the what-it-prints page.

An implementer's seat may not remove anything — not even itself:

$ team remove claude-beacon ; echo "exit $?"
team remove: only the owner, the orchestrator or the operator runs it; this call is claude-beacon
exit 1

The orchestrator's seat may remove others, never itself, and --abandon is the owner's own, from a terminal outside herdr:

$ team remove claude-keeper ; echo "exit $?"
team remove: only the owner removes the orchestrator's or the operator's seat; this call is claude-keeper
exit 1
$ team remove claude-beacon --abandon ; echo "exit $?"
team remove: only the owner abandons a seat, from a terminal outside herdr
exit 1