ClarityQ resolves ambiguity rather than guessing at it. It uses your Context Layer - the table, event and semantic catalogs - to map loose phrasing onto the right tables, metrics and segments, then shows the generated SQL alongside a plain-English explanation of how it read your question.
If a question is genuinely open to more than one interpretation, you can see exactly which one ClarityQ took and refine from there, rather than being handed a number with no way to check it.
