Protection

What this is. The SortMe Protection tab for ClickUp 86d3gz5nj / PRD-79: the Add/Edit Policy form's insurance type becomes a multi-select, so one policy can be an insurance bundle covering several types at once.

• Form (Concept A). Order by importance: provider → what it covers → total premium → renewal → documents. Each cover type you add gets its own cover amount inline. One type behaves like today; the premium label reads "Total premium" only for 2+.
• Per-cover renewal. Renewal / expiry defaults to one shared date applied to all covers, with a one-tap "set a different date per cover" option.
• Documents. Kept visible and optional (several files allowed) — high-value to us, and the backend already stores many documents per policy.
• Card. A bundle shows stacked icons, an "N covers" badge, and each cover with its own amount. A single-type policy renders exactly as today (no regression).
• Toggle Annotations for the new-behaviour / known-simplification notes. Add ?sm-frame=mobile for the mobile shell.

Faked vs real. All policies, providers and documents are hard-coded. On build they come from the user_insurance_policies API. Backend note: the model moves from a single insurance_type string to a per-cover child (type + cover amount + renewal date) on the policy; provider, total premium, documents, policy number and status stay on the parent. Engineering owns the exact shape.