Operating workflow
- Capture the current verdict or FAQ answer, the visible module where it appears, and the evidence source that supports it.
- Compare body copy, table rows, FAQ block, FAQ schema, CTA label, and merchant page against the latest evidence.
- Classify the issue: stale winner, unsupported answer, snippet mismatch, unavailable product, policy drift, or unresolved owner sign-off.
- Update all affected modules together and keep a change record with source URL, check date, owner, and rollback trigger.
- Deploy the full Cloudflare Pages output and verify preview URL, production URL, sitemap, and hub links return HTTP 200.
Reusable fields
PageModuleClaimEvidence source
Last checkedRiskOwnerRollback trigger
Publish gate
- No verdict, FAQ answer, or schema node contradicts current evidence.
- Comparison winners and FAQ snippets are backed by dated sources.
- Hubs and sitemap expose the new asset without stealing matrix-site keyword boundaries.
- Lean keyofvenus and cosyhomer directories are not overwritten; deployment uses Revneey full output.