--- id: FAS-ACC-BKS-06 title: Workspace Policy and Operations acceptance feature: FEAT-ACC-BKS-06 product_area: accounting module: books revision: 1 status: proposed product_intent: proposed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-ACC-BKS-016 - CAP-ACC-BKS-017 - CAP-ACC-BKS-018 - CAP-ACC-BKS-019 scenarios: - id: FAS-ACC-BKS-06-01 title: Provision configuration and enforce ordinary availability kind: behaviour exercises: - CAP-ACC-BKS-016 - CAP-ACC-BKS-019 relies_on: - ATS-ACC-BKS-019-01 - ATS-ACC-BKS-019-06 - ATS-ACC-BKS-016-02 preconditions: >- Platform supplies provisioning and availability observations for an isolated workspace. steps: >- Provision configuration, observe activation and use ordinary configuration routes, then observe disabled and loading states. expected: >- Initial methods appear once and ordinary access follows the recorded availability policy in every observed state. negative: false data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: [] provenance: proposed source: - ATS-ACC-BKS-019-01 - ATS-ACC-BKS-019-06 - ATS-ACC-BKS-016-02 binding_evidence: [] - id: FAS-ACC-BKS-06-02 title: Settings replacement changes statement usage safely kind: interaction exercises: - CAP-ACC-BKS-016 - CAP-ACC-BKS-017 - CAP-ACC-BKS-015 relies_on: - ATS-ACC-BKS-017-03 - ATS-ACC-BKS-017-05 - ATS-ACC-BKS-015-05 preconditions: >- The workspace has selected statement content and saved service-period and truncation policy. steps: >- Save settings while omitting these fields, inspect the resulting statement selection and retained policy, then try the earlier version. expected: >- Omission affects statement usage and retained policy as specified; the stale replacement changes neither. negative: false data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: - TST-ACC-BKS-021 provenance: test source: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0027.spec.ts#ACT-ACC-0027 binding_evidence: - >- react-console:acceptance/accounting/playwright/journeys/configuration/ACT-ACC-0027.spec.ts#ACT-ACC-0027 - id: FAS-ACC-BKS-06-03 title: Erase declared data without crossing workspace boundaries kind: lifecycle exercises: - CAP-ACC-BKS-016 - CAP-ACC-BKS-019 relies_on: - ATS-ACC-BKS-019-02 - ATS-ACC-BKS-019-04 preconditions: >- Two populated workspaces have independent identical configuration identities; one has deleting standing. steps: >- Purge the deleting workspace in single-record batches, interrupt and resume, then inspect both inventories and their ordinary access. expected: >- Bounded continuation empties only the selected workspace and leaves the other configuration intact. negative: false data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: [] provenance: proposed source: - ATS-ACC-BKS-019-02 - ATS-ACC-BKS-019-04 binding_evidence: [] - id: FAS-ACC-BKS-06-04 title: Read scheduled history through subject grants kind: permission exercises: - CAP-ACC-BKS-016 - CAP-ACC-BKS-018 relies_on: - ATS-ACC-BKS-018-04 preconditions: >- A recurring subject has run history and two principals have application access; only one can read that subject. steps: >- Read the history as each principal and compare the schedule and history after the refused request. expected: >- The subject reader receives history, the other receives a resource refusal and neither read mutates timing or runs. negative: true data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: - TST-ACC-BKS-177 provenance: test source: - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers 403 to a caller holding only accounting.application.access binding_evidence: - >- services-accounting:modules/maintenance/tests/e2e/schedules.e2e.spec.js#answers 403 to a caller holding only accounting.application.access - id: FAS-ACC-BKS-06-05 title: Pause repeated failure without duplicating due occurrences kind: regression exercises: - CAP-ACC-BKS-018 - CAP-ACC-BKS-010 relies_on: - ATS-ACC-BKS-018-05 preconditions: >- An isolated recurring subject has a due occurrence and a period-lookup port that consistently fails. steps: >- Race two dispatcher passes, consume the one occurrence and continue through five recorded failed occurrences. expected: >- Each occurrence has one claim and the repeated failures leave a paused schedule and inspectable failure history. negative: true data_needs: >- Run-owned records and principals for the stated setup; record original shared settings and restore them after exclusive cases. bound_to: - TST-ACC-BKS-187 provenance: test source: - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses the schedule after the fifth failure in a row binding_evidence: - >- services-accounting:modules/maintenance/tests/integration/services/scheduling/schedules-end-to-end.integration.spec.js#pauses the schedule after the fifth failure in a row evidence: - provenance: documented source: >- specs/accounting/books/planning/features/FEAT-ACC-BKS-06-access-settings-and-workspace-housekeeping.md - provenance: test source: >- Pinned executable suites and their individual assertion references are listed in the suite register. regression_record: - revision: 1 change: initial scenarios: - FAS-ACC-BKS-06-01 - FAS-ACC-BKS-06-02 - FAS-ACC-BKS-06-03 - FAS-ACC-BKS-06-04 - FAS-ACC-BKS-06-05 why: >- Establish cumulative feature acceptance from the pinned specification and executable evidence. --- # Workspace Policy and Operations: Feature Acceptance Suite ## What the Feature Must Do as a Whole The feature connects resource access, shared policy, recurring timing and Accounting’s workspace lifecycle contribution. Acceptance checks joined outcomes while preserving the distinction between configuration authority and the owners of financial work. ## Interactions Between Capabilities Availability affects whether configuration routes can run, settings choices affect content usage, and subject permissions govern scheduled history. Erasure and export must respect the same workspace boundary across their bounded work. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish the feature’s cumulative acceptance boundary and record unimplemented joined outcomes. |