--- id: FAS-ACC-CLS-04 title: Execution History and Retained Evidence acceptance feature: FEAT-ACC-CLS-04 product_area: accounting module: close revision: 1 status: proposed product_intent: proposed source_sha: services-accounting: f47cb263875bbc0c5640fba7dae6785ec32695f8 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-ACC-CLS-013 - CAP-ACC-CLS-014 - CAP-ACC-CLS-015 - CAP-ACC-CLS-016 scenarios: - id: FAS-ACC-CLS-04-01 title: Read successful execution and its retained record together kind: behaviour exercises: - CAP-ACC-CLS-013 - CAP-ACC-CLS-014 relies_on: - ATS-ACC-CLS-013-01 - ATS-ACC-CLS-014-02 preconditions: A clean close completes with an optional note. steps: 'Read its steps and record, then find it in history.' expected: >- The run and record agree on the subject and requester; the captured evaluation, note and completed result remain available. negative: false data_needs: A clean close completes with an optional note. bound_to: - TST-ACC-CLS-001 provenance: test source: >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0613.spec.ts#ACT-ACC-0613 - id: FAS-ACC-CLS-04-02 title: Keep the requested aging version beside the captured close kind: interaction exercises: - CAP-ACC-CLS-013 - CAP-ACC-CLS-014 - CAP-ACC-CLS-015 relies_on: - ATS-ACC-CLS-013-01 - ATS-ACC-CLS-014-01 - ATS-ACC-CLS-015-01 preconditions: Two units overlap a month and one remains open when the first closes. steps: >- Read the first unit’s completed execution, captured record and retained aging output. expected: >- The run and captured outputs identify the reconstructed request without claiming that report computation has completed. negative: false data_needs: Two units overlap a month and one remains open when the first closes. bound_to: [] provenance: proposed source: - ATS-ACC-CLS-013-01 - ATS-ACC-CLS-014-01 - ATS-ACC-CLS-015-01 finding: FND-ACC-CLS-075 - id: FAS-ACC-CLS-04-03 title: Preserve the original record through correction and erasure kind: lifecycle exercises: - CAP-ACC-CLS-013 - CAP-ACC-CLS-014 - CAP-ACC-CLS-016 relies_on: - ATS-ACC-CLS-014-02 - ATS-ACC-CLS-016-01 - ATS-ACC-CLS-016-02 preconditions: Two workspaces have successful closes and linked correction history. steps: >- Read and export one workspace’s original record after reopening, erase that workspace’s close history and attempt both workspace reads. expected: >- The export carries the retained snapshot and correction history before erasure; ordered removal affects only the selected workspace. negative: false data_needs: Two workspaces have successful closes and linked correction history. bound_to: [] provenance: proposed source: - ATS-ACC-CLS-014-02 - ATS-ACC-CLS-016-01 - ATS-ACC-CLS-016-02 finding: FND-ACC-CLS-075 - id: FAS-ACC-CLS-04-04 title: Allow retained-record review while refusing state changes kind: permission exercises: - CAP-ACC-CLS-013 - CAP-ACC-CLS-014 relies_on: - ATS-ACC-CLS-013-04 - ATS-ACC-CLS-014-05 preconditions: >- A close has succeeded and a reader holds only fiscal-period read authority. steps: >- Inspect the successful run, record and history as the reader; inspect reopen and recovery controls. expected: >- The reader can review the record and catalogue without a reopen action or successful-run recovery controls. negative: true data_needs: >- A close has succeeded and a reader holds only fiscal-period read authority. bound_to: - TST-ACC-CLS-007 provenance: test source: >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0619.spec.ts#ACT-ACC-0619 - id: FAS-ACC-CLS-04-05 title: Bound long execution and correction histories explicitly kind: regression exercises: - CAP-ACC-CLS-013 - CAP-ACC-CLS-014 - CAP-ACC-CLS-016 relies_on: - ATS-ACC-CLS-013-06 - ATS-ACC-CLS-014-07 - ATS-ACC-CLS-016-01 preconditions: >- A close has more than one hundred job attempts and linked correction requests. steps: >- Compare the execution view and record with a complete customer export made before erasure. expected: >- The service views retain their stated bounds while the export’s inclusion rules are checked independently; view truncation is not treated as complete exported history. negative: false data_needs: >- A close has more than one hundred job attempts and linked correction requests. bound_to: [] provenance: proposed source: - ATS-ACC-CLS-013-06 - ATS-ACC-CLS-014-07 - ATS-ACC-CLS-016-01 finding: FND-ACC-CLS-075 evidence: - >- Testing hierarchy: Andrew ruling of 2026-10-23, rhythm-v2-docs:specs/CONVENTIONS.md#5.3 Feature Acceptance Suite. - >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0613.spec.ts#ACT-ACC-0613 - ATS-ACC-CLS-013-01 - ATS-ACC-CLS-014-01 - ATS-ACC-CLS-015-01 - ATS-ACC-CLS-014-02 - ATS-ACC-CLS-016-01 - ATS-ACC-CLS-016-02 - >- react-console:acceptance/accounting/playwright/journeys/reconciliation-close/ACT-ACC-0619.spec.ts#ACT-ACC-0619 - ATS-ACC-CLS-013-06 - ATS-ACC-CLS-014-07 --- # Execution History and Retained Evidence: Feature Acceptance Suite ## What the Feature Must Do as a Whole This suite connects execution review to the record finance staff retain after closing. It considers how the original evidence is read during later correction and how that history participates in customer data operations. Bound browser cases cover successful review and reader access, with no claimed passing execution. ## Interactions Between Capabilities Run details, history and the close record need to describe the same request. Aging references connect closing to Reporting, while export and erasure connect retained history to customer data operations. Those broader chains remain proposed: a recorded request does not establish report completion, and a local purge callback does not establish a complete export or external erasure workflow. ## Regression Record | Revision | Change | Scenarios | Why | |---|---|---|---| | 1 | initial | all | Specify the feature’s combined outcomes and distinguish executable assertions from proposed chains. |