Maintain the application-declared rule vocabulary

Purpose

Applications supply the vocabulary that rule authors use. Registration keeps that vocabulary aligned with what applications can actually evaluate.

How It Works

An application deploys its complete declaration set. Platform checks ownership and compatibility before accepting it. Invalid sets return their problems without partial registration. An unchanged deployment leaves the catalogue alone. A changed declaration requires a new version. Deprecation lets existing expressions continue while steering authors toward current choices. Aliases preserve renamed conditions. Withdrawal fails when stored uses still depend on the declaration. Authors see the licensed vocabulary rather than its query implementation.

Relationships

Application declarations supply the authoring vocabulary and the purposes used to check consumer compatibility.

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: The builder exposes condition declarations for licensed applications.Published expressions protect their declared conditions from withdrawal.
Surfaces: consoleapijob
Intent sources: services-platform:docs/proposals/eligibility/17-decision-register.md#D-05services-platform:docs/proposals/eligibility/17-decision-register.md#D-07services-platform:docs/milestones/plans/PLAT-M11-plan.md#2. Scope

Controls

29 controls apply, from the corpus control catalogue.

TC-AVL-001 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-DAT-001 TC-DAT-002 TC-DAT-003 TC-IAM-001 TC-IAM-006 TC-LOG-005 TC-PI-001 TC-PI-003 TC-PI-005 TC-PRV-001 TC-PRV-002 TC-TEN-001 TC-TEN-002 TC-TEN-003 TC-VEN-001 TC-VEN-002 TC-VEN-003

Permissions

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

Business Rules

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

Id	Rule	Kind	Enforced at	Provenance
`01`must prove Confirmed	Applications register complete condition and purpose declarations during deployment, and Platform rejects an invalid declaration set with its problems without persisting any part. origin: services-platform:docs/proposals/eligibility/17-decision-register.md#D-05 proved by `ATS-PFM-ELG-006-01`, `ATS-PFM-ELG-006-11`, `TST-PFM-ELG-326`, `TST-PFM-ELG-465`	validation	service	test services-platform:modules/eligibility/tests/integration/services/registry/register-eligibility-registration.integration.spec.js#answers a refused manifest with ok false and the refusal, rather than throwing
`02`must prove Confirmed	Condition declarations must use compatible operators, their application’s registered datasets and functions, valid subject fields and registered choice sources. proved by `ATS-PFM-ELG-006-02`, `TST-PFM-ELG-465`	validation	service	test services-platform:modules/eligibility/tests/integration/services/registry/register-eligibility-registration.integration.spec.js#names an operator the value type cannot take
`03`must prove Confirmed	Changed declarations require a higher version; an equal or lower version is rejected, while an identical redeployment performs no write. proved by `ATS-PFM-ELG-006-03`, `ATS-PFM-ELG-006-11`, `TST-PFM-ELG-324`, `TST-PFM-ELG-325`, `TST-PFM-ELG-465`	validation	service	test services-platform:modules/eligibility/tests/integration/services/registry/register-eligibility-registration.integration.spec.js#refuses a declaration changed at the same version, saying to bump it, and writes nothing
`04`must prove Confirmed	Omitted declarations are withdrawn unless a published rule uses the condition or a binding uses the purpose anywhere, in which case registration fails with the affected workspace and rule identified. proved by `ATS-PFM-ELG-006-04`, `ATS-PFM-ELG-006-10`, `ATS-PFM-ELG-007-19`, `TST-PFM-ELG-322`, `TST-PFM-ELG-465`	policy	service	test services-platform:modules/eligibility/tests/integration/services/registry/register-eligibility-registration.integration.spec.js#refuses to withdraw a type a published version of a tenant uses, naming the tenant and the definition, and writes nothing
`05`must prove Confirmed	Deprecated conditions continue to evaluate and appear only when explicitly requested; withdrawn conditions never appear in the authoring catalogue. proved by `ATS-PFM-ELG-006-05`, `TST-PFM-ELG-321`, `TST-PFM-ELG-415`	lifecycle	service	test services-platform:modules/eligibility/tests/e2e/eligibility-registry.e2e.spec.js#never lists a withdrawn type, even with deprecated ones included
`06`must prove Confirmed	Renamed conditions preserve their former keys as aliases for existing published expressions. proved by `ATS-PFM-ELG-001-19`, `ATS-PFM-ELG-006-06`, `ATS-PFM-ELG-006-09`, `TST-PFM-ELG-323`, `TST-PFM-ELG-465`	invariant	service	test services-platform:modules/eligibility/tests/integration/services/registry/register-eligibility-registration.integration.spec.js#folds a renamed type into its successor rather than withdrawing it, so the old key keeps resolving
`07`must prove Confirmed	Authoring catalogues include only licensed application conditions and purposes, support subject-kind filtering and omit internal queries and provider functions. origin: services-platform:docs/proposals/eligibility/17-decision-register.md#D-07 proved by `ATS-PFM-ELG-006-07`, `TST-PFM-ELG-320`, `TST-PFM-ELG-415`	permission	service	test services-platform:modules/eligibility/tests/e2e/eligibility-registry.e2e.spec.js#lists the active types of the tenant’s applications in key order, without a deprecated or withdrawn one or an unlicensed application’s
`08`must prove Confirmed	Each process retains its evaluation catalogue for 60 seconds and invalidates that snapshot after its own successful registration. proved by `ATS-PFM-ELG-006-08`, `TST-PFM-ELG-466`	policy	service	test services-platform:modules/eligibility/tests/integration/services/registry/registry-snapshot.integration.spec.js#keeps answering what it read for 60 seconds, though a type was written since
`09` Confirmed	Condition and purpose declarations have no staff-facing mutation route and change through application deployments.	permission	api	test react-console:acceptance/eligibility/playwright/journeys/registry/ELIG-ACC-0015.spec.ts#ELIG-ACC-0015
`10` Confirmed	Platform declares testing, population, simulation and decision purposes plus date and portal-role conditions; portal-role evaluation awaits a user-to-contact relationship.	policy	service	documented services-platform:docs/eligibility.md#6.1 The manifest and the registration function

Scenarios

Id	Given	When	Then	Provenance
`01`	An application registers a renamed condition with its former key.	A workspace evaluates an unchanged publication using the earlier name.	The alias continues to resolve the condition.	test react-console:acceptance/eligibility/playwright/journeys/registry/ELIG-ACC-0011.spec.ts#ELIG-ACC-0011
`02`	An application submits no conditions despite existing published uses.	Deployment attempts registration.	Those dependencies reject withdrawal without changing the catalogue.	test react-console:acceptance/eligibility/playwright/journeys/registry/ELIG-ACC-0016.spec.ts#ELIG-ACC-0016

Planning

Implementation

Maintain the application-declared rule vocabulary ​

Purpose ​

How It Works ​

Relationships ​