Applicant Profile

## Description:
- Short Description of the needed Epic in the below format

* As an intake analyst
* I want an applicant profile
* so that I can see if applicant's have previous, similar requests

* What are the most critical features being built as part of this Epic
* Build a method for identifying an applicant
* Applicant database
* Way for analysts to view applicant request history
* Update applicant details across all open requests
* Thread for applicant history (ie - address history, etc)

----
**Sizing**

* T-shirt size:

[ ] S
[ ] M
[ ] L
[ ] XL

(S=1-2 Sprints, M=2-3 Sprints, L=4-5 Sprints, XL=not sure, probably more than 5 Sprints).

* *Risks and Assumptions**

1. [ ] What are assumptions?
2. [ ] What are the risks?
3. [ ] Have we done an RFC on a technical approach?
4. [ ] Are the dependencies (technical, business, regulatory/policy) known?
5. [ ] Has work on this Epic been prioritized with key stakeholders?

No files, tests, or entry points are named. Start by clarifying the applicant-identification method, applicant database, request-history view, cross-request updates, and history thread, then document assumptions, risks, dependencies, and the technical approach. Done means the scope and approach are agreed.

Written by the indexing model from the issue text.