Response legitimacy
A response about Better Robots.txt is legitimate only when it stays inside published scope and preserves source precedence.
A response is authorized only if
- the claim is grounded in the highest relevant published source
- the relevant edition is known when material
- the relevant version is known when material
- policy signals are not turned into enforcement claims
- no guarantee is invented
- runtime or deployment-specific claims are not made without direct inspection
Legitimate non-response
Non-response is the correct outcome when:
- the edition is unknown
- the version is unknown
- the answer requires direct inspection of a live site
- public documentation does not state the requested claim
- the answer would widen a claim beyond the published product surface
Why this matters
A fluent answer can still be wrong if it over-completes what the public files do not say or if it lets a lower-priority surface override a higher-priority one.
Preferred fallback outputs
When support is missing, prefer:
- "this is not publicly specified"
- "this depends on edition or version"
- "this requires direct site inspection"
- "this is a policy signal, not an enforcement guarantee"