One at-need contract followed from GPL to reconciliation. Package selection, removable toggles, à la carte, the discount, an amendment, and the close gate.
The Henderson family. A standard cremation. The contract is built at arrangement on Monday, amended on Tuesday after prep discovers a pacemaker, and closed on the following Monday once services rendered are reconciled against what was actually delivered.
gpl_line_items row whether it appears here in Standard, in a Trade package, or à la carte. The price differs by context: gpl_package_line_items.included_price is the authoritative price for items inside a package, gpl_line_items.unit_price is the à la carte price. Cross-package reporting (“how often did Kearney bill Local Transfer this quarter?”) is a single GROUP BY gpl_line_item_id.
Sophie picks Standard Cremation from the package list filtered by disposition type. The platform materialises seven line items at source_type = package_base, each carrying a snapshot of its package-context price from gpl_package_line_items.included_price.
Sophie toggles “Urn — Standard” off. The platform writes a new line at source_type = package_removed with a negative line_total. The original package_base row stays in place, visible with strikethrough.
Both rows persist so the audit trail records both what the package included and what the family opted out of. The snapshot-pricing rule on contract line items is what carries the original package-context price forward even if the catalogue changes later.
The family wants a death-notice placement and a second hour of memorial coordination. Both land as source_type = ala_carte, snapshot-priced from the gpl_line_items.unit_price catalogue. The package discount, when it lands, will not touch these — à la carte is outside the package.
The Hendersons are a three-generation Kearney family. Sophie enters a 20% discount with a captured reason. Because 20% meets Kearney’s discount_approval_threshold_percent of 15%, the platform refuses to save until an approver is recorded. Sophie taps David; he countersigns from his desk.
The discount is a structured property of case_contracts, not a line item. It applies only to the package portion. The à la carte items above are untouched.
Per the contract’s fixed computation order: package subtotal, then package discount, then à la carte subtotal, then a manual tax entry by the director, then the contract total. Each total is recomputed on every change.
Automated PST and GST is Phase 2. At MVP, the director enters tax as a single number.
The signing surface generates the contract PDF from the structured rows. The Hendersons sign through DocuSign on the tablet in the arrangement room. The envelope returns; the signed PDF lands in S3 through the existing Storage:: service; case_contracts.status flips to signed; signed_at, signed_by_id, and case_document_id are written.
The contract_execution document_gate module’s precondition (status = 'signed' and contract_total > 0) is satisfied. The workflow can proceed.
Rob, the licensed embalmer, examines the remains and discovers a pacemaker not in the intake records. The medical_device_check module records the removal as required before cremation. The device removal itself is service delivery; the resulting fee is a contract concern.
Sophie creates an amendment with amendment_category = mandatory_discovery, version 1, with a captured reason. One new line item is added at source_type = incidental_post_signing for $150. The amendment’s net dollar impact — amendment_total — is $168 with tax.
resignature_threshold_amount is $100, resignature_threshold_percent is 5%, whichever is greater. $168 exceeds the $100 floor. The amendment flags requires_resignature = TRUE; case closure is now blocked on the re-signature. Per §6.10, the category does not gate this — the dollar impact does. A small mandatory_discovery below threshold would not require re-sign; a large discretionary above threshold would.
The signing surface routes a one-page amendment-only document via DocuSign. Martha countersigns from her phone over coffee. resigned_at, resigned_by_id, and resigned_case_document_id are recorded on the amendment row. case_contracts.status remains amended; the re-signature blocker on case closure lifts.
The amendment row itself is immutable. Any correction will be a new amendment with category correction referencing this one — supersession, per §6.9.
After disposition completes and asset_terminal_check passes, the service_contract_reconciliation module activates. The platform pulls every case_services_rendered row with reconciled_contract_line_item_id IS NULL. Three rows remain unreconciled. Per ADR-016 Rule 5, this is Contract Management reading Layer 4 across an aggregate boundary.
| Service rendered | Source | Resolution |
|---|---|---|
|
Pacemaker removal
module_completion
|
medical_device_check completed Tue 09:30 |
Match to existing line item.
Already covered by the Tuesday amendment.
reconciled_contract_line_item_id set to the incidental line. No contract change. |
|
After-hours family meeting — 1.5 hours
manual_director_entry
|
Recorded by Sophie Thu evening, never quoted |
Add as amendment.
Opens a v.3 amendment with
amendment_category = reconciliation. New line at source_type = incidental_post_signing for $245. Below re-sign threshold; Sophie signs off internally. |
|
Florist vendor coordination — 30 min
manual_director_entry
|
Sophie’s note — “should have been in the quote” |
Mark as no-charge.
Director judgment: comped due to quoting error. Captured note explains why. The package discount is unaffected — no-charge is a per-service reconciliation outcome, not a discount mechanism.
|
case_services_rendered rows for this case remain at reconciled_contract_line_item_id IS NULL. The case_close module’s precondition is satisfied. The case closes.
gpl_package_line_items.included_price for package context, gpl_line_items.unit_price for à la carte — at the date the contract was created. A regulator asking “what was the disclosed price for memorial coordination on this date?” has a deterministic answer.case_contract_line_items rows are what answer business questions like “every case this quarter that included a death-notice placement” without opening a single PDF.discretionary, mandatory_discovery, correction, reconciliation, discount_adjustment. Version-numbered per contract. Whether the family must re-sign is determined by dollar impact against the tenant threshold, not by category.case_services_rendered) records what was delivered — automatically from modules, manually from directors. At close, every row resolves: matched to an existing line, added as an amendment, or marked no-charge with a captured reason. The case cannot close until every service is accounted for.This is at-need. Pre-need uses the same GPL, the same package selection, and the same line-item shape, with three differences: it references a Person directly (no Case yet), pricing is locked at signing rather than current-on-arrangement-day, and activation at need-time produces a new at-need contract via the conversion service per ADR-016 Boundary Rule 3. Late attachment — the family producing a pre-need at the arrangement meeting — triggers identical conversion mechanics. See pre-need-contracts-prd.md.
The signing surface that produces the DocuSign envelopes, the priority chain for cremation authorisation (BC: spouse → adult child → parent → sibling → executor), and the five locked document_gate modules live in documents-and-signing-prd.md. The GPL structural model lives in ADR-017 (Proposed). The four-layer audit architecture — including Layer 4 services rendered — lives in ADR-014. The aggregate boundaries are set in ADR-016.