---
id: SCR-PFM-ELG-009
title: Eligibility rule history and usage
route: >-
  /console/{tenantId}/configuration/platform/eligibilityRules/{key}/history (and
  /usage)
surface: console
product_area: platform
module: eligibility
revision: 1
status: draft
design_intent: confirmed
origin: >-
  PLAT-M11 plan approved by Andrew 2026-10-21 (version history, comparison,
  rollback, usage and reference migration); the built screen is the approved
  baseline under the UI change approval rule
implementation_evidence: observed
inference: []
source_sha:
  react-console: baf6dae382d6f41dce976c7f848667ccc37e076f
  services-platform: ad3f6a6582843008ed0f5a17b131878d15829af1
purpose: >-
  Inspect release history and active dependencies, compare versions and perform
  permitted rollback or reference migration.
supports:
  - JNY-PFM-ELG-001
  - JNY-PFM-ELG-003
  - CAP-PFM-ELG-002
  - CAP-PFM-ELG-004
  - CAP-PFM-ELG-005
permission: >-
  platform.eligibility.read; Republish needs platform.eligibility.publish;
  Migrate References needs platform.eligibility.retire; Follow Latest needs
  platform.eligibility-bindings.manage
entry_from:
  - 'SCR-PFM-ELG-007: governance navigation'
exits_to:
  - SCR-PFM-ELG-007
displays:
  - field: >-
      Newest-first versions with status, publication details, note and
      simulation line
    source: listEligibilityDefinitionVersions (DOM-PFM-ELG-001)
  - field: Readable version comparison with older logic on the left
    source: diffEligibilityDefinitionVersions
  - field: >-
      Active consumer uses grouped by purpose, follow or pin labels and
      newer-release indicators
    source: getEligibilityDefinitionUsage (DOM-PFM-ELG-002)
  - field: Referencing rule names with follow or pin badges
    source: getEligibilityDefinitionUsage
actions:
  - label: Republish
    operation_id: republishEligibilityDefinitionVersion
    permission: platform.eligibility.publish
    confirm: true
  - label: Follow Latest
    operation_id: updateEligibilityBinding
    permission: platform.eligibility-bindings.manage
    confirm: false
  - label: Migrate References
    operation_id: migrateEligibilityDefinitionReferences
    permission: platform.eligibility.retire
    confirm: true
states:
  - empty
  - loading
  - error
validation:
  - BR-CAP-PFM-ELG-002-07
  - BR-CAP-PFM-ELG-002-08
  - BR-CAP-PFM-ELG-004-08
  - BR-CAP-PFM-ELG-004-11
  - BR-CAP-PFM-ELG-005-05
  - BR-CAP-PFM-ELG-005-06
patterns:
  - PageLayout with standard width
  - PageHeader and breadcrumb
  - VersionHistory and VersionDiff
  - UsagePanel
  - Republish and migration Dialog
  - Toast feedback
component: >-
  components/eligibility/governance/governance-page.tsx; version-history.tsx;
  usage-panel.tsx; version-diff.tsx
evidence:
  - >-
    react-console at baf6dae: components/eligibility/governance/;
    lib/eligibility/api.ts (republish, rePinBinding, migrateReferences),
    diff.ts.
controls: [TC-AVL-004, TC-AVL-005, TC-AZ-001, TC-AZ-002, TC-AZ-003, TC-AZ-004, TC-CHG-001, TC-CHG-002, TC-CHG-003, TC-CHG-004, TC-CHG-005, TC-CHG-006, TC-CHG-007, TC-DAT-001, TC-DAT-002, TC-DAT-003, TC-DAT-004, TC-IAM-001, TC-IAM-002, TC-IAM-004, TC-IAM-005, TC-IAM-006, TC-LOG-001, TC-LOG-002, TC-LOG-003, TC-LOG-004, TC-LOG-005, TC-MON-001, TC-PI-001, TC-PI-002, TC-PI-003, TC-PI-004, TC-PI-005, TC-TEN-001, TC-TEN-002, TC-TEN-003, TC-TEN-004, TC-VEN-001, TC-VEN-002, TC-VEN-003]
---
# Eligibility rule history and usage

## What the Screen Is For

History and Usage provide two views of a definition’s governance: its released expressions and the consumers that depend on it.

## What It Shows and Lets People Do

History opens readable versions, compares selected expressions and confirms republishing a superseded release under a new number. Usage groups active connections, offers re-pin or Follow Latest under binding authority and confirms reference migration from a deprecated rule. It lists reference names and version choices rather than each reference’s own usage count.

## States and Errors

Loading and top-level definition errors use the existing load components. Empty usage explains the lack of dependents. Refused writes produce service feedback. Follow Latest fetches the current binding version immediately before writing and therefore does not protect the version originally reviewed.

## Patterns It Must Respect

Use the existing VersionHistory, VersionDiff and UsagePanel within standard PageLayout and PageHeader. Confirmation dialogs explain republishing and migration; successful actions refresh their related reads.