rule id reference
rule ids give agents and support notes a stable way to talk about repeated issue types without relying on vague highlight text.
quick answer
use rule ids when logging, debugging, or explaining a recurring pattern across documents.
use this for
- agent-readable analysis output
- supporting repeat issues
- mapping highlights to product behavior
steps
- run a voice check or api analysis.
- read the rule id attached to the issue.
- look up the user-facing meaning.
- decide whether to fix, allow, reject, or learn from the pattern.
details to know
- rule ids can represent ai patterns, voice mismatches, trust issues, and positive signals.
- the visible tooltip should stay plain even when the internal id is technical.
- stable ids help integrations avoid brittle string matching.
limits and edge cases
- do not expose internal-only ids that are not part of the public contract.
- do not rename public rule ids without migration notes.
- rule ids explain the type of issue, not whether every instance is correct.
ready to use the product instead of reading about it?
open app