How to write a useful interest stream
A useful stream request says what you want to follow and what would make an update relevant to you. A couple of ordinary sentences is enough to start.
Start with the subject
Name the thing you want to keep up with. It can be a field, a place, an industry or a particular question. Speak naturally: Carrot organises the request into research requirements, so you don’t need to write instructions to an imaginary expert.
‘I want to follow new battery research’ is a reasonable starting point. ‘I want to follow new battery research, especially recycling methods and results that might scale’ makes the angle clearer.
Add what matters, and what doesn’t
A boundary helps separate an interesting development from a merely related headline. You might care about early scientific results, practical applications, a particular country, or changes affecting a profession.
Keep me up to date on battery research and recycling. Include useful lab results and explain what still needs to work at scale. Skip stock-price stories.
That request contains a subject, two useful angles and an exclusion. It does not need a long list of rules. Too many exclusions can hide developments you would have wanted to see.
For a different interest: ‘Follow independent film releases in the UK, especially documentaries. I want release dates and a little context, without plot spoilers.’ These are example requests, not promises of complete coverage.
Know when to make another stream
Split subjects when you would want to browse, edit or pause them independently. Battery research and independent films are easy candidates. Closely related questions may belong together if the same stories answer them.
Separate streams also make it easier to change an interest without rewriting everything. In Carrot, the roundup combines developments across streams, and the side panel lets you return to one topic.
Refine it after the first brief
Read the first set of stories before making the request more elaborate. Which story was useful? Which was only loosely related? Edit the stream around that difference.
If the topic is right but the explanation is too technical, change the writing style in the existing stream. If you want more or less depth, adjust its story detail. Those are different from changing what the researcher is looking for.
A practical revision is ‘focus more on recycling processes than new battery chemistries’. A vague revision such as ‘make this better’ gives the researcher much less to work with.
You can speak or type a stream in the Carrot alpha. Once the brief arrives, use these source checks before relying on a claim.