9.2 — Analyst sees Document AI validation status in MHR filing review (MVP)

**Priority (MoSCoW):** Must
**Persona:** Registry Analyst
**Value:** Provide analysts with a clear validation status for each uploaded MHR document, so they can proceed with greater confidence in accepting documents online.

---

## User Story
As a **registry analyst**,
I want to **see the Document AI validation result beside each uploaded document in DRS/MHR Filing REquest**,
So that **I know whether the document passed automated checks or was flagged for review**.

## Context
- **Where:** Document Registry Service (DRS), document review section of MHR filing requests.
- **Purpose:** Build analyst trust in digital submissions by showing automated validation results.
- **Flow:** Filer uploads → Document AI runs (9.1) → Analyst sees flag/score while reviewing filing request.
- **Policy fit (BA to confirm):**
- Manufactured Home Act — s.8: Registrar may require supporting documents.
**How this story meets it:** Ensures analysts can validate supporting documents digitally before acceptance.

## UX/UI Link (Design-owned)
_TBD — Design to paste after BA review is complete._

## Sprints
| Role (icon + text) | Forecasted (PO-planned) | Actual (post-planning) |
|:-------------------|:-------------------------------|:-------------------------------|
| 🧭 PO | Sprint __ (________–________) | Sprint __ (________–________) |
| 📌 BA | Sprint __ (________–________) | Sprint __ (________–________) |
| 🎨 Design | Sprint __ (________–________) | Sprint __ (________–________) |
| 💻 Dev | Sprint __ (________–________) | Sprint __ (________–________) |

---

## MVP Boundary (story-level; PO-owned)
- **In:**
- Display a validation status indicator (e.g., “Validated” / “Flagged for Review”) beside each uploaded document in MHR filing review.
- Ensure status is accessible (not colour-only, screen-reader announced).
- Preserve original document view unchanged.
- **Out:**
- Detailed tampering heatmaps or visual overlays (future).
- Analyst override/feedback loop (future).

---

## Acceptance Criteria (PO-owned; user-observable)
- [ ] Analyst sees a **validation status** for each uploaded MHR document in DRS.
- [ ] Status is clearly worded (e.g., “Validated” or “Flagged for Review”).
- [ ] **Accessibility:** Status indicators are text-based, not colour-only, keyboard reachable, focus visible, and announced to AT.
- [ ] **Empty state:** If no document is uploaded, no status indicator is shown.
- [ ] **Unavailable:** If validation could not be performed, show “Validation unavailable — document stored” in plain language.

---

## BA Section (Required before Dev)
*(BA responsible, Design consulted — SM enforces DoR)*

### Definition of Ready — BA gate
- [ ] **BA — please cover completed** (rules, errors, edge cases, authoritative sources, policy refs)
- [ ] Edge cases table filled
- [ ] Draft Gherkin (happy path + key errors)
- [ ] Policy refs confirmed & linked in Context
- [ ] Ticket reviewed with Design (labels/states aligned; Design confirms readiness)
- [ ] UX/UI link pasted (Design)

---

**BA — please cover**
- [ ] Business & validation rules (plain language)
- [ ] Error wording users should see + edge cases (incl. **Unavailable**)
- [ ] **Unavailable wording:** plain-language, non-blocking message
- [ ] Data & authoritative sources (e.g., AI validation output stored in DRS)
- [ ] Constraints/NFRs (performance, availability, audit) if relevant
- [ ] Check with Design on accessibility basics (Design owns the HOW)
- [ ] Policy references (MHA/MHR Reg/FOIPPA) if applicable — see below

**Policy references (BA to confirm)**
- Manufactured Home Act — s.8: Registrar may require supporting documents. Link: https://www.bclaws.gov.bc.ca/civix/document/id/complete/statreg/03075_01
- Manufactured Home Regulation — s.3: Proof of information in a record may be required. Link: https://www.bclaws.gov.bc.ca/civix/document/id/complete/statreg/96_2004
- FOIPPA — s.30.1: Personal information must be stored and accessed only in Canada unless permitted by regulation. Link: https://www.bclaws.gov.bc.ca/civix/document/id/complete/statreg/96165_00

**BA Prompts (things to think about)**
- What exact **labels** should appear? (“Validated” / “Flagged” / “Unavailable”?)
- Should analysts see a **confidence score** (e.g., 95%) or only a binary flag?
- Where on the screen should the indicator appear relative to the document link?
- Should flagged document

No files, tests, or entry points are named. First resolve the missing BA and Design decisions, including validation states, data source, edge cases, and UX/UI, then trace the DRS/MHR filing review flow. Done means each uploaded document shows an accessible status, while empty and unavailable cases match the stated acceptance criteria.

Written by the indexing model from the issue text.