Snippet governance workflow
- Inventory all short-form claim surfaces before editing the long review body; snippets often drift first because they are reused across cards and hubs
- Reduce every snippet to one buyer-safe promise plus one limitation when the underlying evidence is mixed or time-sensitive
- Compare snippet language against the evidence ledger, comparison table, FAQ, schema, and CTA so no surface overstates the verdict
- Refresh snippets after price, policy, availability, winner, or buyer-fit changes; do not let cached summaries preserve old claims
- Use Revneey main-site snippets as the golden template before adapting the process to vertical matrix sites
Golden-template migration note
This Revneey main-site asset strengthens docs-first review governance before matrix migration. Preserve vertical keyword boundaries and deploy from full output; do not overwrite lean keyofvenus or cosyhomer source directories.