Gap → brief

Find prompts rivals pass, queue a brief, notify.

Find gaps → At least N? → Create brief → Notify

By comparing the same prompt across the last two runs: they were named and you were not, in an answer where you previously were.

As many as there are real gaps, and you can cap it. Most teams start at three a week, which is what one writer can actually absorb.

The prompt, the winning answer, the sources it used and the facts your page has to carry. Enough for someone to start writing without opening the panel.

It drafts; it does not publish. Turning on the CMS step sends the draft, still as a draft, to whoever reviews.

No. A prompt that already has an open brief is skipped until that brief is closed, which is why the queue does not become noise.

Whoever you name, by email or Slack, with the reason attached rather than a bare alert.

The brief is marked stale and drops out of the queue. Engines move on their own often enough that this happens weekly.

For most teams, yes. It converts measurement into a specific piece of work without asking anyone to interpret a chart first.