outboundlisted

# /operator-cmo:outbound Outbound is where an unsupervised agent stack does the most damage per token, because the output leaves your domain and lands in somebody's inbox with your name on it. ## The decision guard 1. Read the brief. No brief, no sequence. 2. Read `marketing/decisions/positioning.md`: the ICP, the disqualifiers, the problem language, and the proof lines. 3. Read `marketing/policy/ship-policy.md`. Outbound to a named account is tier C by default in the shipped policy, and you should not quietly lower it. 4. Read `marketing/policy/do-not-contact.md` if it exists. Every list you produce is filtered against it before it is written to disk. ## Build the list Apply the ICP as a filter, then apply the disqualifiers as a second pass, and **report how many accounts each disqualifier removed**. That count is the most useful diagnostic in this skill: a rule that never fires is not a rule, and a rule that removes 80% of the list means the ICP and the sourcing disagree. Every row carries: account, contact, role, the trigger that made them qualified, and the source of that trigger with a date. A row with no trigger is not a lead, it is a name, and it goes in a separate `no-trigger` file rather than into the sequence. ## Write the sequence - **Personalisation must be sourced.** Every personalised line names where it came from, in a `src:` field the reviewer can check. If you cannot source it, write the generic line. Inventing a detail about a real perso