Entities rule-function unit

Verification Boundary

Pure rule and mapper tests examine affiliation planning, date windows, seasonal selection, domain derivation, endpoint deletion decisions and API field conversion without PostgreSQL persistence. This register groups 9 files with a common verification boundary; it does not register each file as an independent suite. Files and assertion sources remain explicit so an operator can select the group without losing the narrower proof boundaries.

What This Suite Proves

Pure rule and mapper tests examine affiliation planning, date windows, seasonal selection, domain derivation, endpoint deletion decisions and API field conversion without PostgreSQL persistence. The structured bindings retain the previously recorded contributions. An unbound file supplies no newly asserted specification coverage. No execution result is claimed by this registration.

What It Does Not Prove

A calculated plan does not prove the database accepts it, that a transaction rolls back correctly, or that a caller is authorized. A bound contribution is evidence for its assertions rather than certification of an entire composite scenario. Skipped or environment-dependent declarations remain visible in the source observations.

Real Dependencies and Test Doubles

The rule functions and supplied input structures are real. No database or deployed request is part of this group. The evidence list and per-file source observations identify the existing tests and their declared dependencies.

Must Not Be Doubled

Keep the actual decision and conversion functions under test; a replacement function would only test its supplied answer.