Database checks for Explain Invocation

Verification Boundary

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

What This Suite Proves

Explanation never reserves the retried estimate. Original refusal arithmetic does not change. Missing grant references remain explicit. Current admission check observes later capacity. Failure histories disclose retries and truncation. Healthy or foreign requests do not explain. 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 explanation assembly, persistence and the ledger’s read-only affordability predicate are real. A controlled clock supplies the present instant.

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.