Eligibility, Responsibilities and Attention
Purpose
This module supplies shared qualification decisions and directs work to the people responsible for it. Its planning layer connects reusable expressions, consumer decisions, responsibility coverage and personal attention.
Boundary
Platform maintains these shared records and evaluates their declarations. Applications own the source data, the business conditions that create work and the actions taken from a qualification answer. Security owns access and derived grants; Websites owns page access; Commerce owns checkout enforcement. Query, metadata, Notifications and operational services provide their respective shared dependencies. Legacy criteria conversion remains outside this scope.
Features
| Feature | Owned Concepts | Capabilities | Journeys | Product intent |
|---|---|---|---|---|
FEAT-PFM-ELG-01 — Rule Library | 1 | 6 | 1 | confirmed |
FEAT-PFM-ELG-02 — Rule Uses and Decisions | 2 | 5 | 1 | confirmed |
FEAT-PFM-ELG-03 — Population and Change Impact | 0 | 1 | 1 | proposed |
FEAT-PFM-ELG-04 — Responsibility Coverage | 1 | 3 | 2 | confirmed |
FEAT-PFM-ELG-05 — Personal Attention | 1 | 3 | 1 | confirmed |
FEAT-PFM-ELG-06 — Attention Follow-up and Settings | 0 | 2 | 0 | confirmed |
Capabilities
| Id | Feature | Title | Product intent | Evidence |
|---|---|---|---|---|
CAP-PFM-ELG-001 | FEAT-PFM-ELG-01 | Author a readable eligibility rule | confirmed | observed |
CAP-PFM-ELG-002 | FEAT-PFM-ELG-01 | Locate rules and understand their dependencies | confirmed | observed |
CAP-PFM-ELG-003 | FEAT-PFM-ELG-01 | Try a rule against real records | confirmed | observed |
CAP-PFM-ELG-004 | FEAT-PFM-ELG-01 | Release, schedule and restore rule versions | confirmed | observed |
CAP-PFM-ELG-005 | FEAT-PFM-ELG-01 | Replace obsolete rules without losing their uses | confirmed | observed |
CAP-PFM-ELG-006 | FEAT-PFM-ELG-01 | Maintain the application-declared rule vocabulary | confirmed | observed |
CAP-PFM-ELG-007 | FEAT-PFM-ELG-02 | Connect a rule to an application decision | confirmed | observed |
CAP-PFM-ELG-008 | FEAT-PFM-ELG-02 | Determine eligibility with an explanation | confirmed | observed |
CAP-PFM-ELG-009 | FEAT-PFM-ELG-02 | Retain the eligibility decisions that matter | confirmed | observed |
CAP-PFM-ELG-010 | FEAT-PFM-ELG-02 | Refresh decisions and request role rechecks | confirmed | partially-observed |
CAP-PFM-ELG-011 | FEAT-PFM-ELG-03 | List qualifying subjects and assess a draft’s impact | proposed | partially-observed |
CAP-PFM-ELG-012 | FEAT-PFM-ELG-02 | Monitor eligibility failures and delays | confirmed | observed |
CAP-PFM-ELG-013 | FEAT-PFM-ELG-04 | Assign accountability for an area of work | confirmed | observed |
CAP-PFM-ELG-014 | FEAT-PFM-ELG-04 | Arrange temporary responsibility cover | confirmed | observed |
CAP-PFM-ELG-015 | FEAT-PFM-ELG-04 | Identify and repair gaps in responsibility coverage | confirmed | observed |
CAP-PFM-ELG-016 | FEAT-PFM-ELG-05 | Maintain attention conditions throughout their lifecycle | confirmed | observed |
CAP-PFM-ELG-017 | FEAT-PFM-ELG-05 | Deliver relevant attention with a reason | confirmed | observed |
CAP-PFM-ELG-018 | FEAT-PFM-ELG-05 | Manage personal responses to attention items | confirmed | observed |
CAP-PFM-ELG-019 | FEAT-PFM-ELG-06 | Escalate overdue attention and plan reminders | confirmed | inconsistent |
CAP-PFM-ELG-020 | FEAT-PFM-ELG-06 | Adjust shared attention and personal visibility | confirmed | partially-observed |
Journeys
| Id | Title | Product intent | E2E policy |
|---|---|---|---|
JNY-PFM-ELG-001 | Release and revise a shared membership rule | confirmed | required |
JNY-PFM-ELG-002 | Connect a product to a qualification rule | confirmed | required |
JNY-PFM-ELG-003 | Assess a draft before changing its audience | proposed | optional |
JNY-PFM-ELG-004 | Follow a closed batch from attention to posting | confirmed | required |
JNY-PFM-ELG-005 | Hand responsibility cover to a colleague | confirmed | required |
JNY-PFM-ELG-006 | Restore ownership of an uncovered area | confirmed | required |
Testing Layers
Each capability has a design test specification, each feature has a cumulative acceptance suite, and the executable register identifies the existing files that provide proof. Coverage findings preserve the unresolved checks and source limitations.