Conflict checks
- Every high-intent claim has one controlling source or a visible caveat explaining uncertainty
- Price, availability, policy, spec, and warranty conflicts are fixed before winner or best-for labels go live
- CTA copy, merchant card copy, table cells, FAQs, and schema do not preserve old claims after the article body is corrected
- Conflicts that cannot be resolved are held from sitemap/indexation or routed to consolidation rather than shipped as thin trust debt
- Deployment uses full dist-cf-pages output and does not overwrite keyofvenus/cosyhomer lean directories
Golden-template migration note
This Revneey main-site asset strengthens docs-first claim governance before matrix migration. Preserve vertical keyword boundaries and deploy from full output; do not overwrite lean keyofvenus or cosyhomer source directories.