What is a personalised news brief?

What makes it a brief?

A brief has a scope and an end. You should be able to see what it covers, read the useful developments, and stop. A feed can keep adding items as you scroll. Neither format is right for every situation: a feed can be useful for exploring widely, while a brief suits a recurring question such as ‘what changed in this field?’

Personalisation starts with that question. ‘Technology’ leaves a lot open. ‘Battery recycling methods that could work outside a laboratory’ gives the researcher a subject, a boundary and a reason to prefer one story over another.

Streams, a roundup and stories

In Carrot, a stream is a saved research interest. Keep separate streams for topics you want to return to independently. Your roundup brings a few developments from those streams together. A story is the individual update you open for its explanation and sources.

For example, you might have a battery research stream and a film stream. The roundup gives you a starting point across both. Opening the battery stream takes you to that topic’s brief, rather than making you search through every film story first.

What should a useful story tell you?

A headline helps you decide whether to open something. The body should add what happened, the relevant context and the limits of the evidence. Repeating the headline in a longer sentence is not enough.

Look for links to the original material and clear dates. A story researched today may describe an older announcement. The research date, publication date and date of the event answer different questions; don’t assume they are interchangeable.

Carrot’s alpha keeps sources with the story and supports follow-up questions. You can ask what changed, what remains uncertain, or how a development compares with something you already know.

A brief is a starting point

An AI-written brief can omit context, misunderstand a source or miss a relevant development. Treat it as a way to orient yourself, not as complete coverage. When a decision depends on a claim, open the evidence and check it.

The useful test is personal: after reading, can you name what changed and decide whether you need to know more? If every item feels irrelevant, narrow the stream. If the explanations assume too much, change the writing style or ask for clarification.

Try our guide to writing a useful stream request, then see how that works in the current Carrot alpha.