What it requires. A topic's stated scope promises to answer about a domain that its grounding does not cover.
Why it matters. The scope is what the planner routes on and what a reader takes as the agent's remit. Where it is broader than the grounding, requests route in correctly and are answered from nothing relevant. This is an irreducibly semantic check and is reported as a judgement rather than a measurement.
How to fix it. Narrow the scope to what the grounding supports, or widen the grounding to match the promise.
Source. Our grounding quality specification v1, section 3
Is this rule worth checking?
Votes and comments are published here. We read them, and we publish what we change with the reasoning — a vote does not move a rule on its own.