Briefs and insights

Both features turn your collected data into a written draft. They are beta.

#How they work

1. Citeroot computes the facts in code: rates with intervals, the weakest prompts, stages and engines, competitor leads, source gaps and the latest audit's top issues.
2. Those facts, and only those, are handed to the writer, with an instruction not to invent numbers, quotes, competitors or URLs.
3. You get a Markdown draft you can edit, copy or download. Insights show the facts table next to the narrative so you can check one against the other.

If an Anthropic API key is configured on the deployment, Claude writes the draft. If not, you get a plainer template draft built from the same facts.

#Briefs

A brief is a content plan for one target: a question you're missing from, a gap source, or a topic you type. It suggests the question to answer, an answer-first paragraph, the evidence to include, sources to earn and how to measure the result.

#Insights

An insight is an investigation of the current state: where you are named, where competitors win, what to fix first.

#Limits

Per calendar month: Scout 0 briefs and 1 insight; Trail 3 briefs and 5 insights; Summit 50 of each; Expedition 500 of each. An insight needs at least five collected answers.

#Read before you use

A draft is a starting point. Check claims against your own product, don't publish text you haven't read, and remember that Citeroot only knows what the answers and audits showed it.