Direct Support: A Controlled Workflow for Engine Compatibility During First Controlled Test — Duplicate-Domain Control for a Failed-Target Recheck Article_title Direct Support: A Controlled Workflow for Engine Compatibility During First Controlled Test — Duplicate-Domain Control for a Failed-Target Recheck Article_summary Failed-Target Recheck guidance for engine compatibility in a controlled direct Tier 2 support project, covering testing current scripts against the platforms actually present in a list, one contextual target link, verification evidence, and safe campaign scaling. Article Direct Support: A Controlled Workflow for Engine Compatibility During First Controlled Test — Duplicate-Domain Control for a Failed-Target Recheck Engine Compatibility becomes useful only when the campaign boundary is explicit. In this failed-target recheck 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 solo campaign operators, that rule keeps the link graph understandable and prevents a lower tier from accidentally bypassing the layer it should support during the first controlled test. For this direct Tier 2 support failed-target recheck covering engine compatibility during the first controlled test, the contextual destination appears once as verified-link planning. 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. Keep Lower Tiers in Their Role The result is more stable verification data and a decision trail that remains meaningful when the list or engine set changes.