Geographic matching and deciding input

Verification Boundary

The suite exercises regional calculations, declarations or console components with test inputs. Its assertions do not establish deployed service behavior.

What This Suite Proves

The linked source assertions contribute checks for ordering resolves overlapping criteria; fallback is deferred and the final enabled fallback wins; text intervals include their endpoints; state matching preserves case sensitivity; country matching supplies the legacy default; uncovered addresses can remain unplaced; an absent address cannot use fallback; unsupported criteria fail instead of choosing a target. 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

Test inputs, execution contexts, request clients or component dependencies are supplied by the suite. Database persistence and deployed transport are outside this boundary.

Must Not Be Doubled

The calculation, permission declaration or console behavior under assertion must remain the real implementation.