Partner disability-addition qualification support

21 September 2026. Model-authored source review and bounded implementation; not specialist acceptance, current legal advice or an entitlement decision. This increment uses already captured guidance. It changes one existing concept, adds explicit evidence dependencies and makes four staff profiles inspect a conditional branch. It acquires no new source and changes no historical receipt.

What the component explains

The Department for Work and Pensions’ Decision makers’ guide (DMG) separates the Pension Credit additional amount for severe disability into no-partner and partner branches. An additional amount is a component of an award, not the whole Pension Credit award. Having a partner does not by itself establish that any disability addition is payable.

The existing staff-domain/partner-disability-addition concept now says:

Bounded reading of the captured Pension Credit severe-disability additional-amount rules for a claimant who has a partner. DMG 78045–78047 set distinct lower-rate branches, and 78048–78050 address the higher rate. Their benefit, residence and caring conditions must be read together. DMG 78047's patient branch concerns the other partner being unable to receive the specified benefit because of being a patient for over 28 days; its remaining conditions continue on the next page. DMG 78050 restricts the higher-rate condition when either partner is treated as receiving benefit under the partner-patient provision in 78060(2), and directs consideration of the lower rate. It does not exclude every form of treated receipt. Read the separate CA/UC actual-payment qualification in 78057, in respect of caring for the claimant or partner, and the complete treated-receipt provisions in 78060, with the dated changes in memos 02/25, 06/25 and 01/26. This component does not establish that partner status persists after care-home admission, consolidate current law or calculate an award.

CA means Carer’s Allowance. UC means Universal Credit; its carer element is an amount for caring circumstances. Treated receipt means that the source expressly treats a benefit as received under specified conditions. It is not a general rule that all pending or underlying entitlement is actual payment.

Whole passages rather than isolated paragraph matches

The captured 78046 and 78047 final caring conditions literally refer to the partner receiving “AA” or DLA, although their preceding benefit lists are wider. The whole pages retain that wording. This increment does not silently harmonise those clauses or infer a consolidated benefit list. “AA” is the source’s defined abbreviation associated with Attendance Allowance and specified equivalents; the dated amendments still need reconciliation.

A superscript is not a new subparagraph

The extracted page 14 text says DMG 78060 2.1.. Inspection of the captured PDF rendering shows item 2, followed by superscript footnote 1 and the sentence stop. Footnote 1 cites regulation 6(5)(b). The authored definition therefore describes 78060(2), the partner-patient provision. It does not invent a subparagraph 2.1 or exclude every form of treated receipt in 78060(1).

This is a documented source-layout interpretation. The PDF and extracted text remain unchanged, including the flattened superscript. The interpretation remains model-derived and subject to specialist review.

Exact ten-page support group

The concept authoring uses the existing required_source_ids field. The unchanged producer verifies each target against the concept’s selected source evidence, then emits an existing Dublin Core dcterms:requires relationship. Here a dependency means evidence that must accompany an explanation, not a legal finding of applicability.

Every identifier has prefix https://chris-page-gov.github.io/okf-dwp/id/. Page numbers are one-based PDF pages. The page 17 selection uses the actual anchor which the award is first paid; it does not invent a repeated paragraph number on that continuation page.

All ten pages were already present in the semantic index. This increment adds seven concept-to-page references and ten required-support relationships. The small severe-disability overview still requires only its existing four pages; it does not require this partner component or every detailed branch. All ten new dependencies end at evidence records, so they do not create a dependency cycle between concepts.

The memo pages remain separate dated evidence. In particular, memo 01/26 paragraphs 5 and 6 use different component wording. Those literals are not merged into an invented synonym. Other subjects on a whole page are available for inspection, without becoming statements made by this component.

Conditional navigation and staff-question scope

One new, evidence-backed skos:related relationship connects care-home to partner-disability-addition. It says that a care-home enquiry may require investigation of this branch after household status is examined. It explicitly does not establish continuing couple status or satisfaction of the conditions. Its provenance includes the care-home page 78/25 and the partner passages. It is a navigation link, not an appliesTo assertion.

The profile authoring makes the following bounded additions:

Paths start at an actual existing trigger, follow skos:related to the partner component, then dcterms:requires to each of the ten pages. The producer does not add a partner seed to the care-home questions. Removing the care-home navigation edge causes compilation to reject the now-unreachable qualification group.

Staff 012 and 013 each now have 35 required identifiers and 44 declared paths, including five still-absent obligation identifiers. Their support covers 24 distinct pages; only pages 78/13 and 78/14 are additional to their previous 22-page group. Staff 014 and 017 each have 21 required identifiers and 16 declared paths, with ten partner-support pages alongside their original candidate evidence and five absent obligations.

The existing source-closure obligation label is clarified for each of these four cases. These are four intentional label changes. Every obligation identifier, category, status and resolution remains unchanged. All 203 obligations remain open and all 40 profiles remain insufficient. Original question wording, triggers, candidate identifiers and ambiguities are unchanged; Staff 018’s full authored profile is unchanged. Obligation objects as a whole are not claimed byte-identical because their four labels changed.

Provenance and version boundaries

The subsequent frozen source/assembler comparison passes all 320 assemblies and exact replay. The current assembler retains 585/585 declared path occurrences at 512 KiB and 449/585 at 256 KiB. Whole source records remain unchanged; all contexts remain insufficient. The combined Reader has 20,044 records and 21,242 relationships, with 20 focused controls passing. These later engineering checks do not change the source review's authority.

The captured Chapter 78 PDF has SHA-256 d5e17de1d343fc6a6498089897b222a4989914fa53f85af9ddc8c9c05471e2b8. The whole-page extraction has SHA-256 f90fb5e92c5aebf4c07fb3383ca8bc0bb1ded55448949d987ed87e360c6b4894. Capture was 2026-09-15T14:21:01Z; the retained HTTP Last-Modified observation was 2026-04-16T15:41:27Z. These are source observations, not legal commencement or assurance of current applicability.

The earlier disability review records the receipt-page fingerprints and dated memo boundary. Generated catalogue bindings retain the PDF, extraction and literal hashes for all selected pages. Evidence remains normalised machine extraction with derived authority. Definitions, navigation and support relationships remain model-derived with unreviewed, model-assisted authority. All 520 pre-existing evidence records are identical to the base commit 8ea4465a4cb5a867d82c87e635f2ef1d1df18d8a.

Verification and integration boundary

The existing locked environment and producer were used. No schema, producer or dependency change was needed:

uv sync --locked
uv run --locked python scripts/build_staff_semantic.py
uv run --locked python scripts/build_staff_semantic.py --check
uv run --locked python -m unittest discover -s scripts -p test_staff_semantic.py
uv run --locked python -m unittest discover -s scripts -p test_household_semantic.py

38 staff controls and 14 household controls pass. They cover the exact support group, source hashes, page continuations, restricted patient-reference meaning, actual caring-payment scope, existing triggers, conditional profile warnings, the negative unreachable-route control and preservation of open obligations. The small overview and the existing ambiguous SDA alternatives remain intact.

The semantic producer yields 903 records, 1,482 assertions, 51 authored concepts, 98 selected source pages, 39 support dependencies and four qualification profiles. The index is 4,740,429 bytes, within its existing 8 MiB bound. Snapshot: dwp-staff-semantics-10abede694e3ed57e118. Index SHA-256: 685353567b90db880f1bd1ba33b57ae7ecc430673332ce69e47512a9ae606886.

Only the four semantic producer outputs were regenerated. Combined Reader integration, new context-retention comparisons, publication and model-answer trials are separate work. Earlier 903-record observations bind an earlier source identity and must not be presented as measurements of these declarations.

What this does not complete

• Residence and ignored-person rules are referenced by these passages. Detailed branches, including pages 18–24, are not made universally required or claimed complete here. The ignored-person proposal remains deferred.
• The existing statutory overlay contains regulation 6 and Schedule I paragraphs 1 and 2 of the State Pension Credit Regulations. Links and acquired bodies do not reconcile the relevant version, all amendments or the applicability of their subprovisions. The additional residence material also depends on legal and judgment evidence outside this bounded support group.
• Hospital and funding-specific cessation rules, household facts, territorial scope, benefit-specific qualifications and memo wording remain to reconcile.
• Ten declared support pages do not guarantee their retention in a bounded assembled package. The separate offline 256/512 KiB comparison above measures the frozen source and engine; actual public service delivery remains a separate check. Missing support must remain visible.
• No source-closure, legal, factual-scope or specialist-review obligation is closed by this increment or by passing the engineering tests.