Database checks for Organization Usage

Verification Boundary

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

What This Suite Proves

Summary states usage and local renewal. Features explain current restriction. Unknown historical operations have an Other group. Customer periods stay organization-scoped. 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 composite reads, workspace lookup and scoped execution contexts are real. A fixed clock selects windows; the queries and row policy are not doubled.

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.