Organization compliance and notice preparation integration
Verification Boundary
Organization compliance calculation, violation persistence, reprocess progress, attention reads and notice preparation cross local service and database seams.
What This Suite Proves
Tests establish stored violations, computed compliance status, changes to attention items and reprocess progress or failure. Communication submission tests establish caller-transaction visibility. Template tests exercise publication, partial updates, clearing and compensation when Platform refuses or cannot save. Notification preparation remains distinct from actual delivery to a recipient.
What It Does Not Prove
This group does not prove final mail delivery, deployed Platform template validation or the authorization of a public reprocess request. Organization CRUD is separate. A reprocess counter or an accepted request is not by itself evidence that every organization reaches its terminal recomputed state.
Level and Rationale
Violation rows, attention publication and reprocess progress must agree with organization state across transactions. A lower-level calculation cannot establish rollback, terminal failure accounting or compensation across the owned-template seam. The database tier verifies the retained facts that staff later review.
Real Dependencies and Test Doubles
PostgreSQL, compliance services, CRM notice composition and progress queries are real. Platform communication operations use the local adapter described by the tests. Object storage for communication payloads is prepared by the repository test bootstrap. These substitutes intentionally exclude deployed publication and delivery availability.
Must Not Be Doubled
Keep violation persistence, progress updates and caller transactions real. Do not substitute the comparison of current role counts with stored violations. When testing template compensation, keep the CRM compensating behavior and the refused remote outcome; replacing both with an accepted result would remove the failure boundary.
Fixtures and Isolation
Tests create their own organizations, compliance types, role fixtures and reprocess records. Template tests restore injected Platform behavior. Reprocess fixtures own unfinished-run premises so a cleanup cannot cancel another run; the selected serial invocation avoids overlapping process-level adapters.
Determinism and Retries
Explicit role-count and date fixtures drive the expected compliance result. Retry and failure cases retain the source-declared sequence and counters. This register adds no runner retries; retrying a failed reprocess test could conceal an unfinished run or duplicate submission.
How It Runs
Run the command in the frontmatter from the service repository after preparing the test database. It selects every file in this aggregate register under the repository Mocha bootstrap and runs serially. This is the aggregate selection of the integration gate; the complete repository integration command includes other modules and is wider than this register.
Coverage Gaps
Integration coverage does not fill the API lifecycle gap for terminal reprocess settlement or prove delivered notices. Existing recipient batching, policy-state and recovery findings remain open. No control is claimed solely because a permitted notice or successful template publication is tested.