Mission

Definition

A mission is a lead that cleared the bar and is now waiting for you — it carries the original post, a draft reply written for it, and its place in the approval workflow.

A mission moves from awaiting a draft, to awaiting your approval, to approved or rejected, and finally to sent once your own sender confirms it went out.

Approved missions are posted by your sender — the OpenClaw plugin or the standalone daemon — from your own account. The brain never posts anything and never holds your platform credentials.

Your rejections matter as much as your approvals. Telling the system why a lead was wrong is what teaches it which of your sources are worth listening to, so reject reasons are worth choosing accurately rather than clicking through.

Drafts are written to fit the channel they will go out on, so a public reply and a direct message are not the same length.

Related terms

  • Signal score →A 0–100 measure of how strong a buying signal a post represents.
  • Role-aware swarm →Three AI judges assess every candidate independently, and their disagreement decides what reaches you.
  • 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