Routing workflow
- Start from the buyer decision, then attach the proof pages that make that decision credible
- Each hub card should clarify whether it supports link hygiene, review quality, schema, disclosure, comparison, or coupon pollution cleanup
- Prefer exact but conservative anchors: proof-backed, updated, checked, or methodology-driven only when the destination supports it
- When proof gets stale, downgrade anchors and snippets before traffic quality declines
- Record changed routes, deploy URL, report path, and next review cadence in MEMORY.md
Golden-template migration note
This Revneey main-site asset hardens internal link routing and proof destination governance before matrix migration. Preserve vertical keyword boundaries and deploy from full output; do not overwrite lean keyofvenus or cosyhomer source directories.