Burndown workflow
- Group stale work by reusable proof tasks: policy snapshot, screenshot capture, schema sync, table audit, or FAQ refresh
- Fix claims closest to CTAs first because they influence buying decisions directly
- Use source-date patches for stable claims and full verdict reviews for volatile comparisons
- Do not add new affiliate angles until old evidence debt is below the launch threshold
- Record each update in the page body, schema metadata, hub link, and MEMORY deployment log
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.