Database checks for Evidence Access

Verification Boundary

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

What This Suite Proves

Content access requires a live eligible grant. Handled content reads have content-free audit events. Unavailable bodies return their status. Not-found content follows eligible access. 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 content access, real staff-grant persistence and AI audit writes are real. Evidence storage is in memory; mail and job-start ports record calls rather than contacting external services.

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.