Database checks for Allowance Overrides

Verification Boundary

The suite checks module persistence or service behavior against prepared PostgreSQL with scoped records.

What This Suite Proves

Grant lists derive current window state. Grant inspection follows revocation. Invalid grant shape is rejected. Default and invalid windows have distinct results. Reasons and tickets have bounded text. Peak overlap governs the ceiling. Grant creation retains its widening audit. Revocation preserves original authorization. Capacity notices depend on restoration and explicit request. Preview agrees with grant validation and projection. Combined bindings require every named suite; a component assertion alone does not establish the full experiment.

What It Does Not Prove

The suite does not establish browser behavior, deployed routing, live model quality or actual recipient inbox delivery.

Real Dependencies and Test Doubles

PostgreSQL, production grant checks, revocation, ledger reads, security audit and Administrator role assignments are real. Recording email captures restoration messages instead of sending them.

Must Not Be Doubled

Retain PostgreSQL constraints, transaction behavior and the production persistence or dispatcher path under test. A scripted provider must not replace accounting or authorization.