define-missionlisted

# /define-mission — Agency Mission Statement > **Purpose.** Build the agency's mission statement — the **durable why** that survives pivots, sets the program tier's pedagogy, filters which clients to take vs. decline, and gives the team a north-star that doesn't move when next quarter's revenue target moves. Different from positioning: positioning is *market-facing* (for whom, against whom, with what mechanism); mission is *operator-facing + team-facing* (why this work exists for the people doing it). > > **Bar.** A mission statement passes when the operator can read it 12 months after writing it and still say "yes, that's why I'm doing this" without flinching, and when the agency's first hire can read it on day 1 and use it to make a judgment call without consulting the operator. If it's a wall poster nobody references, it failed. ## When to invoke - Cycle 1 onboarding — the first foundations skill an operator runs (lower threshold than `/build-positioning` because mission is a generative input to ICP/voice/offer, not a derivative of them) - After a period of "yes-to-everything" intake — operator has taken on 3+ misfit clients, can't articulate why each was a mistake; mission gap is the diagnostic - Pre-program launch — the program tier (`product_strategy.program_tier`) needs a pedagogy backbone, not just a curriculum; mission supplies it - First key hire — operator about to bring on first ghostwriter, account manager, or operator-of-the-operator; the hire needs a why-fil