3 - View History & Supporting Documents

## Problem (WHY)
Registry Analysts need to access the history of a manufactured home’s base registration and review or upload supporting documents for a Transfer Upon Death (ToD) filing request. Today, this requires paper files and manual scanning, slowing down processing and contributing to backlogs.

---

## Epic Description (WHAT — MVP)
Provide a digital way for Registry Analysts to view the **base registration history**, see all **uploaded supporting documents** for a filing request, and **upload additional documents**.

This reduces reliance on paper records, streamlines document handling, and ensures Analysts have the information they need to complete the filing review process.

- **Value:**
- Analysts can confirm whether there are relevant historical records affecting the filing.
- Analysts can review QS-submitted supporting documents without mail-ins or scanning.
- Analysts can upload new documents to the filing request digitally.
- **Outcomes:**
- No paper history checks required.
- No mailed-in supporting documents required.
- Reduced scanning backlog.

---

## Goals (outcomes)
- Analysts can open a filing request (Epic 1) and:
- View the base registration history through a linked view.
- Review uploaded documents tied to the filing request.
- Upload additional documents directly into the filing request.
- Analysts complete their work digitally without relying on paper files.

---

## Product Personas (in scope)
- **Registry Analyst** — views base registration history, reviews and uploads documents.
- **Operations staff** — benefit from eliminating paper records and scanning backlogs.

---

## Context
- **Where:** Filing Request Details view (entered from Epic 1).
- **Before:** Analysts pull paper history files and receive supporting documents by mail.
- **After:** Analysts review base registration history online, view QS-uploaded documents, and add new documents directly in the system.

---

## Design Reference Link
Figma: https://www.figma.com/design/rbiPKU4yAW8PqDDjFRBVKQ/Staff-Review-Queue?node-id=2047-5568

---

## MoSCoW — MVP scope clarity
- **Must (MVP):**
- Link to **base registration history** from within the filing request.
- View all uploaded supporting documents for the filing request.
- Upload additional documents into the filing request (with metadata).
- **Should:**
- N/A in MVP scope.
- **Could:**
- Display document metadata such as uploader, date uploaded, file size/type.
- **Won’t (MVP):**
- Automated required-documents validation.
- Inline document sanitization.
- Version control or document comparison.
- Linking to documents across different filing requests.

---

## Roles & Triggers
- **Roles:** Registry Analyst (primary).
- **Trigger:** Analyst has already opened a filing request (Epic 1) and may have assigned it (Epic 2).

---

## Risks & Notes
- Risk: Analysts may expect to see the **full base registration record**, not just history.
- Mitigation: PO to confirm with business if “history only” is sufficient.
- Risk: Uploads may bypass DRS controls.
- Mitigation: Ensure DRS integration from start.

---

## Dependencies & Systems
- Depends on Epic 1 (filing must be open).
- Depends on DRS for document storage.
- May depend on Epic 2 (assignment) if upload restricted to assigned analyst.

---

## Dependencies — BCROS products (cross-product)
- **DRS:** For storage and retrieval of documents.
- **MHR:** For base registration history.

---

## Compliance & Accessibility (guardrails)
- **FOIPPA:** Ensure sensitive records are restricted to staff only.
- **Accessibility:** WCAG 2.2 AA basics — all uploaded docs must be labeled, viewer and upload fields must be keyboard accessible, not colour-only indicators.
- **Auditability:** Record who uploaded each document, with date/time.

---

## Post-MVP Candidates
- Automated validation of required documents (death certificate, will, affidavit).
- Inline document viewer with annotation tools.
- Document comparison or version control.
- “Close and Return” navigation improvements.

---

## Linked MVP Stories
- **3.1 — View Base Registration History (link from filing request)**
- **3.2 — View Uploaded Supporting Documents**
- **3.3 — Upload Documents to Filing Request**

Start with linked stories 3.1, 3.2, and 3.3 and the referenced Figma design. Confirm the Filing Request Details entry point and the Epic 1 dependency, then review how DRS document storage and MHR registration history are accessed. Done means analysts can view history, review uploaded documents, and upload additional documents with the stated metadata, access controls, and auditability.

Written by the indexing model from the issue text.