---
id: TST-ACC-CLS-033
title: Read-only readiness and evaluator savepoints
kind: integration
product_area: accounting
module: close
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - >-
    modules/fiscal-close/tests/integration/services/persistence/readiness-transactions.integration.spec.js
implements:
  - ATS-ACC-CLS-004-02
  - ATS-ACC-CLS-004-04
  - ATS-ACC-CLS-004-10
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 3
isolation: >-
  The suite owns test-identifier workspaces and fixture records, removed by its
  teardown.
binding_policy: >-
  Each binding identifies the assertions this suite executes; combined scenarios
  may require other bound suites. Existence is not a recorded execution result.
evidence:
  - >-
    services-accounting:modules/fiscal-close/tests/integration/services/persistence/readiness-transactions.integration.spec.js
  - provenance: test
    source: >-
      services-accounting:modules/fiscal-close/tests/integration/services/persistence/readiness-transactions.integration.spec.js
    assertion_titles:
      - 'fiscal close persistence: the readiness transaction (integration)'
      - opens a read-only transaction when the caller has none
      - refuses a write in it
      - 'runs in the caller’s transaction, which stays writable'
      - >-
        rolls an evaluator’s failure back to its savepoint and keeps the
        transaction usable
real_dependencies: >-
  Production persistence and mapping run with application-role transactions and
  workspace policies on PostgreSQL. Fixture records and fixed context values
  supply the inputs; the service and database enforcement under assertion remain
  real.
product_intent: proposed
implementation_evidence: observed
---
# Read-only readiness and evaluator savepoints

## 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

The transaction suite checks standalone read-only behavior, refusal of a write, joining a writable caller transaction and rolling a failed evaluator back before another database query succeeds.

## 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 persistence and mapping run with application-role transactions and workspace policies on PostgreSQL. Fixture records and fixed context values supply the inputs; the service and database enforcement under assertion remain real.

## 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.