Locate rules and understand their dependencies

Purpose

Staff need to understand a rule’s reach before changing it. Discovery and usage views bring that reach together.

How It Works

A reader searches the configuration catalogue and narrows its results. Visibility controls expose inactive and private entries when needed. The reader opens a rule to inspect its draft and released expression. Usage shows the application decisions connected to it. Version choices reveal which consumers move with publication and which remain pinned. Referencing rules extend the dependency picture. Consistent counts help the reader understand an archive refusal. Permission and workspace boundaries still govern these views. The product should add reporting access to the catalogue.

Relationships

Dependency discovery connects consumer bindings to replacement and retirement review.

Show evidence (sources, provenance, origins, pinned commits)

The Formal Contract

The narrative above explains; the sections below are authoritative — the rules, scenarios and tests this document binds.

Outcomes: Search locates definitions by their name, lifecycle, owner or included condition.Dependency review identifies consumers and included-rule references before a change.
Surfaces: consoleapi
Intent sources: services-platform:docs/milestones/plans/PLAT-M11-plan.md#3. How it works for the userservices-platform:docs/milestones/PLAT-M11-eligibility-rules.md#Decisions

Controls

25 controls apply, from the corpus control catalogue.

TC-AVL-004 TC-AVL-005 TC-AZ-001 TC-AZ-002 TC-AZ-003 TC-AZ-004 TC-DAT-001 TC-DAT-003 TC-DAT-004 TC-LOG-002 TC-LOG-003 TC-LOG-004 TC-LOG-005 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

Permissions

Key	Checked at	Scope
`platform.eligibility.read`	api	tenant

Business Rules

11 rules, 8 to be proved before approval. A rule's product intent is derived from its origin: 11 confirmed by a product decision, the rest inheriting this capability's confirmed.

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Rule, version, usage and decision reads require eligibility read authority, rejecting callers without it, without a role or outside the authorized customer. proved by `ATS-PFM-ELG-002-01`, `ATS-PFM-ELG-002-12`, `ATS-PFM-ELG-009-08`, `TST-PFM-ELG-103`, `TST-PFM-ELG-411`	permission	api	test services-platform:modules/eligibility/tests/e2e/eligibility-definitions.e2e.spec.js#refuses a caller without platform.eligibility.read, 403
`02`must prove Confirmed	Portal callers cannot enter the rule administration routes. proved by `ATS-PFM-ELG-002-02`, `TST-PFM-ELG-411`	permission	api	test services-platform:modules/eligibility/tests/e2e/eligibility-definitions.e2e.spec.js#refuses a portal caller every definitions route, as a context mismatch
`03`must prove Confirmed	The explorer returns only workspace rules in key order and supports status, ownership, reuse, subject kind, used condition and literal case-insensitive name or key filters. proved by `ATS-PFM-ELG-002-03`, `TST-PFM-ELG-098`, `TST-PFM-ELG-439`	policy	service	test services-platform:modules/eligibility/tests/integration/services/model/explorer.integration.spec.js#takes a percent sign in the text literally rather than as a wildcard
`04`must prove Confirmed	Searches exceeding 200 characters and unsupported filter choices fail with the offending parameter named. proved by `ATS-PFM-ELG-002-04`, `TST-PFM-ELG-099`, `TST-PFM-ELG-411`	validation	api	test services-platform:modules/eligibility/tests/e2e/eligibility-definitions.e2e.spec.js#refuses an explorer filter outside the closed list, 400
`05`must prove Confirmed	Rule pages resume after the preceding page’s last key, return 50 entries by default and allow no more than 200. proved by `ATS-PFM-ELG-002-13`	policy	api, service	test services-platform:modules/eligibility/tests/integration/services/model/explorer.integration.spec.js#pages by the key, the cursor resuming after the last record
`06` Confirmed	A rule overview returns its latest publication, current draft and dependency counts. proved by `ATS-PFM-ELG-001-16`, `ATS-PFM-ELG-002-09`	policy	service	test services-platform:modules/eligibility/tests/integration/services/model/explorer.integration.spec.js#answers the version it last published and its draft
`07`must prove Confirmed	Usage organizes bindings by purpose, presents their consumer and version choices, flags outdated pins and lists live referencing rules with their own usage. proved by `ATS-PFM-ELG-002-05`, `ATS-PFM-ELG-002-11`, `ATS-PFM-ELG-007-16`, `TST-PFM-ELG-171`, `TST-PFM-ELG-436`	calculation	service	test services-platform:modules/eligibility/tests/integration/services/governance/usage.integration.spec.js#groups the bindings by consumer kind in kind order, each labelled from the registry and counted
`08`must prove Confirmed	Reference counts include current drafts, published versions of live or deprecated rules and versions pinned by active uses, consistently across discovery, detail, usage and archive refusals. proved by `ATS-PFM-ELG-002-06`, `ATS-PFM-ELG-002-10`, `ATS-PFM-ELG-005-09`, `TST-PFM-ELG-439`	calculation	service	test services-platform:modules/eligibility/tests/integration/services/model/explorer.integration.spec.js#is the number the archive refusal names
`09`must prove Confirmed	A rule outside the current workspace is reported as absent. proved by `ATS-PFM-ELG-002-07`, `ATS-PFM-ELG-002-13`, `TST-PFM-ELG-432`, `TST-PFM-ELG-436`, `TST-PFM-ELG-439`	invariant	service, database	test services-platform:modules/eligibility/tests/integration/services/model/explorer.integration.spec.js#refuses a key the tenant does not have, 404
`10` Confirmed	The console configuration list reveals archived rules through Show Inactive and product-specific rules through Show Private Rules, identifying the owning product. origin: services-platform:docs/milestones/plans/PLAT-M11-plan.md#D2 proved by `ATS-PFM-ELG-002-08`, `TST-PFM-ELG-124`	policy	console	observed react-console:components/configuration/resources/eligibility-rules.tsx:eligibilityRuleResources
`11` Confirmed	The product should make eligibility rules available to reporting; the proposed dataset is absent and the explorer currently reads the rule store directly.	policy	service	documented services-platform:docs/eligibility.md#19. Open items

Scenarios

Id	Given	When	Then	Provenance
`01`	The organization has 60 qualification definitions.	A librarian traverses default and maximum pages and searches a subset.	Each matching rule appears once during traversal.	test react-console:acceptance/eligibility/playwright/journeys/definitions/ELIG-ACC-0075.spec.ts#ELIG-ACC-0075
`02`	A shared expression has a price use, an outdated auditor pin and two references.	The administrator inspects dependencies before editing.	Purpose groups show the uses, flag the lagging pin and include each referencing rule’s usage.	test react-console:acceptance/eligibility/playwright/journeys/governance/ELIG-ACC-0139.spec.ts#ELIG-ACC-0139

Planning

Implementation

Locate rules and understand their dependencies ​

Purpose ​

How It Works ​

Relationships ​