How to adapt use cases
- Replace example questions with your real user questions.
- Map risks to your institution or business rules.
- Choose architecture only after understanding source authority.
- Define evaluation criteria before launch.
Use cases
Each use case includes the problem, recommended architecture, relevant tools, risks, and evaluation criteria.
Students and teachers need grounded explanations across course materials, policies, readings, and institutional guidance.
Patrons and staff need discovery across catalogs, PDFs, archives, metadata, and institutional repositories.
Researchers need to synthesize papers, protocols, datasets, and prior results without losing citation traceability.
Citizens and staff need reliable answers from laws, procedures, forms, and internal guidance.
Teams need answers across knowledge bases, tickets, policies, product docs, and internal systems.
Legal and compliance teams must track changing regulations, cases, policies, and internal interpretations.
Support teams need accurate answers from product docs, policies, tickets, and known issue records.
Archives include scanned documents, mixed formats, uncertain OCR, and complex provenance requirements.