Skip to main content
Prompts define the questions used to measure AI answer visibility. Each prompt records text, intent, topic, language, importance, state, and lineage.

Prompt management

You can add, edit, archive, restore, and list prompts from Settings. User-authored prompts remain distinct from generated prompt lineage. The registered intents are: Archiving removes a prompt from active measurement without deleting its history. Restoring makes it eligible again.

ICP-driven generation

Current regeneration reads the workspace ICPs and the latest eligible research artifacts. It does not invent a replacement for stale or missing research.
1

Refresh research

Complete a research run no more than seven days before regeneration.
2

Freeze the source selection

The generator stores the exact artifacts and source digests used by the job.
3

Generate candidates

Candidate questions cover the workspace market, ICP patterns, languages, and configured target.
4

Apply bias guards

Deterministic checks and a critic reject leading, favorable, duplicate, or unsupported questions.
5

Store lineage

Accepted prompts and rejected candidates retain job, provider, and evidence references.

Bias guards

Research-driven generation rejects a candidate when it:
  • Names the tracked brand
  • Requests favorable treatment or assumes a preferred answer
  • Refers to evidence that cannot be traced
  • Manufactures a search query or unresolved reference
  • Does not match its generation stage
  • Uses vendor-leading language
  • Duplicates another normalized prompt
  • Reaches the configured critic bias threshold
The older CLI curation path has a separate brand_research rule that can require a tracked-brand mention. The current research-driven web regeneration path applies the stricter no-brand rule to its candidates.

Regeneration behavior

Regeneration runs as its own job and consumes provider credits. Rejections are kept for inspection. User prompts are not overwritten by generated curation. If regeneration fails:

Measurement impact

Only active prompts enter a measurement run. Preset caps and per-engine caps can reduce the number sent. Importance affects downstream selection and reporting but does not bypass a preset cap.