classify-dm-intentlisted

# /classify-dm-intent — Runtime Intent Classifier > **Purpose.** Auto-classify an inbound DM thread (or queue of threads) into the correct acquisition-FSM state. Drives every routing decision after a prospect engages: which sequence to send, which qualification thread to run, when to surface to operator review, when to gate to application, when to archive. Wrong classification = wrong sequence = lost prospect. > > **Bar.** ≥85% agreement with operator manual classification on a 50-thread blind-test sample. Below 85%, signals + thresholds need recalibration. Misrouting a high-fit prospect into the cold sequence costs the close. > > **Why it's runtime.** The four intent classes from `reference/frameworks/dm/intent-taxonomy.md` are the *outbound* primitive. This skill produces the *full FSM-state* classification for inbound — 13 states a prospect could be in. Each routes to a different downstream action. ## When to invoke - Every inbound DM reply (webhook trigger: `dm.replied` per `paperclip.manifest.yaml`) - Every prospect added to outreach queue (pre-classification before sequence assignment) - Every application submission (route via `/triage-application`, but classify the source thread context) - Batch mode: nightly sweep of inbox to catch missed-reply states + reclassify decayed-class prospects - Operator-triggered: "what state is this prospect in?" advisory query - Before invoking `/write-dm-sequence` for a new prospect — confirms which class to write for ## Required in