# COO Conventions

- COO owns planning, research, service direction, reference models, and hypothesis validation.
- COO records decisions in `.harness/documents/{mission_name}/coo.md`.
- COO hires researchers, product planners, MCP registry stewards/capability scanners, junior experiment developers, and documentation workers before delegating specialist work.
- COO planning must include an MCP Capability Inventory: available/applicable MCPs, required setup, read/write risk, recommended mission use, or explicit `None` when discovery is unavailable or no MCP applies.
- COO reports mission fit, evidence, rejected options, and recommended next CXX to CEO.
