---
id: FAS-PFM-OPS-01
feature: FEAT-PFM-OPS-01
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-001
  - CAP-PFM-OPS-002
  - CAP-PFM-OPS-003
  - CAP-PFM-OPS-004
  - CAP-PFM-OPS-005
  - CAP-PFM-OPS-006
  - CAP-PFM-OPS-007
scenarios:
  - id: FAS-PFM-OPS-01-01
    title: Follow a run from submission to inspection
    kind: behaviour
    exercises:
      - CAP-PFM-OPS-001
      - CAP-PFM-OPS-005
      - CAP-PFM-OPS-007
    relies_on:
      - ATS-PFM-OPS-001-02
      - ATS-PFM-OPS-005-09
      - ATS-PFM-OPS-007-01
    preconditions: A workspace submits work whose job family publishes the shared views.
    steps:
      - do: 'Create the run, report a completed step, then list and inspect it through Scheduled Jobs.'
        provenance: proposed
        source: ATS-PFM-OPS-001-02; ATS-PFM-OPS-005-09; ATS-PFM-OPS-007-01
    expected: The submitted work is traceable through its durable record and published monitor.
    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-001-02; ATS-PFM-OPS-005-09; ATS-PFM-OPS-007-01
  - id: FAS-PFM-OPS-01-02
    title: Explain a reconciled provisioning failure
    kind: interaction
    exercises:
      - CAP-PFM-OPS-001
      - CAP-PFM-OPS-002
      - CAP-PFM-OPS-003
    relies_on:
      - ATS-PFM-OPS-002-03
      - ATS-PFM-OPS-003-05
      - ATS-PFM-OPS-003-07
    preconditions: A notifying provisioning run has committed but never started.
    steps:
      - do: Reconcile the stale run and apply the failure consequence again.
        provenance: proposed
        source: ATS-PFM-OPS-002-03; ATS-PFM-OPS-003-05; ATS-PFM-OPS-003-07
    expected: >-
      The workspace becomes recoverably failed, the run records failure, and the completed requester
      notice is not resent.
    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-002-03; ATS-PFM-OPS-003-05; ATS-PFM-OPS-003-07
  - id: FAS-PFM-OPS-01-03
    title: Recover completed work through a separate attempt
    kind: lifecycle
    exercises:
      - CAP-PFM-OPS-001
      - CAP-PFM-OPS-004
      - CAP-PFM-OPS-006
    relies_on:
      - ATS-PFM-OPS-004-02
      - ATS-PFM-OPS-004-06
      - ATS-PFM-OPS-004-07
    preconditions: Provisioning fails after a completed step and staff can inspect and retry it.
    steps:
      - do: 'Inspect the failure, confirm retry, and compare the predecessor with the new attempt.'
        provenance: proposed
        source: ATS-PFM-OPS-004-02; ATS-PFM-OPS-004-06; ATS-PFM-OPS-004-07
    expected: The new run retains lineage and bypasses completed work while the predecessor stays final.
    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-004-02; ATS-PFM-OPS-004-06; ATS-PFM-OPS-004-07
  - id: FAS-PFM-OPS-01-04
    title: Compare customer reach with staff inspection
    kind: permission
    exercises:
      - CAP-PFM-OPS-005
      - CAP-PFM-OPS-006
      - CAP-PFM-OPS-007
    relies_on:
      - ATS-PFM-OPS-005-02
      - ATS-PFM-OPS-005-04
      - ATS-PFM-OPS-006-01
      - ATS-PFM-OPS-007-03
    preconditions: Two customers publish jobs; a staff reader has a grant into one workspace.
    steps:
      - do: >-
          Read the granted workspace, request a foreign customer run, and separately inspect through HQ
          authority.
        provenance: proposed
        source: ATS-PFM-OPS-005-02; ATS-PFM-OPS-005-04; ATS-PFM-OPS-006-01; ATS-PFM-OPS-007-03
    expected: Each surface preserves its own audience and scope while reading the same published records.
    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-005-02; ATS-PFM-OPS-005-04; ATS-PFM-OPS-006-01; ATS-PFM-OPS-007-03
  - id: FAS-PFM-OPS-01-05
    title: Keep interrupted work explainable after repeated settlement
    kind: regression
    exercises:
      - CAP-PFM-OPS-001
      - CAP-PFM-OPS-002
      - CAP-PFM-OPS-003
      - CAP-PFM-OPS-004
    relies_on:
      - ATS-PFM-OPS-001-04
      - ATS-PFM-OPS-002-02
      - ATS-PFM-OPS-003-02
      - ATS-PFM-OPS-004-07
    preconditions: A stale run has unfinished steps and its execution reports success.
    steps:
      - do: 'Reconcile it, deliver a late report, repeat notice claiming, and create a permitted retry.'
        provenance: proposed
        source: ATS-PFM-OPS-001-04; ATS-PFM-OPS-002-02; ATS-PFM-OPS-003-02; ATS-PFM-OPS-004-07
    expected: >-
      The unsupported success becomes failure, the final history stays stable, and recovery uses a
      separate run.
    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-001-04; ATS-PFM-OPS-002-02; ATS-PFM-OPS-003-02; ATS-PFM-OPS-004-07
evidence:
  - CAP-PFM-OPS-001; its capability test specification and the workflows it crosses
  - CAP-PFM-OPS-002; its capability test specification and the workflows it crosses
  - CAP-PFM-OPS-003; its capability test specification and the workflows it crosses
  - CAP-PFM-OPS-004; its capability test specification and the workflows it crosses
  - CAP-PFM-OPS-005; its capability test specification and the workflows it crosses
  - CAP-PFM-OPS-006; its capability test specification and the workflows it crosses
  - CAP-PFM-OPS-007; its capability test specification and the workflows it crosses
---

# Background Work: Feature Acceptance Suite

## What the Feature Must Do as a Whole

Background work must remain explainable from committed submission through outcome and recovery. The feature cases connect durable records, reconciliation, requester notices and audience-specific inspection.

## Interactions Between Capabilities

Explain a reconciled provisioning failure. The workspace becomes recoverably failed, the run records failure, and the completed requester notice is not resent.

Recover completed work through a separate attempt. The new run retains lineage and bypasses completed work while the predecessor stays final.

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. |