Part 3 · Operate
Community capture
Three ways a question gets in, and the line none of them crosses.
01What it is
A question from a community reaches your queue three ways: you select it in the browser, you forward it to your capture address, or you paste it. All three run the same pipeline.
02Why it exists
The public sweep reads open rooms. Most of the good questions are asked in rooms it cannot reach: a private Slack, a Discord, a paid group.
The line is that the product captures what you deliberately mark and never what you scrolled past. Ingesting a channel you were let into is surveillance, and it ends memberships. Losing the community costs more than any conversation inside it.
03How to use it
- 01Select a message in a browser and press the shortcut.
- 02Forward a message or a digest to your capture address, which is on the Today screen.
- 03Paste a message into the box on Today or Conversations.
- 04Read the reply it drafts before posting it. You post, in your own account.
04What good looks like
- You give it
- Somebody in a private Slack asks how to tell when an account is evaluating.
- You get
- Captured, classified as a comparison, and a reply drafted that answers the question first and discloses the product once at the end.
- Why
- The community gate requires an answer that stands on its own before any mention, measured on what remains when mentions are stripped.
Observed in a real run
05What weak looks like, and what it costs
- You give it
- A draft that mentions the product before answering.
- You get
- Refused by the community gate, stored with the reason, never queued.
- Why
- Answer-first is a hard gate, because a reply that pitches is what gets somebody removed from a room they cannot rejoin.
Derived from the rules in the code