---
id: FAS-PFM-ELG-02
feature: FEAT-PFM-ELG-02
product_area: platform
module: eligibility
revision: 2
status: proposed
product_intent: proposed
source_sha:
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
capabilities:
  - CAP-PFM-ELG-007
  - CAP-PFM-ELG-008
  - CAP-PFM-ELG-009
  - CAP-PFM-ELG-010
  - CAP-PFM-ELG-012
scenarios:
  - id: FAS-PFM-ELG-02-01
    title: Explain and retain an application decision
    kind: behaviour
    exercises:
      - CAP-PFM-ELG-007
      - CAP-PFM-ELG-008
      - CAP-PFM-ELG-009
    relies_on:
      - ATS-PFM-ELG-007-02
      - ATS-PFM-ELG-008-01
      - ATS-PFM-ELG-009-01
    preconditions: 'A compatible use and local subjects with met, unmet and unknown results exist.'
    steps: Evaluate each under the declared failure policy and inspect consequential history.
    expected: 'The caller’s answer and retained state, outcome and reasons agree.'
    negative: false
    data_needs: >-
      Run-owned workspace records, separate caller grants and a controlled clock for time-dependent
      checks.
    bound_to: []
    provenance: proposed
    source:
      - ATS-PFM-ELG-007-02
      - ATS-PFM-ELG-008-01
      - ATS-PFM-ELG-009-01
    action_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-02
        - ATS-PFM-ELG-008-01
        - ATS-PFM-ELG-009-01
    assertion_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-02
        - ATS-PFM-ELG-008-01
        - ATS-PFM-ELG-009-01
    binding_scope: This sequence is proposed and has no executable proof binding.
  - id: FAS-PFM-ELG-02-02
    title: Refresh results and diagnostics after a release
    kind: interaction
    exercises:
      - CAP-PFM-ELG-007
      - CAP-PFM-ELG-008
      - CAP-PFM-ELG-009
      - CAP-PFM-ELG-010
      - CAP-PFM-ELG-012
    relies_on:
      - ATS-PFM-ELG-007-12
      - ATS-PFM-ELG-008-04
      - ATS-PFM-ELG-009-05
      - ATS-PFM-ELG-010-02
      - ATS-PFM-ELG-012-05
    preconditions: A following use has a cached display answer and retained history.
    steps: >-
      Change its rule, publish, evaluate display and authorization, then inspect history and
      diagnostic output.
    expected: >-
      Fresh results use the new expression, authority bypasses cached display data and diagnostics
      disclose no fact payload.
    negative: false
    data_needs: >-
      Run-owned workspace records, separate caller grants and a controlled clock for time-dependent
      checks.
    bound_to: []
    provenance: proposed
    source:
      - ATS-PFM-ELG-007-12
      - ATS-PFM-ELG-008-04
      - ATS-PFM-ELG-009-05
      - ATS-PFM-ELG-010-02
      - ATS-PFM-ELG-012-05
    action_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-12
        - ATS-PFM-ELG-008-04
        - ATS-PFM-ELG-009-05
        - ATS-PFM-ELG-010-02
        - ATS-PFM-ELG-012-05
    assertion_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-12
        - ATS-PFM-ELG-008-04
        - ATS-PFM-ELG-009-05
        - ATS-PFM-ELG-010-02
        - ATS-PFM-ELG-012-05
    binding_scope: This sequence is proposed and has no executable proof binding.
  - id: FAS-PFM-ELG-02-03
    title: 'Suspend, resume and remove a use'
    kind: lifecycle
    exercises:
      - CAP-PFM-ELG-007
      - CAP-PFM-ELG-008
      - CAP-PFM-ELG-009
      - CAP-PFM-ELG-010
    relies_on:
      - ATS-PFM-ELG-007-08
      - ATS-PFM-ELG-007-09
      - ATS-PFM-ELG-008-01
      - ATS-PFM-ELG-010-06
    preconditions: 'A use has plans, retained decisions and a display cache entry.'
    steps: 'Suspend and evaluate, resume compatibly, remove the use and inspect plan and history stores.'
    expected: >-
      Availability controls evaluation while removal clears plans and preserves historical
      decisions.
    negative: false
    data_needs: >-
      Run-owned workspace records, separate caller grants and a controlled clock for time-dependent
      checks.
    bound_to: []
    provenance: proposed
    source:
      - ATS-PFM-ELG-007-08
      - ATS-PFM-ELG-007-09
      - ATS-PFM-ELG-008-01
      - ATS-PFM-ELG-010-06
    action_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-08
        - ATS-PFM-ELG-007-09
        - ATS-PFM-ELG-008-01
        - ATS-PFM-ELG-010-06
    assertion_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-08
        - ATS-PFM-ELG-007-09
        - ATS-PFM-ELG-008-01
        - ATS-PFM-ELG-010-06
    binding_scope: This sequence is proposed and has no executable proof binding.
  - id: FAS-PFM-ELG-02-04
    title: Keep caller contexts and explanation levels separate
    kind: permission
    exercises:
      - CAP-PFM-ELG-007
      - CAP-PFM-ELG-008
      - CAP-PFM-ELG-009
    relies_on:
      - ATS-PFM-ELG-007-11
      - ATS-PFM-ELG-007-13
      - ATS-PFM-ELG-008-08
      - ATS-PFM-ELG-008-09
      - ATS-PFM-ELG-008-10
      - ATS-PFM-ELG-009-05
    preconditions: 'Console, member and registered service callers are available in two workspaces.'
    steps: 'Request plans, evaluation and history in each permitted and forbidden context.'
    expected: >-
      Each context receives only its admitted subjects and explanation detail; foreign history
      remains concealed.
    negative: true
    data_needs: >-
      Run-owned workspace records, separate caller grants and a controlled clock for time-dependent
      checks.
    bound_to: []
    provenance: proposed
    source:
      - ATS-PFM-ELG-007-11
      - ATS-PFM-ELG-007-13
      - ATS-PFM-ELG-008-08
      - ATS-PFM-ELG-008-09
      - ATS-PFM-ELG-008-10
      - ATS-PFM-ELG-009-05
    action_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-11
        - ATS-PFM-ELG-007-13
        - ATS-PFM-ELG-008-08
        - ATS-PFM-ELG-008-09
        - ATS-PFM-ELG-008-10
        - ATS-PFM-ELG-009-05
    assertion_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-007-11
        - ATS-PFM-ELG-007-13
        - ATS-PFM-ELG-008-08
        - ATS-PFM-ELG-008-09
        - ATS-PFM-ELG-008-10
        - ATS-PFM-ELG-009-05
    binding_scope: This sequence is proposed and has no executable proof binding.
  - id: FAS-PFM-ELG-02-05
    title: Return healthy batch entries beside read failure
    kind: regression
    exercises:
      - CAP-PFM-ELG-008
      - CAP-PFM-ELG-009
      - CAP-PFM-ELG-012
    relies_on:
      - ATS-PFM-ELG-008-04
      - ATS-PFM-ELG-009-01
      - ATS-PFM-ELG-012-02
    preconditions: A provider batch contains one failing entry and one healthy entry.
    steps: >-
      Evaluate through provider failure and circuit refusal and inspect the returned entries,
      selected history and metrics.
    expected: >-
      The healthy entry remains answered while uncertain entries keep their reasons and the circuit
      emits the monitored series.
    negative: true
    data_needs: >-
      Run-owned workspace records, separate caller grants and a controlled clock for time-dependent
      checks.
    bound_to: []
    provenance: proposed
    source:
      - ATS-PFM-ELG-008-04
      - ATS-PFM-ELG-009-01
      - ATS-PFM-ELG-012-02
    action_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-008-04
        - ATS-PFM-ELG-009-01
        - ATS-PFM-ELG-012-02
    assertion_evidence:
      provenance: proposed
      source:
        - ATS-PFM-ELG-008-04
        - ATS-PFM-ELG-009-01
        - ATS-PFM-ELG-012-02
    binding_scope: This sequence is proposed and has no executable proof binding.
evidence:
  - CAP-PFM-ELG-007
  - CAP-PFM-ELG-008
  - CAP-PFM-ELG-009
  - CAP-PFM-ELG-010
  - CAP-PFM-ELG-012
  - WF-PFM-ELG-002
  - WF-PFM-ELG-004
  - WF-PFM-ELG-005
  - WF-PFM-ELG-008
  - WF-PFM-ELG-009
  - WF-PFM-ELG-021
---

# Rule Uses and Decisions: Feature Acceptance Suite

## What the Feature Must Do as a Whole

Application connections determine how answers are produced, retained and refreshed. The feature scenarios follow the same connection across availability, caller boundaries and diagnostics.

## Interactions Between Capabilities

Explain and retain an application decision. Evaluate each under the declared failure policy and inspect consequential history.

Refresh results and diagnostics after a release. Change its rule, publish, evaluate display and authorization, then inspect history and diagnostic output.

Suspend, resume and remove a use. Suspend and evaluate, resume compatibly, remove the use and inspect plan and history stores.

Keep caller contexts and explanation levels separate. Request plans, evaluation and history in each permitted and forbidden context.

Return healthy batch entries beside read failure. Evaluate through provider failure and circuit refusal and inspect the returned entries, selected history and metrics.

## Regression Record

| Revision | Change | Scenarios | Reason |
|---|---|---|---|
| 1 | Initial | All | Establish cumulative feature proof from the existing planning and design contracts. |