Close execution, refusal and recovery

Verification Boundary

This suite exercises the named persistence or service behavior on the local integration database. Its bindings can cover parts of a combined capability scenario.

What This Suite Proves

The job suite follows clean and year-end closes, readiness refusal, command replay, finalization failure and cancellation before or after recorded recognition. Fault cases replace the aging port and selected cases use a recording recognition stand-in.

What It Does Not Prove

Financial port stand-ins in selected cases prove orchestration and output retention, not actual ledger entries.

Real Dependencies and Test Doubles

The suite uses local PostgreSQL with the application persistence and its declared constraints. Fixture contexts supply callers and time. Durable job suites run the task handlers in process and selected fault cases replace financial ports.

Must Not Be Doubled

The persistence and database constraints under assertion must remain real. A financial port stand-in cannot qualify actual recognition or reversal; those outcomes require the real posting suite.