Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.
Agreed demo scope
Status: accepted scope, not an implementation specification.
The owner accepted the recommended coverage, intake definition, and payment separation on September 22, 2026. The canonical scope decision is the resolution of Choose the six-product demo journeys and success criteria. Later decisions refined the business access boundaries, record ownership, and fictional product rules. Exact fields remain for specs; the runtime is selected in ADR 0008.
Product coverage and observable outcomes
These are fictional demonstration journeys, not statements of actual product terms or legal requirements.
| Product | Selected journey | Observable success |
|---|
| Life insurance | Application, EOI submission when requested, review, and coverage decision. | The applicant submits the requested information, sees the review result, and can view the resulting coverage following a successful decision. |
| Medicare supplement | Application, missing-information response, and enrollment tracking. | The applicant responds to a request for information and sees the simulated enrollment outcome. |
| Disability income | Claim, evidence, decision, and simulated benefit payout, alongside a separate employer leave/RTW case. | The claimant sees the benefit decision and payout status; the employee and manager can follow the separate leave/RTW path. |
| Dental | Claim against existing seeded coverage, status tracking, and benefit-use summary. | The customer tracks the submitted claim and sees the resulting benefit-use summary. |
| Long-term care | Benefit request, supporting documents, review, and simulated outcome. | The requester supplies evidence and sees the review outcome. |
| Annuities | View an existing seeded contract and request a withdrawal within its available balance. | The customer tracks review and simulated disbursement; a successfully completed withdrawal reduces the balance once. Payout-schedule changes are deferred. |
The demo must show a successful outcome and a meaningful exception for each selected journey. The accepted fictional rule catalog defines evidence gates, correction/review outcomes, amount checks, and simulated payment behavior. Exact task/state transitions remain a workflow decision. The catalog establishes synthetic demonstration behavior, not real insurance eligibility, pricing, or leave-law rules.
Shared capabilities
- A customer dashboard with the relevant policies or contracts and work in progress.
- A document center, including EOI documents where requested.
- Task and status history.
- Draft and resume for the selected applications and claims that span sessions.
- US English (
en-US) and US Spanish (es-US) with a remembered language choice and consistent bilingual form releases.
- Applicable payment-account management, premium collection, and benefit-payout status.
Intake means a new application through a simulated coverage or enrollment decision for the selected intake journeys. Existing policies and contracts are seeded for the servicing demonstrations. Customer-driven linking of existing policies is deferred.
Premium collection uses simulated ACH debits for seeded individual life, Medicare supplement, dental, and long-term-care obligations. Disability is employer-funded in the initial fixtures. Direct-deposit setup and simulated disbursement support disability benefits, long-term-care benefits, and annuity withdrawals. Dental has no separate payout journey; annuity funding and payroll deduction are deferred.
The employer path uses continuous leave date ranges, manager review, and return-to-work review. Required evidence review precedes return approval; managers do not see the medical documents. Employer leave approval does not determine the insurer's disability-benefit decision. Shared case links must preserve those separate decisions.
Actors and access
The owner accepted experiences for customer/employee, manager, insurer reviewer, employer benefits administrator, content author, and technical operator. One person can use a shared login across personal and employer contexts with separate permissions. The accepted roles and access matrix records employer isolation, self-service fixture relationships, staff permissions, and the deferral of manager delegation, impersonation, and dependent/beneficiary representative transactions.
Simulation boundary
Use synthetic customers, documents, policies/contracts, and financial data. Simulate payment execution and legacy systems. The named platform requirements remain in force; simulated legacy systems do not authorize replacing Contentful or Camunda with mocks. The owner selected a local BFF/backend-adapter implementation for the first prototype and moved MuleSoft to a later phase.
An end-to-end demo must make the submission, applicable review, and outcome visible. Later specs will define the verification evidence connecting the UI, workflow, BFF/Experience API, and simulated records. Production integration or real financial execution is outside this prototype.
Deferred work
- Life insurance claims.
- Customer-driven linking of an existing policy or contract.
- Payroll deductions.
- Annuity payout-schedule changes and funding journeys.
- Intermittent leave, statutory entitlement calculations, automated medical underwriting, actuarial pricing, clinical judgments, taxes, and penalties.
- Additional journeys beyond the selected product coverage.
- Real customer data, payment execution, or legacy integration.
These deferrals do not remove the selected benefits, document, leave, or payment capabilities. Expanding the initial journey set requires an explicit scope revision.
Open decisions
The remaining discovery ticket must settle acceptance and handoff evidence. Later specs define exact fields and implementation contracts. Business role boundaries, record ownership, fictional product rules, the bilingual form contract, and the runtime topology are agreed.