Database checks for Rollup Settled Invocations

Verification Boundary

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

What This Suite Proves

Daily rebuilding keeps classifications and organization boundaries. Progress resumes from unfinished changes. 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 rollup and persistence queries, scoped raw records and shared daily cells are real. A controlled clock supplies change and budget boundaries.

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.