Direct Support: Planning Platform Diversity Before the Next Weekly Maintenance — Article Quality Control for a Platform-Mix Review Article_title Direct Support: Planning Platform Diversity Before the Next Weekly Maintenance — Article Quality Control for a Platform-Mix Review Article_summary Platform-Mix Review guidance for platform diversity in a controlled direct Tier 2 support project, covering balancing contextual engines without treating every placement type as equivalent, one contextual target link, verification evidence, and safe campaign scaling. Article Direct Support: Planning Platform Diversity Before the Next Weekly Maintenance — Article Quality Control for a Platform-Mix Review Platform Diversity becomes useful only when the campaign boundary is explicit. In this platform-mix review for a direct Tier 2 support project, the destination is an imported Money Robot page that already points to the money site; it is never the money-site URL itself. For SER project managers, that rule keeps the link graph understandable and prevents a lower tier from accidentally bypassing the layer it should support during the weekly maintenance. For this direct Tier 2 support platform-mix review covering platform diversity during the weekly maintenance, the contextual destination appears once as tiered campaign checklist. One relevant link is sufficient for the page's purpose, avoids repeating the same destination inside a single document, and leaves the surrounding explanation readable. The anchor is selected from a plain topical pool in the project data, while the URL token is resolved by GSA only at submission time. State What the Project May Target Begin with about 12 direct Tier 2 support destinations and inspect a representative selection before interpreting the overall run.