Database checks for AI Ledger Concurrency

Verification Boundary

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

What This Suite Proves

Concurrent requests share capacity atomically. Concurrency slots return on settlement. Grant windows and revocation apply at request time. Lower limits preserve running reservations. Lowering limits preserves admitted work. Grant boundaries change the next admission. 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, the production ledger, grant services, execution context and transactions are real. A controlled clock supplies boundaries; actual competing statements establish the race.

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.