Public Benefit / Program
Describe a public social-benefit program, its versioned provision rules and governed interfaces to assessment, delivery, review and monitoring.
Bundle → Layer → Finding → Questions Filled
6 bundles · 12 layers · 12 findings · 36 questions
Program foundation Identity and authority anchor the persistent program.
Program identity
One governed program identity persists through rule revisions; a beneficiary award or a statistical grouping is not the program.
Program identity
One governed program identity persists through rule revisions; a beneficiary award or a statistical grouping is not the program.
- Which authoritative identifier and namespace distinguish this program from similarly named schemes? identity
- Which benefit functions and cash, in-kind or service forms does the program declare? classification
- Which predecessor, successor or component schemes are linked without asserting identity equivalence? relationship
Mandate and stewardship
Record the jurisdiction, instruments and accountable administering roles as qualified references rather than inferring competence from an operator account.
Mandate and stewardship
Record the jurisdiction, instruments and accountable administering roles as qualified references rather than inferring competence from an operator account.
- Which instrument and territorial profile authorize the program and its administering body? authority
- Which public program steward is accountable for rules, delivery coordination and published information? ownership
- Which effective interval and transition basis apply to each mandate revision? temporal
Qualification and intake Eligibility and evidence profiles define the assessment interface.
Eligibility profile
Express program-specific qualifying conditions with exceptions and assessment units. Contributory status, means testing and coverage breadth are separate axes.
Eligibility profile
Express program-specific qualifying conditions with exceptions and assessment units. Contributory status, means testing and coverage breadth are separate axes.
- Which qualifying rules, exceptions and evidence categories apply to the relevant program revision? requirement
- Is entitlement assessed for a person, household or other defined unit, and how are members related? composition
- How are overlapping benefits, contribution conditions and means tests distinguished in this profile? constraint
Intake and evidence requirements
Describe application or automatic-enrolment routes, minimal evidence and missing-information handling. Individual applications and adjudications remain external records.
Intake and evidence requirements
Describe application or automatic-enrolment routes, minimal evidence and missing-information handling. Individual applications and adjudications remain external records.
- Which application, assisted or automatic-enrolment routes are authorized for this program? process
- Which facts require evidence, from which permitted sources and for which assessment date? evidence
- How can missing, disputed or inaccessible evidence be corrected without being treated as a negative eligibility finding? exception
Provision and resources Benefit design and financing are related but distinct.
Benefit specification
Define the offered amount basis or service scope and its revision. A program schedule describes possible provision, not a granted right or proof of receipt.
Benefit specification
Define the offered amount basis or service scope and its revision. A program schedule describes possible provision, not a granted right or proof of receipt.
- What amount basis, currency or service quantity defines each offered benefit component? definition
- Which rate or scope revision applies to each assessment period and transitional cohort? temporal
- Which assumptions, limits and rounding or indexation rules must an adopted calculation profile validate? validation
Funding and capacity
Record financing categories and evidenced resource constraints separately from legal entitlement. Budget exhaustion does not silently cancel a right.
Funding and capacity
Record financing categories and evidenced resource constraints separately from legal entitlement. Budget exhaustion does not silently cancel a right.
- Which funding sources and accounting references support the program? relationship
- Which resource limits have an explicit legal effect and which are only operational risks? constraint
- Which expenditure, commitments and administrative costs are reported with accounting period and method? measurement
Award and delivery interfaces External determinations and delivery evidence bind to the program.
Assessment and award interfaces
Keep benefit-specific bindings to external applications, decisions and entitlements, with reasons and rule revision. No individual determination is made by this model.
Assessment and award interfaces
Keep benefit-specific bindings to external applications, decisions and entitlements, with reasons and rule revision. No individual determination is made by this model.
- Which application, decision and entitlement masters can be linked to this program revision? relationship
- What rule version, evidence references and authorized decision source must accompany an award link? provenance
- How are pending, refused, granted and disputed outcomes distinguished from a simulation or missing result? state
Delivery and reconciliation interfaces
Define authorized money, in-kind and service delivery arrangements and evidence needed for reconciliation. Financial postings and care episodes are externally mastered.
Delivery and reconciliation interfaces
Define authorized money, in-kind and service delivery arrangements and evidence needed for reconciliation. Financial postings and care episodes are externally mastered.
- Which delivery channels and alternative arrangements support each benefit form? process
- Which external evidence distinguishes an instruction, a completed delivery and an unresolved receipt? evidence
- How are partial, duplicate, failed or reversed deliveries escalated without reissuing an award? quality
Continuity and redress Change policies and review routes preserve contestability.
Change and continuity rules
Describe review triggers, supersession and closure policies. Observed circumstances and program revisions are separate from legally effective changes to awards.
Change and continuity rules
Describe review triggers, supersession and closure policies. Observed circumstances and program revisions are separate from legally effective changes to awards.
- Which reported or observed changes trigger review and how is their source and disputed status recorded? event
- How does the profile distinguish occurrence, reporting, assessment and legal-effect dates? temporal
- Which transition, suspension, recovery or closure rules preserve continuity and require an external decision? lifecycle
Review and redress routes
Describe accessible complaint, reconsideration and appeal routes with decision-specific conditions. Complaint handling, formal review and court proceedings remain distinct.
Review and redress routes
Describe accessible complaint, reconsideration and appeal routes with decision-specific conditions. Complaint handling, formal review and court proceedings remain distinct.
- Which accessible review channels, representation arrangements and reasons notices are provided? access
- Which decision types, time rules and exceptions govern each redress route? constraint
- How are review outcomes and remedial delivery references linked without assuming that an appeal suspends the original decision? relationship
Monitoring and safeguards Aggregates, privacy and provenance support accountable administration.
Coverage and performance evidence
Define measures of reach, timeliness, spending and adequacy with denominators and uncertainty. Statistical benefit functions do not classify individual eligibility.
Coverage and performance evidence
Define measures of reach, timeliness, spending and adequacy with denominators and uncertainty. Statistical benefit functions do not classify individual eligibility.
- Which coverage, timeliness or adequacy indicators are used with defined populations, periods and units? measurement
- What missingness, double-counting or comparability limits qualify the reported measures? quality
- Which statistical classification version and mapping losses accompany an external report? interoperability
Data safeguards and evidence continuity
Separate public program descriptions from protected recipient links. Require an applicable basis, minimal data, retention rules and accountable source provenance.
Data safeguards and evidence continuity
Separate public program descriptions from protected recipient links. Require an applicable basis, minimal data, retention rules and accountable source provenance.
- What lawful purpose, processing basis and additional sensitive-data condition authorize each data category? privacy
- Which schedules, holds and lawful disposal rules apply to program evidence and protected link payloads? retention
- Which recipient scopes, redactions and audit records prevent a program catalogue from exposing personal cases? security
Classifiers Filled
- Family
- World Models
- Category
- Society, people and institutions
- Entry kind
- entity
- Navigation path
- NAV.SOC.POL.PRG
- Domain
- SOC.POL.PRG
- Industry
- Cross-industry
- Tags
- publicbenefitprogramsoc.pol.prg
- Also called
- B13
What it is Filled
One persistent public social-benefit program or scheme, with versioned benefit components and operational profiles. Individual cases, awarded rights, payments and care episodes are linked external instances. This is a proposed research model, not an eligibility engine or a legal authorization.
In scope
- Program identity, authority, territory, benefit forms, eligibility and evidence profiles
- Program-specific interfaces to applications, determinations, entitlement and delivery masters
- Funding context, continuity, redress routes, statistical definitions and evidence safeguards
Out of scope
- Generic project or commercial program management, private insurance claims and charitable grant lifecycles
- Person and household identity masters, detailed health records, care treatment and financial ledger execution
- Making individual eligibility decisions, paying benefits, imposing recovery or suspension, filing appeals or implementing legal calculation engines
Why it exists Filled
Describe a public social-benefit program, its versioned provision rules and governed interfaces to assessment, delivery, review and monitoring.
Distinguishing features Derived, awaiting review
- Unlike WM-POL-001: Pin enabling instruments and amendments; legal-instrument lifecycle remains external.
- Unlike WM-POL-015: Bind territorial applicability and jurisdiction profile; no worldwide rule assumption.
- Unlike WM-POL-016: Resolve competent administering institutions and evidenced delegation.
- Unlike WM-PER-001: Bind person identities only when authorized; do not create a recipient registry here.
- Unlike WM-PER-004: Bind household assessment units and membership semantics without equating household and person.
- Unlike WM-PER-006: Use relevant life-event evidence as a qualified trigger, not an automatic award change.
- Unlike WM-REC-009: Individual applications have separate identity and lifecycle; automatic enrolment can omit an application.
- Unlike WM-POL-017: Administrative cases own procedural progress and review case records; this program supplies profile bindings.
- Unlike WM-POL-021: Decision authority, reasons and legal effect remain externally mastered.
- Unlike WM-POL-014: Granted rights and entitlement instances remain distinct from program benefit schedules.
- Unlike WM-POL-018: Public service descriptions and channels support provision without making every service a benefit.
- Unlike WM-XCT-014: Financial accounts and postings stay ledger-owned; cashless benefits do not require ledger composition.
- Unlike WM-XCT-002: Access contracts and any consent records remain externally governed; consent is not the sole possible legal basis.
- Unlike WM-XCT-004: Link audit evidence without taking ownership of audit-trail semantics.
- Unlike WM-XCT-012: Preserve provenance bindings; generic provenance semantics stay external.
- Unlike Legacy B13 Social Provision and Benefit: Legacy program definition is retained; entitlement, delivery and appeal records become separately mastered links. Legacy conformance, universal access and consent-only claims are not inherited.
Note: Derived from boundary notes against neighbouring models.
What robots and AI may and may not do Derived, awaiting review
Must not
- Under-review ICO guidance cannot be treated as a current automated-decision authorization.
- Deny protected data access unless recipient, purpose and scope are authorized.
May
- Register program description: Proposed, unimplemented local operation. Register program description without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Bind rule profile: Proposed, unimplemented local operation. Bind rule profile without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Link external outcome: Proposed, unimplemented local operation. Link external outcome without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Record reconciliation evidence: Proposed, unimplemented local operation. Record reconciliation evidence without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Record change or review reference: Proposed, unimplemented local operation. Record change or review reference without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Prepare protected aggregate: Proposed, unimplemented local operation. Prepare protected aggregate without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
Note: Derived from functions, policies, CRUD and access rules; prohibitions were not authored for agents as such.
Moral aspects Derived, awaiting review
- Six proposed local operations with authority checks and refusal; wrongful loss of support and privacy leakage remain explicit hazards.
- Reject consent-only privacy rules and unconditional recipient or assigned-officer access.
- Funding context, continuity, redress routes, statistical definitions and evidence safeguards
- Access contracts and any consent records remain externally governed; consent is not the sole possible legal basis.
- Legacy conformance, universal access and consent-only claims are not inherited.
Note: Sentences mentioning harm, privacy, consent or similar, collected from the specification.
Owners Filled
Steward
Name the accountable public program steward, evidenced authority and delegation limits
Roles
- Public program steward
- Maintain accountable identity, authority and profile stewardship
- Policy and legal reviewer
- Verify current scope, exceptions, legal effect and adoption constraints
- Authorized benefit officer
- Maintain qualified links to externally determined cases and awards
- Data protection and records officer
- Approve purposes, recipient scopes, minimisation and disposition
- Monitoring analyst
- Use authorized aggregates and documented statistical definitions
Links to other meta-models Filled
references
- WM-POL-001 - Pin enabling instruments and amendments; legal-instrument lifecycle remains external.
- WM-POL-015 - Bind territorial applicability and jurisdiction profile; no worldwide rule assumption.
- WM-POL-016 - Resolve competent administering institutions and evidenced delegation.
- WM-PER-001 - Bind person identities only when authorized; do not create a recipient registry here.
- WM-PER-004 - Bind household assessment units and membership semantics without equating household and person.
- WM-PER-006 - Use relevant life-event evidence as a qualified trigger, not an automatic award change.
- WM-REC-009 - Individual applications have separate identity and lifecycle; automatic enrolment can omit an application.
- WM-POL-017 - Administrative cases own procedural progress and review case records; this program supplies profile bindings.
- WM-POL-021 - Decision authority, reasons and legal effect remain externally mastered.
- WM-POL-014 - Granted rights and entitlement instances remain distinct from program benefit schedules.
- WM-POL-018 - Public service descriptions and channels support provision without making every service a benefit.
- WM-XCT-014 - Financial accounts and postings stay ledger-owned; cashless benefits do not require ledger composition.
- WM-XCT-002 - Access contracts and any consent records remain externally governed; consent is not the sole possible legal basis.
- WM-XCT-004 - Link audit evidence without taking ownership of audit-trail semantics.
- WM-XCT-012 - Preserve provenance bindings; generic provenance semantics stay external.
aligned
- ESSPROS - Map functions and financing categories conceptually with version and loss reporting; no statistical conformance claim.
- ILO Recommendation No. 202 - Use floor, governance and monitoring guidance as contextual alignment; national implementation must be verified.
- PROV-O - Proposed attribution and derivation mapping only; no implemented RDF binding.
neighbor
- WM-POL-001 - Pin enabling instruments and amendments; legal-instrument lifecycle remains external.
- WM-POL-015 - Bind territorial applicability and jurisdiction profile; no worldwide rule assumption.
- WM-POL-016 - Resolve competent administering institutions and evidenced delegation.
- WM-PER-001 - Bind person identities only when authorized; do not create a recipient registry here.
- WM-PER-004 - Bind household assessment units and membership semantics without equating household and person.
- WM-PER-006 - Use relevant life-event evidence as a qualified trigger, not an automatic award change.
- WM-REC-009 - Individual applications have separate identity and lifecycle; automatic enrolment can omit an application.
- WM-POL-017 - Administrative cases own procedural progress and review case records; this program supplies profile bindings.
- WM-POL-021 - Decision authority, reasons and legal effect remain externally mastered.
- WM-POL-014 - Granted rights and entitlement instances remain distinct from program benefit schedules.
- WM-POL-018 - Public service descriptions and channels support provision without making every service a benefit.
- WM-XCT-014 - Financial accounts and postings stay ledger-owned; cashless benefits do not require ledger composition.
- WM-XCT-002 - Access contracts and any consent records remain externally governed; consent is not the sole possible legal basis.
- WM-XCT-004 - Link audit evidence without taking ownership of audit-trail semantics.
- WM-XCT-012 - Preserve provenance bindings; generic provenance semantics stay external.
- Legacy B13 Social Provision and Benefit - Legacy program definition is retained; entitlement, delivery and appeal records become separately mastered links. Legacy conformance, universal access and consent-only claims are not inherited.
What else AI and robots need to interact with it Incomplete
Identity and identifiers required Filled
- Authoritative master-system identifier with namespace
- Governed stable external URI with revision
- Opaque local UUID with reconciliation status
Direct properties not applicable Not applicable
Not applicable
Institutional or informational subject: no invented physical properties.
Recognition optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Capabilities and actions required Filled
- Register program description: Proposed, unimplemented local operation. Register program description without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Bind rule profile: Proposed, unimplemented local operation. Bind rule profile without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Link external outcome: Proposed, unimplemented local operation. Link external outcome without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Record reconciliation evidence: Proposed, unimplemented local operation. Record reconciliation evidence without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Record change or review reference: Proposed, unimplemented local operation. Record change or review reference without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
- Prepare protected aggregate: Proposed, unimplemented local operation. Prepare protected aggregate without deciding eligibility, changing a legal right, transmitting a payment or submitting an appeal.
Hazards and failure modes optional Missing, in the backlog
Not described yet. This gap is in the card backlog.
Standards and interfaces required Derived, awaiting review
- PROV-O: The PROV Ontology
Context of use required Filled
- ILO Recommendation No. 202 is guidance to states, not a directly executable national entitlement.
- ESSPROS is a European statistical framework; selected UK pages illustrate only their own scope, with territorial and decision-specific exceptions.
- No Cyprus legal profile is inferred from repository location or user timezone.
Sources Filled
- Social Protection Floors: Governance and Financing - annex reproducing Recommendation No. 202 - International Labour Organization
- ESSPROS - Information on data - Eurostat
- Universal Credit - Eligibility - Department for Work and Pensions
- Universal Credit - How you are paid - Department for Work and Pensions
- Universal Credit - Report a change of circumstances - Department for Work and Pensions
- Challenge a benefit decision - Mandatory reconsideration - Department for Work and Pensions
- What are the rules on special category data? - Information Commissioner's Office
- PROV-O: The PROV Ontology - World Wide Web Consortium
Open questions
- Verify current legal and source versions, licensing, jurisdictional applicability and the revised ICO guidance before operational adoption.
- Build and test nested schemas, pinned neighbor bindings and mappings with household, noncash, disputed-evidence, partial-delivery, retrospective-change, redress and disposal fixtures.
- Restore independent external review before canonical or publishable-draft promotion.
- Independent external review remains waived; local self-audit cannot replace it.
- Direct HTTP checks were not attempted under the owner-reported sandbox restriction; no response status was measured.
- Current law, ICO guidance changes, source versions, licensing and territorial applicability need qualified review.
- Nested field schemas, neighbor version pins, benefit calculators, conformance mappings and adversarial instance fixtures remain incomplete.
- Non-UK operational profiles, contributory pension detail, cross-border coordination, emergency schemes and specialist care delivery require further research.
Machine files
Provenance
world-models research · reviewable-draft
Built from: models/wm-pol-012-public-benefit-program/spec.yaml