✅ Scope and Integration Responses
1. Primary use case for LMS integration:
The avatar will function as a virtual tutor and real-time Q&A assistant within Moodle, helping students navigate courses, understand assignments, and get clarification on content using voice queries.

2. Intended audience:
Primarily students, though instructors may also use it for task automation and course support.

3. Internal or public rollout:
Initially intended for internal use (single-tenant) within the organization. Expansion to public rollout may be considered after pilot success.

4. Target timelines:

Prototype: 2 weeks

Pilot: 6 weeks

Full production: Within 10 weeks

5. Existing knowledge base for RAG?
Not yet curated.

6. If no, should we extract content from LMS?
Yes, extract course outlines, modules, lesson materials, and FAQs from Moodle to build the knowledge base.

7. Should AI respond from LMS content only or general knowledge too?
Primarily from LMS/internal content, with optional fallback to general knowledge when needed.

8. Custom prompt engineering or adaptive model?
Both — initial prompts will be engineered, but the model should also adapt based on user behavior.

9. Knowledge base update frequency:
Preferably daily, but can fall back to manual updates during the prototype phase.

10. Primary user input mode:
Voice-first (with fallback to text if needed).

11. Multilingual voice input/output required?
Not in the initial version — English only. Other languages (e.g., Urdu, Arabic) may be added later.

12. Speaker adaptation or voice cloning?
Nice-to-have, not essential for MVP. May be explored for personalization in future iterations.

13. Sentiment or emotion detection?
Yes, desirable for improved engagement and empathy (especially in tutoring scenarios).

✅ LMS & Technical Stack Responses
14. LMS platform:
Moodle

15. API access available?
Yes — REST API access is enabled.

16. API documentation or keys?
Can be shared during Phase 1 development.

17. LMS functionalities assistant should handle:

Course navigation

Assignment deadlines & submission status

Gradebook access

Content summaries

Notifications & reminders

Access to uploaded documents

18. LMS authentication protocol:
OAuth2 via Moodle’s standard plugin.

19. Log user interactions for analytics/auditing?
Yes, especially for usage analytics and learning progress tracking.

20. LMS supports embedding external apps/iframes?
Yes, Moodle supports iframe embedding and plugin integration.

✅ Deployment & Infrastructure
21. Azure subscription/resource group?
Not available yet — but will be purchased before development begins.

22. Azure region:
Planning for Southeast Asia or Central India, based on performance and latency.

23. Preferred Azure services:

Azure OpenAI (for GPT integration)

App Service (for web app hosting)

Blob Storage (for storing course files and logs)

Azure Functions (for serverless backend logic)

Azure Cognitive Services (for speech recognition, TTS)

24. Azure OpenAI vs external GPT API?
Azure OpenAI preferred, for smoother integration with other Azure services and data residency control.

25. Autoscaling or container orchestration?
Yes — plan to use AKS (Azure Kubernetes Service) for scalability.

26. CI/CD implementation:
Yes — GitHub Actions will be used for deployment pipelines.

27. Monitoring tools preferred:

Azure Monitor

Application Insights

Log Analytics

28. Azure Active Directory (AAD) for auth?
Yes — AAD will be integrated for staff authentication once subscription is active.

✅ Avatar Preferences
29. Custom avatar needed?
Please design a custom avatar, aligned with the institution's brand.

30. Preferred avatar type:
2D animated for speed and compatibility with Moodle; explore 3D for future immersive applications.

31. Avatar deployment platform:
Embedded in Moodle (course pages and dashboard) + standalone widget for mobile compatibility.

32. Avatar visibility:
On-demand (modal/pop-up) preferred to reduce distraction during learning.