UAT - Corrections

### Summary
A user acceptance testing session reviewed the corrections workflow to assess readiness of the modernized approach and gaps against current operations. Feedback confirmed alignment with correcting filings rather than individual data elements, while identifying usability, clarity, and governance issues related to visibility, audit traceability, and staff-only processing. Decisions confirmed the exclusion of certain legacy correction types, upcoming changes to certification and attribution fields, and follow-up actions to address usability, documentation, and preparation for further UAT sessions.

### Feedback Items
- Participants confirmed that correction filings are staff-only actions and are not available to citizens under any circumstance.
- The workflow demonstrated the ability to initiate corrections directly from the filing history, supporting traceability back to the original filing.
- Feedback indicated this approach was clearer than legacy models which corrected individual data blocks.
- Clarification was provided that not all filing types support corrections, with lightweight filings excluded.
- Registered corrections were identified as a distinct filing type, historically represented through Form 47, and processed by registry staff.
- Participants noted confusion caused by the visibility of fees during correction flows, even when staff corrections result in no charge. This behavior was flagged as requiring refinement to avoid misinterpretation during processing.
- Feedback highlighted inconsistent regeneration of Notices of Articles following corrections. Recent changes were described where regeneration occurs only when affected data falls within the document scope.