outbound-emaillisted

# Outbound Email ## Runtime authority The research and copy rules below remain authoritative for email content. For goal state, orchestration, approval, execution, evaluation, and reporting, use `.agents/company/` through the `outbound` Department. Never invoke a channel module directly. From the repository root, operate email goals with: ```sh PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=.agents python3 -B -m company status GOAL_ID PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=.agents python3 -B -m company once GOAL_ID PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=.agents python3 -B -m company approve GOAL_ID PYTHONDONTWRITEBYTECODE=1 PYTHONPATH=.agents python3 -B -m company report GOAL_ID ``` Never select `execution_mode: live` or approve a prepared batch for the user. An unmet run with a valid next experiment continues automatically; the next send still parks for approval. `company next` is only a manual escape hatch. # Personal Cold Email + Sending Workflow Three parts, one loop: 0. **ICP**: read `../../../company/strategy/icp.md` before any outreach. The Department-specific countries, tiers, and lead-flow rules live in `../../../company/departments/outbound/strategy.md`; they may not redefine ICP. 1. **Content**: research-first, one-person voice, personal cold emails (and DMs) that read like a specific human wrote them to one specific human. 2. **Sending**: the Outbound Department reads the master lead list (`.spielos/data/outbound/`) and acts through guarded provider adapters.