department-runnerlisted

# Department Runner Use the shared runtime in `.agents/company/`; do not create channel-specific state machines. Inspect the Department/workflow/agent catalog with `python3 -B -m company catalog` using `PYTHONPATH=.agents` and `PYTHONDONTWRITEBYTECODE=1`. Create or select one measurable Department goal, then use `once`, `status`, `approve`, `pause`, `resume`, and `report`. Preserve the five-stage contract and surface every suspension. A completed unmet run with a valid next experiment continues automatically; the next guarded action still parks. A Department supplies domain observation, diagnosis, artifacts, guardrails, execution and measurement; the runtime owns transitions, all goals, state, leases, approvals and events. Every execution must preserve a typed run, hypothesis, Department version, config snapshot, controlled and changed variables, evidence validity, decision, and evaluation. A technical system test can validate machinery but cannot establish market or positioning truth. ## Generic work-order execution Do not require a host-specific agent file for an installed agent. The durable work order is the complete portable execution contract. 1. List available assignments with `company tasks --status active`. 2. Claim exactly one with `company tasks WORK_ORDER_ID --claim HOST_AGENT_ID`. A claim is exclusive; never perform an order claimed by another host. 3. Read that order's `brief`, resolve its agent from `company catalog`, and load only the listed `skill_