Deployed regional assignment lifecycle

Verification Boundary

The suite calls development services and uses their public record reads to inspect regional outcomes. Browser journeys may also cover work outside Regions; this register counts only the regional assertions.

What This Suite Proves

The linked source assertions contribute checks for references block removal; moving the deciding address changes placement; lost deciding input clears calculated placement; policy saves preserve existing placements; recalculation applies changed coverage; explicit recalculation applies saved coverage. A scenario spanning several files relies on those assertions together; this file supplies only its named checks.

What It Does Not Prove

The register establishes neither a current passing run nor verified conformance. Unbound scenarios, broader feature chains and the delegated infrastructure beyond this execution boundary remain unproved.

Real Dependencies and Test Doubles

Development APIs and the configured authentication environment are real dependencies. Browser journeys can intercept a specifically named fault; persona availability and cleanup are part of the suite source.

Must Not Be Doubled

Regional matching, regional persistence and the stored values under assertion must remain real. A substitute answer for these dependencies cannot qualify the linked regional outcomes.