lifecycle-and-routinglisted

# Lifecycle and Routing Define stages as exits, route deterministically, and measure the SLA rather than publishing it. Most lead-quality arguments are handoff-definition arguments in disguise. ## When to use - Sales says the leads are bad and marketing says the leads are fine - Inbound sits untouched - No written stage definitions, or written ones nobody follows - Territory or ownership changes ## Inputs - Reads: `workspace/data/scoring-model.md`, `workspace/data/object-model.md` - Needs from user: current stage list, how a lead reaches a rep today, the ownership rules, and one recent example of a lead both sides disagreed about That last example is the most useful input in the whole skill. Work the specific case rather than the abstraction. ## Workflow ### 1. Define every stage as an exit, not an entry The single change that fixes most lifecycle problems. An entry definition ("an MQL is a lead that downloaded something") tells you nothing about what happens next. An exit definition names what must be true to leave, who decides, and where it goes. ``` STAGE: <name> Enters when: <condition> Exits when: <specific, checkable condition> Who decides: <role> Exits to: <next stage, or disqualified with a reason> Max time in stage: <n days, then it is escalated or aged out> ``` **The max-time field prevents the silent graveyard.** Without it, records accumulate in a middle stage forever and the stage becomes a place things go rather than a