UX Design - low-res wireframes - Cancel a Registration

Goal: collect requirements for a feature across outstanding entity types; create low-res wireframes showing variances between the entity types.

### Possible approach:
Pull data fields, any logic and help text from [the forms](https://www2.gov.bc.ca/gov/content/employment-business/business/managing-a-business/permits-licences/businesses-incorporated-companies/forms-corporate-registry)
Compare components and identify any missing ones
Low res wireframes
Meet with business SMEs to identify pain points and edge cases

Due: End of January

Cancelling a Registration - Entity types
- [ ] BC Corporations (everything under the Make a Corporation Historical folder in SOFI)
- [ ] Extraprovincial (EP) Corporations & LLCs (Cancel Registration & Notice of Ceasing to Carry on Business in BC)
- [ ] Extraprovincial (EP) Cooperatives
- [ ] BC Limited Partnerships - Dissolution of LP
- [ ] EP Limited Partnerships - Dissolution of XP LP
- [ ] BC Limited Liability Partnership - Cancellation of LLP & Dissolution of LLP (not sure what the difference is)
- [ ] EP Limited Liability Partnership - Cancellation of LLP & Dissolution of LLP (not sure what the difference is)
- [ ] BC Sole Proprietorships
-[ ] BC General Partnerships

**Flowchart**: https://drive.google.com/file/d/1VkcBtiUlfJCPMXLz3iF3iGCPFneoY_P4/view?usp=sharing
This flowchart shows the similarities and differences between creating different entity types. Not all are mapped out, but this will give you an idea of the similarities and things that have already been built.
(note: **"continue in"** has not been built, just mapped out here. No designs to re-use for that one.)

**SOFI Test environment to register test companies:** https://tst.corponline.gov.bc.ca/corporateonline/colin/static/colin/html/index.html
You can use your IDIR to complete all of these (from a staff perspective).
if you need a credit card: 4030000010001234

Start with the linked corporate-registry forms and the flowchart, then compare the listed entity types and their cancellation or dissolution paths. Done means requirements, differences, missing components, pain points, and edge cases are captured in low-resolution wireframes for the listed entities.

Written by the indexing model from the issue text.