---
id: TST-ACC-REC-077
title: Workspace-local daily schedule setup
kind: integration
product_area: accounting
module: reconciliation
revision: 1
status: draft
source_sha:
  services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8
repository: services-accounting
files:
  - modules/reconciliation/tests/integration/services/scheduled/reconciliation-schedules.integration.spec.js
implements:
  - ATS-ACC-REC-017-01
environment: local
implementation_state: implemented
latest_result: not-run
latest_run_at: null
latest_run_ref: null
conformance: not-verified
estimated_minutes: 5
isolation: Suite-owned workspace fixtures and deterministic records removed by suite cleanup.
evidence:
  - >-
    services-accounting:modules/reconciliation/tests/integration/services/scheduled/reconciliation-schedules.integration.spec.js
bindings:
  - scenario: ATS-ACC-REC-017-01
    assertions:
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/scheduled/reconciliation-schedules.integration.spec.js#creates
        the three daily schedules on the first pass
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/scheduled/reconciliation-schedules.integration.spec.js#keeps
        the tenant’s zone on each schedule
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/scheduled/reconciliation-schedules.integration.spec.js#creates
        nothing on a second pass
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/scheduled/reconciliation-schedules.integration.spec.js#leaves
        a schedule a person disabled disabled
      - >-
        services-accounting:modules/reconciliation/tests/integration/services/scheduled/reconciliation-schedules.integration.spec.js#gives
        another tenant its own three
---

# Workspace-local daily schedule setup

## Verification Boundary

This suite calls production services over the real test database. Fixture setup may write records directly; the exercised commands and queries retain their normal database enforcement.

## What This Suite Proves

The executable assertions identified in the binding records supply the registered scenario observations. When a scenario names several suites, this suite supplies its listed assertions and does not independently establish every clause.

## What It Does Not Prove

Deployed infrastructure, live console behavior and shared scheduling delivery are outside this local boundary.

## Real Dependencies and Test Doubles

PostgreSQL, migrations and the exercised production code are real. Fixtures supply the financial world and caller context; deterministic setup and owner-side inspection do not replace database enforcement.

## Must Not Be Doubled

The exercised database constraints, transactional services and route enforcement remain real. Replacing them would remove the boundary this suite registers.