--- id: FAS-PFM-OPS-04 feature: FEAT-PFM-OPS-04 product_area: platform module: operations revision: 1 status: proposed product_intent: proposed source_sha: services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1 macroservice-libraries: 54536a441935c6e09fdb7f96f0bec71c52ba4e03 react-console: baf6dae382d6f41dce976c7f848667ccc37e076f capabilities: - CAP-PFM-OPS-014 - CAP-PFM-OPS-015 - CAP-PFM-OPS-016 scenarios: - id: FAS-PFM-OPS-04-01 title: Explain a ready licensed application kind: behaviour exercises: - CAP-PFM-OPS-014 - CAP-PFM-OPS-015 - CAP-PFM-OPS-016 relies_on: - ATS-PFM-OPS-014-01 - ATS-PFM-OPS-015-01 - ATS-PFM-OPS-016-01 preconditions: An isolated workspace has commercial eligibility for an application with no operational state. steps: - do: 'Prepare the application, resolve availability, and read customer application standing.' provenance: proposed source: ATS-PFM-OPS-014-01; ATS-PFM-OPS-015-01; ATS-PFM-OPS-016-01 expected: The customer can connect successful preparation with the available application. negative: false data_needs: 'An isolated workspace, owned test records and caller contexts named in the preconditions.' bound_to: [] provenance: proposed source: ATS-PFM-OPS-014-01; ATS-PFM-OPS-015-01; ATS-PFM-OPS-016-01 - id: FAS-PFM-OPS-04-02 title: Reflect suspension in customer standing kind: interaction exercises: - CAP-PFM-OPS-014 - CAP-PFM-OPS-015 - CAP-PFM-OPS-016 relies_on: - ATS-PFM-OPS-014-06 - ATS-PFM-OPS-015-02 - ATS-PFM-OPS-016-02 preconditions: A licensed application is enabled and staff can change its operational state. steps: - do: 'Suspend it, resolve availability, and inspect the customer response before resuming.' provenance: proposed source: ATS-PFM-OPS-014-06; ATS-PFM-OPS-015-02; ATS-PFM-OPS-016-02 expected: The application becomes unavailable with a customer-safe explanation and returns after resumption. negative: false data_needs: 'An isolated workspace, owned test records and caller contexts named in the preconditions.' bound_to: [] provenance: proposed source: ATS-PFM-OPS-014-06; ATS-PFM-OPS-015-02; ATS-PFM-OPS-016-02 - id: FAS-PFM-OPS-04-03 title: Recover failed preparation without resetting first enablement kind: lifecycle exercises: - CAP-PFM-OPS-014 - CAP-PFM-OPS-015 - CAP-PFM-OPS-016 relies_on: - ATS-PFM-OPS-015-01 - ATS-PFM-OPS-015-04 - ATS-PFM-OPS-014-01 preconditions: 'Preparation first fails, later succeeds, and the application is subsequently suspended.' steps: - do: >- Retry preparation, inspect standing, suspend and resume, then compare the original activation time. provenance: proposed source: ATS-PFM-OPS-015-01; ATS-PFM-OPS-015-04; ATS-PFM-OPS-014-01 expected: >- Readiness recovery and later suspension remain traceable without replacing original activation history. negative: false data_needs: 'An isolated workspace, owned test records and caller contexts named in the preconditions.' bound_to: [] provenance: proposed source: ATS-PFM-OPS-015-01; ATS-PFM-OPS-015-04; ATS-PFM-OPS-014-01 - id: FAS-PFM-OPS-04-04 title: Refuse foreign standing and unauthorized state changes kind: permission exercises: - CAP-PFM-OPS-014 - CAP-PFM-OPS-015 - CAP-PFM-OPS-016 relies_on: - ATS-PFM-OPS-015-07 - ATS-PFM-OPS-016-03 preconditions: A staff reader and a foreign customer administrator know the workspace identity. steps: - do: >- Attempt a state change with read-only staff and request applications as the foreign administrator. provenance: proposed source: ATS-PFM-OPS-015-07; ATS-PFM-OPS-016-03 expected: Neither request changes operational state or exposes the workspace’s application information. negative: true data_needs: 'An isolated workspace, owned test records and caller contexts named in the preconditions.' bound_to: [] provenance: proposed source: ATS-PFM-OPS-015-07; ATS-PFM-OPS-016-03 - id: FAS-PFM-OPS-04-05 title: Keep backfill from reversing suspension kind: regression exercises: - CAP-PFM-OPS-014 - CAP-PFM-OPS-015 - CAP-PFM-OPS-016 relies_on: - ATS-PFM-OPS-015-06 - ATS-PFM-OPS-014-05 - ATS-PFM-OPS-016-01 preconditions: An always-available application has a deliberate suspended row beside missing core rows. steps: - do: 'Run activation and backfill twice, then resolve and inspect customer standing.' provenance: proposed source: ATS-PFM-OPS-015-06; ATS-PFM-OPS-014-05; ATS-PFM-OPS-016-01 expected: >- Missing rows are supplied while the deliberate operational decision stays visible under the resolver’s standing. negative: false data_needs: 'An isolated workspace, owned test records and caller contexts named in the preconditions.' bound_to: [] provenance: proposed source: ATS-PFM-OPS-015-06; ATS-PFM-OPS-014-05; ATS-PFM-OPS-016-01 evidence: - CAP-PFM-OPS-014; its capability test specification and the workflows it crosses - CAP-PFM-OPS-015; its capability test specification and the workflows it crosses - CAP-PFM-OPS-016; its capability test specification and the workflows it crosses --- # Application Standing: Feature Acceptance Suite ## What the Feature Must Do as a Whole Application standing must connect commercial eligibility, operational readiness and the customer explanation. The feature cases follow preparation, suspension and recovery through the availability answer. ## Interactions Between Capabilities Reflect suspension in customer standing. The application becomes unavailable with a customer-safe explanation and returns after resumption. Recover failed preparation without resetting first enablement. Readiness recovery and later suspension remain traceable without replacing original activation history. Proposed chains require an executable suite that performs the complete sequence. Separate lower-level bindings do not establish whole-feature execution. ## Regression Record | Revision | Change | Scenario | Why | |---|---|---|---| | 1 | initial | all | Establish cumulative whole-feature proof from the landed planning and design contracts. |