Financial setup API lifecycle

Verification Boundary

Requests pass through the local enforcing Accounting dispatcher, request mapping and persistence to PostgreSQL. This is local API evidence rather than a deployed network run.

What This Suite Proves

The enforcing API tests setup creation, versioned replacement, references, financial validation, dependency protection and setup removal.

What It Does Not Prove

Local execution does not prove deployed infrastructure, downstream purchase behavior, real domain extension completion or atomic remote-template recovery.

Real Dependencies and Test Doubles

The composed handler, permission evaluation and Accounting database are real. Local signing keys and Platform workspace registration stand in for external infrastructure.

Must Not Be Doubled

Do not double PostgreSQL, row-level security, transaction boundaries, constraints or the persistence implementation when claiming these local guarantees.

Show evidence (sources, provenance, origins, pinned commits)

Isolation: Suite-named local workspaces, isolated fixture records and explicit cleanup or rollback.
Kind: api-lifecycle
Repository: services-accounting
Environment: local
Implementation state: implemented
Latest result: not-run
Conformance: not-verified

Test Files

services-accounting:modules/products/tests/e2e/product-accounting.e2e.spec.js

Implements

ATS-ACC-PRD-015-01 ATS-ACC-PRD-015-02 ATS-ACC-PRD-015-03 ATS-ACC-PRD-015-05 ATS-ACC-PRD-015-06 ATS-ACC-PRD-015-07 ATS-ACC-PRD-015-10 ATS-ACC-PRD-015-11 ATS-ACC-PRD-016-01 ATS-ACC-PRD-016-02 ATS-ACC-PRD-016-03 ATS-ACC-PRD-016-05 ATS-ACC-PRD-016-06 ATS-ACC-PRD-016-07

Implementation

Financial setup API lifecycle ​

Verification Boundary ​

What This Suite Proves ​

What It Does Not Prove ​

Real Dependencies and Test Doubles ​

Must Not Be Doubled ​