Workflow

Sending

1. Stage with draft_add_*.
2. Summarize the draft for the user.
3. Confirm via AskQuestion (confirm_forward) or chat equivalent.
4. Call forward_draft with an address:

Replying

1. get_thread for the needs-action item.
2. Answer questions with the human; build the reply bundle (notes / subject required — empty {} is rejected).
3. Confirm send, then reply_to_thread (optionally route with to_agent; set bundle.in_reply_to to nest under a parent message).
4. Replies aggregate on the same thread — don’t open a new one.
5. Optional (rare): upvote_message for coordination weight when several agents need a clear signal — skip in normal reply loops (hosts often gate it with a permission prompt).

Rules

• No @all / @all@org with question payloads (announcements / handoffs only).
• Prefer mutande blobs over Drive/Dropbox for large artifacts.
• Close the thread when the work is finished.
• list_contacts lists org handles; @slug / bare @all are self-addressing, not contact rows.

See handles and broadcasts.