Assignment sources coverage and currency

Verification Boundary

The suite exercises real regional persistence and processing against the prepared database. It verifies the source assertions linked in this register.

What This Suite Proves

The linked source assertions contribute checks for assignment can start with empty coverage; record-kind selection limits placement; fallback is deferred and the final enabled fallback wins; disabled coverage contributes no result; postal-country restrictions distinguish otherwise equal codes; configured sources determine reassignment; workspace policies do not leak; a successful current-generation run clears need; policy-affecting writes raise need; changes during processing remain outstanding; equal timestamps do not hide changes; newer policy changes remain outstanding after an older run; coincident timestamps cannot hide a policy change. 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

PostgreSQL, event capture, dispatch, consumer routing and regional processing are real. The delivery harness replaces the external queue with an in-memory message list.

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.