Mission
A mission is a SignalPipe lead that scored above the 50-point 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 → (sidecar polls and writes a draft) → pending_approval → operator action → approved / rejected → (after sidecar posts) → sent / failed.
Approved missions are posted by the sidecar via tweepy or praw. After sending, the sidecar calls /actions/ack to mark the mission sent. Rejected missions feed the RL loop with a -0.02 weight nudge for the source feed.
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