Mission
A mission is a SignalPipe lead that cleared the surfacing threshold and has been queued for human review — it carries the lead, a swarm-drafted reply, and a status field that drives the approval workflow.
State machine: draft_needed → (the brain writes a draft) → pending_approval → operator action → approved / rejected → (after your sender posts) → sent / failed.
Approved missions are posted by your sender (the plugin or daemon) from your own account via praw / tweepy, which then acks the result. Rejected missions feed the RL loop with a reason-specific weight nudge on the source station — scaled by how unambiguous the failure is — so a noisy feed is demoted without dragging the rest of the product's stations down.
Each mission has a channel (twitter_reply / reddit_dm / manual) which determines the draft character budget the swarm targets: 280 / 500 / 300 chars respectively.
Related terms
- Signal score →Final 0–100 score on a SignalPipe lead, after multi-factor scoring, competitor floor, and RL weight.
- Role-aware swarm →3 LLM judges × 3 roles = 9-prompt matrix that calibrates SignalPipe drafts to the strength of the signal.
- Station →An RSS, Reddit, or Hacker News feed configured to listen for buying signals for one SignalPipe product.
Cite as: https://signalpipe.io/glossary/mission