signal-pipelinelisted

# Signal Pipeline Turn events into timed actions. A signal without a decay window and a routing destination is a notification, and notifications get ignored. ## When to use - Setting up trigger-based outreach - Signals fire and nothing happens, or everything happens - Evaluating or renewing an intent data contract - Reps say the alerts are noise ## Inputs - Reads: `workspace/data/object-model.md`, `workspace/data/scoring-model.md` - Needs from user: current signal sources and cost, what happens today when a signal fires, and last year's closed-won and closed-lost lists for the backfill test ## Workflow ### 1. Build the taxonomy with four properties per signal A signal is not usable until all four are filled in. Use `templates/signal-taxonomy.csv`. | Property | Why | |---|---| | **Decay window** | How long it stays actionable. A signal with no window is permanent, which means meaningless | | **Severity** | How strongly it predicts a conversation. Drives the threshold | | **Play** | Exactly what happens. Not "notify the rep" | | **Owner** | Who acts, by name or by role | Reference windows, adjust to your motion: | Signal | Decay window | Severity | |---|---|---| | Champion changed jobs to a target account | 30 to 60 days | High | | New executive hired in the buying function | 90 days | High | | Funding round announced | 90 days | Medium | | Hiring for roles that imply your problem | 60 days | Medium | | Competitor mentioned in a public posting | 45 days | Medium | | Pr