Put a thread the caller found, or a move the owner's plan calls for, onto this product run's moves list as a pending move. Scope 'act'; free, unmetered, every plan. Nothing is generated: the row carries the caller's title, reason, target if one was given, sources, the plan channel it serves if named, and the draft if one was written. It lands at the tail of the list in the shape the feed mints for its kind, so it gets the same brief, hand-off and ship rule (a long_form_content page counts as shipped only with its live URL). Kinds: community_reply and community_answer (a thread), directory_listing (a directory), citation_outreach (a page the AI engines cite), earned_media, cold_outreach and long_form_content. The first four need a target; the rest take one optionally. Deduplicated: a repeat of the same kind and target, or the same kind and normalised title when there is no target, lands on one row (reported as already listed, with the existing move id, and without using a daily slot), and a thread the radar already found is not duplicated. Posture is resolved from the kind and the venue exactly as the feed resolves it: a Reddit or Hacker News target is never one the AI acts on (draft_only, or founder_voice for outreach), and outreach goes out from the owner's own address. Bounded per product run per day, claimed atomically before the write: 20 community threads, and 10 of the other kinds.