Close-state, run and snapshot database constraints

Verification Boundary

The suite checks its declared service or persistence boundary against local PostgreSQL. Bindings identify the assertions it contributes to a capability case; they do not establish every assertion in a combined case.

What This Suite Proves

Database assertions cover close stamps, valid states, active-run uniqueness, command bounds, references and immutable snapshot storage. Workspace policies isolate both reads and writes.

What It Does Not Prove

This register records assertion scope without claiming a passing run or complete coverage of every rule and scenario variant.

Real Dependencies and Test Doubles

Production migrations, application-role SQL, execution-context transactions and workspace session settings exercise database refusal directly. These enforcement boundaries are not doubled.

Must Not Be Doubled

Keep production queries, writes, mappings, application-role privileges and database constraints real wherever they are the subject of an assertion. Recording financial ports establish invocation behavior; actual recognition and reversal require the suite using the real posting service.