Source-check routes for AI answers

AI answers need a source-check route when the answer could affect a decision, a cost, a deadline, or someone's trust. The route should say where to verify the claim and what evidence is strong enough.

## Match source to claim
A pricing claim needs the vendor page. A legal or policy claim needs the official rule or a qualified secondary source. A software behavior claim is strongest when checked against documentation, release notes, or a reproducible test.

## Separate freshness from authority
An authoritative page can still be stale. A recent forum post can still be wrong. Good checking considers both: who is saying it, and whether the page reflects the current version or date.

## Keep disputed claims visible
If sources disagree, do not flatten them into one confident sentence. Name the disagreement and the date checked. That is more useful than pretending certainty.

## Store the route
A reusable answer should include enough source context that another reader can re-check it later: source name, target page, date, and what exact claim it supported.

Source-check routes for AI answers

// COMMENTS

ON THIS PAGE