Assignment-policy persistence and competing writes

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 unsaved configuration returns defaults; assignment can start with empty coverage; typed sources require a type; existence governs service address-type choices; versionless settings writes bypass conflict checks; collected validation errors preserve the policy; criteria lists require valid bounded content; foreign and absent rule targets are rejected; omitted rules preserve the list; rule identity and position remain valid; individual writes invalidate older policy drafts; individual edits cannot be discarded by an older full draft. 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 and the regional persistence under assertion are real. The suite supplies test execution contexts and fixtures; a local API harness replaces deployed transport where applicable.

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.