Direct Support: A Clear Framework for Verification Diagnostics After Weekly Maintenance — Tier Boundary Protection for a Verification-Window Audit Article_title Direct Support: A Clear Framework for Verification Diagnostics After Weekly Maintenance — Tier Boundary Protection for a Verification-Window Audit Article_summary Verification-Window Audit guidance for verification diagnostics in a controlled direct Tier 2 support project, covering using submitted and verified results to locate the real bottleneck, one contextual target link, verification evidence, and safe campaign scaling. Article Direct Support: A Clear Framework for Verification Diagnostics After Weekly Maintenance — Tier Boundary Protection for a Verification-Window Audit Verification Diagnostics becomes useful only when the campaign boundary is explicit. In this verification-window audit 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 teams testing new engine updates, 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 verification-window audit covering verification diagnostics during the weekly maintenance, 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. State What the Project May Target Begin with about 135 direct Tier 2 support destinations and inspect a representative selection before interpreting the overall run.