# Omagy Team Runtime Rules

Team is a durable tmux runtime. Do not model it as native agy subagent fanout.

- The leader owns startup, monitoring, checkpoint/integration, and shutdown.
- Workers claim tasks and update lifecycle state only through `omagy team api`.
- `.omagy/state/team/<team>` is the source of truth, but direct JSON edits are
  prohibited outside the runtime implementation.
- Worker panes are triggered through tmux dispatch, but task ownership and
  completion are valid only after the corresponding API state transition.
- Shutdown requires terminal task state unless the leader explicitly uses
  `--force`.