How vicharanashala/cp1 works
Curio is a logged-in community knowledge platform. Members search the curated FAQ and chatbot first, optionally consult forum results, submit quality-gated questions, and participate in answer resolution; valuable resolved threads can return to the FAQ. Administration governs content, users, and moderation, while scheduled maintenance supports the knowledge lifecycle. The tree and excerpts establish the query and admin paths; several documented FAQ, chatbot, reputation, and job details are represented at their supported directory level because their implementation was not sampled.
Main entry points: models Domain models · App.jsx Application routes · queryService.js Query lifecycle · index.js API routes
Components 28
Member experience
- Application routes
client/src/App.jsx - FAQ and chatbot
client/src/pages/Faq.jsx - Question intake
client/src/pages/AskQuery.jsx - Forum and answers
client/src/pages/QueryDetail.jsx - Admin dashboard
client/src/pages/admin
Knowledge lifecycle
- Query lifecycle
server/services/queryService.js - Submission quality gates
server/services/gibberishService.js - Semantic search
server/services/vectorService.js - Answer resolution
server/services/answerService.js - FAQ and promotion
server/services/faqService.js - FAQ-first chatbot
server/services/chatbotService.js
Governance
- Moderation and governance
server/services/adminService.js - Reputation and users
server/services/userService.js - Curated taxonomy
server/services/taxonomyService.js
API and domain services
- FAQ API
client/src/api/faq.js - Forum API
client/src/api/queries.js - Answer API
client/src/api/answers.js - Admin API
client/src/api/admin.js - API routes
server/routes/index.js - Query controller
server/controllers/queryController.js - Answer controller
server/controllers/answerController.js - FAQ controller
server/controllers/faqController.js - Admin controller
server/controllers/adminController.js - Domain models
server/models
Maintenance
- Scheduled maintenance
server/jobs
Other components
- Member
- MongoDB
- AI provider
Connections 34
- Member → Application routes: uses
- Application routes → FAQ and chatbot: routes to
- Application routes → Question intake: routes to
- Application routes → Forum and answers: routes to
- Application routes → Admin dashboard: routes to
- FAQ and chatbot → FAQ API: requests FAQ
- FAQ and chatbot → FAQ-first chatbot: asks chatbot
- Question intake → Forum API: submits
- Forum and answers → Forum API: loads and updates
- Forum and answers → Answer API: manages answers
- Forum and answers → FAQ API: promotes thread
- Admin dashboard → Admin API: manages platform
- API routes → Query controller: dispatches
- API routes → Answer controller: dispatches
- API routes → FAQ controller: dispatches
- API routes → Admin controller: dispatches
- Query controller → Query lifecycle: invokes
- Answer controller → Answer resolution: invokes
- FAQ controller → FAQ and promotion: invokes
- Admin controller → Moderation and governance: invokes
- Admin controller → Reputation and users: manages users
- Admin controller → Curated taxonomy: curates terms
- Query lifecycle → Submission quality gates: checks submissions
- Query lifecycle → Semantic search: finds similar queries
- Query lifecycle → AI provider: embeds and refines
- FAQ-first chatbot → AI provider: uses model
- Query lifecycle → Domain models: reads and writes
- Answer resolution → Domain models: reads and writes
- FAQ and promotion → Domain models: reads and writes
- Moderation and governance → Domain models: reads and writes
- Reputation and users → Domain models: reads and writes
- Curated taxonomy → Domain models: reads and writes
- Domain models → MongoDB: persists records
- Scheduled maintenance → Domain models: maintains records