Delay of Dissolution

# Epic — Delay of Dissolution (MVP)

## Problem (WHY)
Businesses and staff need a clear, compliant way to pause an active involuntary dissolution. Current COLIN behaviour allows anonymous, public, and CRA users to file Delays, which is not aligned with legislation. Existing logic is unclear, does not show trigger dates, and does not enforce policy limits. Users cannot see how a Delay affects their dissolution timeline, and staff do not have proper tools to manage exceptional cases.

## Epic Description (WHAT — MVP)
Deliver a new, policy-aligned Delay of Dissolution filing that only authenticated **business users** associated with the corporation and **staff** can perform. A Delay extends the trigger date for the next phase (or milestone D2/HIS) of involuntary dissolution (D1→D2 or D2→HIS). The system displays current dates, phase, and projected timelines, then shows updated timelines when the user selects a Delay duration. Business users can file two six-month Delays per dissolution instance; staff can apply six months or a custom duration.

- **Value (who benefits & how):**
- **Business users:** Can pause dissolution and see the impact clearly. No anonymous access. Limit of two six-month Delays enforced.
- **Staff:** Can set custom Delay durations, manage exceptions, and apply court-ordered or special arrangements.
- **Analysts/operations:** Gain consistent dates, clear history, and a filing that matches legislation and policy.

- **Statuses (nouns):**
- **D1** (Phase 1 – pre-Gazette)
- **D2** (Phase 2 – Gazette period)
- **HIS** (historical dissolved)

- **Actions (verbs):**
- **File Delay**
- **Select Delay duration** (six months or custom – staff)
- **Confirm Delay**

- **Outcomes:**
- Trigger date for the current dissolution phase is extended.
- Updated projected movement from D1→D2 and D2→HIS.
- Filing appears in history.
- Receipt generated; optional PDF filing under consideration.

## Goals (outcomes)
- Only authenticated business users and staff can file a Delay.
- Business users can file up to two six-month Delays per dissolution instance.
- Staff can file any number of Delays and set custom durations.
- Users see the current phase, current trigger dates, and updated dates before confirmation.
- Trigger-date updates are accurate and consistent with the dissolution engine.

## Product Personas (in scope)
- **Business User:** Authenticated individual associated with the corporation needing to pause dissolution.
- **Registry Staff:** Applies standard or custom Delay durations and manages exceptional cases.
- **Analyst / Operations:** Relies on accurate dissolution timelines and clean filing history.

## Context
- **Where:** Business Registry filing dashboard; Staff dissolution tools.
- **Before:** Corporation is Active, not Frozen, and currently in D1 or D2 of involuntary dissolution (XPROs supported in future).
- **After:** Trigger dates update; filing recorded; receipt available.

## Design Reference Link (Design-owned)
_Please see annotations in figma for dev notes_
Dashboard alert prior to delay: https://www.figma.com/design/LcP4NgVYKVxEk8V7fXWIuc/Involuntary-Dissolution---Delay-of-Dissolution?node-id=2564-1521&t=9qpWdJPu9iuPntc6-1
Non staff form: https://www.figma.com/design/LcP4NgVYKVxEk8V7fXWIuc/Involuntary-Dissolution---Delay-of-Dissolution?node-id=2560-901&t=9qpWdJPu9iuPntc6-1
Staff form: https://www.figma.com/design/LcP4NgVYKVxEk8V7fXWIuc/Involuntary-Dissolution---Delay-of-Dissolution?node-id=2556-9218&t=9qpWdJPu9iuPntc6-1
Dashboard after submission of delay: https://www.figma.com/design/LcP4NgVYKVxEk8V7fXWIuc/Involuntary-Dissolution---Delay-of-Dissolution?node-id=2587-4444&t=9qpWdJPu9iuPntc6-1
Receipt: https://www.figma.com/design/LcP4NgVYKVxEk8V7fXWIuc/Involuntary-Dissolution---Delay-of-Dissolution?node-id=2585-1604&t=9qpWdJPu9iuPntc6-1

---

## MoSCoW — MVP scope clarity
- **Must (MVP):**
- Allow authenticated business users to file a six-month Delay.
- Enforce limit of two Delays per dissolution instance for business users.
- Allow staff to select six months or enter custom durations.
- Show current dissolution phase, entry date, current trigger dates, and projected HIS (when in D1).
- After user selects the duration, show new trigger dates and updated projected HIS.
- Update only the applicable trigger-date fields.
- Block anonymous, public, and CRA users.
- No ledger comment.
- No future effective date.
- Record the filing and generate a receipt.

- **Should:**
- Optional PDF copy of filing.
- Clear visual hierarchy for D1/D2 timelines.

- **Could:**
- Enhanced future UI for timeline visualization.
- Helpful explainer about dissolution phases.

- **Won’t:**
- CRA workflows (handled separately).
- Extra-provincial support (future work).
- Ledger comments (legacy COLIN behaviour).
- Changing dissolution job schedules.

---

## Roles & Triggers
- **Roles:** Business user, Registry staff.
- **Triggers:** Dissolution engine places corp into D1 or D2; user initiates Delay.

---

## Risks & Notes
- Confusion if UI does not clearly show before/after dates.
- Risk of users filing as the dissolution job runs; needs clean date validation.
- CRA may require separate admin tooling later.

---

## Dependencies & Systems
- Involuntary Dissolution engine (D1/D2 trigger-date fields).
- Filing history system.
- Staff dissolution management tools.

## Dependencies — BCROS products (cross-product)

- Entities and your feature both use dissolution states (D1, D2, HIS).
- Both sides need to treat these states the same way (same names, same meaning, same order).
- Both sides also need to record filings the same way in history so a user sees consistent info anywhere in BC Registries.
- Dependency on COLIN? see question below

**Questions:**
- Where does the batch job for delay of dissolution run?

---

## Compliance & Accessibility (guardrails)
- **FOIPPA:** Only authenticated business users and staff may file. No public or anonymous access.
- **Accessibility:** WCAG 2.2 AA — clear labels, keyboard access, visible focus, readable dates.
- **Auditability:** Filing logged with who/when and updated trigger dates.

---

## Linked MVP Stories
- ** — Business user files Delay of Dissolution**
- ** — Staff files Delay with six-month or custom duration**
- ** — Spike: Validate date calculation logic & edge cases**

Start by reviewing the involuntary dissolution engine, filing history system, and staff dissolution management tools, then compare the linked Figma flows with the MVP requirements. Confirm the D1/D2 date rules, access restrictions, filing limits, and receipt behavior before implementation. Done means the business and staff flows record valid Delays and display consistent updated timelines.

Written by the indexing model from the issue text.