Source registry and verification status

Verification rules

• Prefer official documentation, generated CLI schema, and pinned repository content.
• Record source URL, commit/release or observation date, verification date, compatibility range, content hash, and reviewer.
• When an official source changes, create a semantic diff and map it to affected claims and routes.
• Never silently overwrite reviewed production content from an upstream feed.
• Mark unsupported or unverified guidance stale; do not rely on a date badge alone.

External pricing and community evidence

Pricing pages are volatile and can differ by account, region, commitment, currency, or promotion. Calculator defaults are editable examples. Community reports may reveal a symptom or demand signal, but they do not replace official behavior documentation or reproduction evidence.