← Atlas Journey · Docs

Frozen document. Dates and status refer to its original source. Private resources and unreviewed images are unavailable.

Spec: Branching insurance service wizards

Status: researched specification published as issue #101; the owner approved its 20-slice task graph on October 7, 2026. Expanded implementation is pending prerequisite handoffs. This extends issues #23, #24, #90 and #91 without closing or replacing them.

Problem Statement

Atlas currently presents largely one-page insurance forms. A single conditional follow-up does not represent the multi-party evidence, branching intake, corrections and continuing servicing in insurance journeys. Customers cannot see a saved, reviewable path through these stages.

Solution

Deliver Contentful-authored multi-stage wizards for all six products, with answer-driven sections and Camunda-controlled service subflows. Show progress, save/resume, branch changes, a final review and targeted follow-up. Use researched real-world patterns with explicitly fictional product rules and synthetic evidence.

User Stories

  1. As a customer, I want to start a named service journey with its purpose and synthetic-data notice, so that I can choose the correct service.
  2. As a customer, I want to move through labeled steps with Next, Back and a progress summary, so that I can understand what remains.
  3. As a customer, I want to save and resume the current step across sessions, so that I can avoid reentering answers.
  4. As a customer, I want to receive only applicable steps after answering a question, so that I can avoid irrelevant requests.
  5. As a customer, I want to see which later answers will be removed when changing an earlier answer, so that I can make corrections safely.
  6. As a customer, I want to switch en-US and es-US during the wizard, so that I can continue with the same canonical answers.
  7. As a customer, I want to review an accessible summary and edit its sections before final submission, so that I can correct mistakes.
  8. As a customer, I want to receive field errors and a focused error summary, so that I can complete the right fields.
  9. As a customer, I want to upload synthetic evidence with scan status and retry, so that I can know whether it is usable.
  10. As a customer, I want to resume a pinned form release after content changes, so that I can see consistent questions.
  11. As a customer, I want to continue after a connection loss with saved state and operation receipts, so that I can avoid duplicate submissions.
  12. As a customer, I want to see an explicit conflict after another session updates the draft, so that I can avoid overwriting newer work.
  13. As a reviewer, I want to receive the same case with a stage timeline and authorized evidence, so that I can review the complete submission.
  14. As a customer, I want to respond to a targeted request for information on the same case, so that I can avoid starting again.
  15. As a customer, I want to withdraw an eligible request before a committed effect, so that I can cancel unfinished work.
  16. As a technical operator, I want to observe uncertain operations without making insurance decisions, so that I can reconcile delivery safely.
  17. As a life applicant, I want to distinguish myself, the insured person, owner and beneficiaries, so that I can record the correct relationships.
  18. As a life applicant, I want to add multiple beneficiaries with allocations checked before submission, so that I can avoid inconsistent designations.
  19. As a life applicant, I want to answer structured health and coverage-replacement questions, so that I can receive applicable follow-up steps.
  20. As a life applicant, I want to complete EOI details and required synthetic evidence after a relevant answer, so that I can provide reviewable insurability information.
  21. As a life claimant, I want to select a beneficiary or authorized representative claim route, so that I can provide the right claimant relationship and evidence.
  22. As a life claimant, I want to respond to a missing beneficiary or authority-document request, so that I can continue the death-claim review.
  23. As a Medicare supplement applicant, I want to provide synthetic Medicare enrollment and coverage dates, so that I can identify the appropriate enrollment review route.
  24. As a Medicare supplement applicant, I want to identify an asserted open-enrollment or guaranteed-issue situation, so that I can provide evidence for human review.
  25. As a Medicare supplement applicant, I want to answer replacement questions only when replacing coverage, so that I can provide relevant previous-coverage information.
  26. As a Medicare supplement applicant, I want to complete a health-question route when the selected simulated route requires it, so that I can provide underwriter context.
  27. As a Medicare supplement applicant, I want to see that coverage is supplemental and no live eligibility is verified, so that I can understand the demo outcome.
  28. As a disability claimant, I want to describe occupation, last worked date and continuous or intermittent absence, so that I can provide the right claim context.
  29. As a disability claimant, I want to provide injury or illness details and a recurrence route, so that I can receive the right evidence requests.
  30. As an employee, I want to have employer and clinician statements tracked separately, so that I can see outstanding work without impersonating other actors.
  31. As an employee, I want to link a leave request to a disability case without merging approval authority, so that I can track both decisions.
  32. As a manager, I want to review only permitted absence and RTW information, so that I can avoid seeing medical or bank data.
  33. As an employee, I want to update a partial or full return-to-work plan, so that I can continue through the applicable review.
  34. As a dental claimant, I want to choose pretreatment estimate or completed-treatment claim, so that I can avoid representing an estimate as a payment.
  35. As a dental claimant, I want to provide repeatable procedure lines and service dates, so that I can describe multiple services.
  36. As a dental claimant, I want to complete additional tooth, surface, missing-tooth or attachment questions when applicable, so that I can support the relevant procedures.
  37. As a dental claimant, I want to identify other coverage and receive coordination-of-benefits questions, so that I can provide required payment context.
  38. As a dental claimant, I want to review an itemized synthetic benefit breakdown, so that I can understand the simulated decision.
  39. As a long-term-care claimant, I want to choose home care, facility care or a transition between them, so that I can provide the right provider information.
  40. As a long-term-care claimant, I want to describe assistance with activities of daily living or cognitive-supervision needs, so that I can provide assessment context.
  41. As a long-term-care claimant, I want to track clinician assessment, care plan and invoice evidence separately, so that I can see missing documents.
  42. As a long-term-care claimant, I want to submit later care-period invoices without duplicating the original claim, so that I can continue benefit administration.
  43. As an annuity owner, I want to choose partial withdrawal, full surrender or recurring-distribution setup, so that I can receive the correct servicing questions.
  44. As an annuity owner, I want to see qualified or nonqualified contract questions and illustrative charges, so that I can review contract-specific synthetic consequences.
  45. As an annuity owner, I want to identify an asserted hardship or charge-waiver reason with evidence, so that I can request human review.
  46. As an annuity owner, I want to review tax withholding, payout destination and consent before a fresh MFA step, so that I can authorize the intended simulated action.
  47. As an annuity owner, I want to track an uncertain payout and cancel only before the allowed commitment boundary, so that I can avoid duplicate or unauthorized money effects.
  48. As a content author, I want to author bilingual steps, conditional groups and declarative validations, so that I can change supported forms without a frontend deployment.
  49. As a content author, I want to have cyclic, unreachable, incompatible or untranslated wizard definitions rejected, so that I can activate only usable releases.
  50. As a customer, I want to have the server reject hidden fields, skipped mandatory stages and forged tasks, so that I can preserve the workflow rules.
  51. As an auditor, I want to trace answers, rule version, case revision and workflow task to the submitted release, so that I can reproduce the journey.
  52. As a tester, I want to exercise every named branch and recovery path through the integrated seam, so that I can verify more than the happy path.
  1. As an annuity owner, I want to review a contact or beneficiary servicing change with exact before and after values, so that I can confirm the intended update.

Implementation Decisions

Testing Decisions

Out of Scope

Live underwriting, actual Medicare eligibility checks, real payment movement, real medical/customer information, production compliance certification, new products, automatic claims decisions derived from clinical answers, real e-signature contracts and migration of existing pinned releases. State-specific legal forms and carrier rules are not represented as universally valid policy.

Companion acceptance catalog: service stages and branch matrix. Primary-source research is linked there, with source-edition limits.

Further Notes

Use the PR skill's Summary/Evidence/Merge Danger template for all subsequent PRs. Keep one integration branch for this spec and independently verifiable tracer-bullet tickets. The to-issues publication gate requires owner approval of the concrete breakdown before implementation workers start. Existing approvals for earlier small branches do not approve this expanded graph.