Rename headers (Problem Statement, Architecture Diagram); expand teammate contributions with data-handling roles
Browse files
README.md
CHANGED
|
@@ -45,8 +45,8 @@ short_description: Guarded RAG support navigator for UMD students
|
|
| 45 |
|
| 46 |
| Section | Description |
|
| 47 |
|---|---|
|
| 48 |
-
| [Problem](#problem) | The student-support gap the system addresses |
|
| 49 |
-
| [Architecture](#architecture) | End-to-end pipeline diagram |
|
| 50 |
| [Approach](#approach) | The plan-and-rephrase design pattern |
|
| 51 |
| [Design Iterations](#design-iterations) | How the architecture evolved |
|
| 52 |
| [Datasets](#datasets) | Sources, sizes, licenses |
|
|
@@ -63,7 +63,7 @@ short_description: Guarded RAG support navigator for UMD students
|
|
| 63 |
|
| 64 |
---
|
| 65 |
|
| 66 |
-
## Problem
|
| 67 |
|
| 68 |
University students often need help that sits in the gap between a counseling appointment and a Google search. They have a question, a worry, or a moment of distress, and they need a system that will listen, decide what kind of help is appropriate, and point them to a real resource.
|
| 69 |
|
|
@@ -78,7 +78,7 @@ EmpathRAG addresses both by separating *what to say* from *how to say it*. Routi
|
|
| 78 |
|
| 79 |
---
|
| 80 |
|
| 81 |
-
## Architecture
|
| 82 |
|
| 83 |
```mermaid
|
| 84 |
flowchart TB
|
|
@@ -423,7 +423,10 @@ app.py Hugging Face Spaces entry shim
|
|
| 423 |
### Authorship
|
| 424 |
|
| 425 |
- **Mukul Rayana** — University of Maryland, MSML. Project lead; architecture, code, evaluation design, and end-to-end system development across all design iterations.
|
| 426 |
-
- **Karthik** — University of Maryland, MSML.
|
|
|
|
|
|
|
|
|
|
| 427 |
|
| 428 |
### Course and Use
|
| 429 |
|
|
|
|
| 45 |
|
| 46 |
| Section | Description |
|
| 47 |
|---|---|
|
| 48 |
+
| [Problem Statement](#problem-statement) | The student-support gap the system addresses |
|
| 49 |
+
| [Architecture Diagram](#architecture-diagram) | End-to-end pipeline diagram |
|
| 50 |
| [Approach](#approach) | The plan-and-rephrase design pattern |
|
| 51 |
| [Design Iterations](#design-iterations) | How the architecture evolved |
|
| 52 |
| [Datasets](#datasets) | Sources, sizes, licenses |
|
|
|
|
| 63 |
|
| 64 |
---
|
| 65 |
|
| 66 |
+
## Problem Statement
|
| 67 |
|
| 68 |
University students often need help that sits in the gap between a counseling appointment and a Google search. They have a question, a worry, or a moment of distress, and they need a system that will listen, decide what kind of help is appropriate, and point them to a real resource.
|
| 69 |
|
|
|
|
| 78 |
|
| 79 |
---
|
| 80 |
|
| 81 |
+
## Architecture Diagram
|
| 82 |
|
| 83 |
```mermaid
|
| 84 |
flowchart TB
|
|
|
|
| 423 |
### Authorship
|
| 424 |
|
| 425 |
- **Mukul Rayana** — University of Maryland, MSML. Project lead; architecture, code, evaluation design, and end-to-end system development across all design iterations.
|
| 426 |
+
- **Karthik** — University of Maryland, MSML. Data partner. Contributions include:
|
| 427 |
+
- Curation of the UMD Student Support Conversational Dataset (single-turn, multi-turn, and high-risk scenarios).
|
| 428 |
+
- Compilation and source-verification of the UMD Resource Knowledge Base passages drawn from UMD Counseling, ISSS, ADS, Graduate Ombuds, NIMH, NAMI, SAMHSA, CDC, and 988.
|
| 429 |
+
- Annotation conventions for safety-tier and route labels used by the route classifier and evaluation harness.
|
| 430 |
|
| 431 |
### Course and Use
|
| 432 |
|