Skip to main content

Chapter 3: The GovBot Architecture — Metabots, Common Bot Objects (CBots) & Collection

3.1 Architectural Philosophy: Modularity and Interoperability

The GovBot architecture is inspired by federalism: a central government (Metabot) working with state governments (CBots) under a common constitution (Collections and Standards). This loosely coupled, modular approach ensures that:

  • MDAs can innovate independently on their CBots without breaking the central system.
  • The system is highly scalable; new services are added by creating new CBots, not by bloating a single monolith.
  • Failure is contained; a bug in one CBot does not bring down the entire GovBot service.
  • Specialisation is enabled; each agency can focus on perfecting their domain-specific knowledge and conversation flows.

This architecture aligns with the GovStack Building Block methodology, treating GovBot itself as a horizontal, reusable component that can orchestrate interactions across other DPI components.

3.2 The Metabot (GovBot): The Central Orchestrator and Public Face

The Metabot serves as the single point of entry for citizens and the main "face" of the service. Its key responsibilities include:

A) Primary Functions

  • Intent Classification and Routing: Performs initial analysis of user queries to determine broad topics (e.g., Birth Registration, Business, Immigration) and routes conversations to appropriate specialised CBots.
  • General Knowledge and Fallback: Handles general queries about government structure, operating hours, and news; serves as fallback when no specific CBot is identified.
  • Consistent User Experience (UX): Maintains uniform tone of voice, branding, and interaction patterns across the entire platform.
  • Channel Management: Orchestrates multi-channel delivery (web, widget, social media, and voice) while maintaining conversation context.

B) Technical Characteristics

  • Lightweight NLP for broad intent classification.
  • Minimal domain-specific knowledge to avoid duplication.
  • Robust fallback mechanisms for unrecognised queries.
  • Session management across multiple interaction channels.

3.3 CBots: Specialised Agency Assistants

Each CBot (Common Bot Object) is a dedicated conversational AI for a specific ministry, department, or agency (MDA). Examples include:

  • BRSBot — Business Registration Service

  • ODPCBot — Office of the Data Protection Commissioner

  • ImmigrationBot — Department of Immigration Services

  • CRSBot — Civil Registration Service

  • KONZABot — Konza Technopolis Development Authority

  • KFCBot — Kenya Film Commission

  • KFCBBot — Kenya Film Classification Board

  • IRSBot — Integrated Population Registration Service

  • Dept of RefugeesBot — Department of Refugees

  • ICTABot — Information and Communication Authority

  • NRBBot — National Registration Bureau

Each CBot Contains:

a) Specialised NLP Components

  • Domain-Specific Intent Recognition: Fine-tuned to understand jargon and intent types within its specific domain.
  • Entity Extraction: Customised to identify relevant entities specific to the agency's services.
  • Context Management: Maintains conversation context for multi-turn dialogues within the domain

b) Conversation Management

  • Agency-Specific Dialogue Flows: Detailed conversation trees for the services provided (e.g., BRSBot: step-by-step guides on company registration).
  • Escalation Protocols: Clear pathways for handing complex cases to human agents within the MDA.
  • Service Integration Logic: Rules and APIs for connecting to the MDA's backend systems.

c) Administrative Interface

  • Content Management Dashboard: Allows non-technical MDA staff to update FAQs, modify answers, and manage knowledge base content.
  • Analytics View: Provides agency-specific insights into query volumes, common issues, and user satisfaction.
  • Testing Environment: Sandbox for trying new conversation flows before deployment.

Benefits of the CBot Approach

  • Domain Expertise: Each CBot becomes highly knowledgeable in its specific area.
  • Independent Development: MDAs can develop and deploy updates without coordination with other agencies.
  • Focused Improvement: Analytics and feedback are specific to each agency's domain.
  • Progressive Enhancement: New features can be piloted with individual CBots before platform-wide rollout.

3.4 Collections: The Centralised Knowledge Fabric with RAG

Collections form the cornerstone of accuracy and trust in the GovBot ecosystem. They are a centralized, vector-based knowledge store that all bots query using Retrieval-Augmented Generation (RAG).

A) The RAG Process in Detail

1. Ingestion Phase

Official Documents → Text Extraction → Chunking → Vectorisation → Vector Database

pgsql Copy code

  • Source Materials: PDFs, web pages, FAQs, policy documents from all MDAs
  • Text Processing: Extraction of clean text from various document formats
  • Intelligent Chunking: Breaking content into meaningful segments (typically 200–500 words) while preserving context
2. Vectorisation
  • Embedding Models: Using multilingual models (e.g., all-MiniLM-L6-v2,multilingual-e5)to convert text into numerical representations
  • Metadata Enrichment: Tagging chunks with source MDA, publication date, document type, and relevance criteria
  • Indexing: Creating search-optimised indices in the vector database (e.g., Chroma)
3. Retrieval Process

User Query → Query Vectorisation → Similarity Search → Relevant Chunks Retrieval

pgsql Copy code

  • Semantic Search: Finding text chunks whose vectors are most similar to the query vector
  • Hybrid Search: Combining semantic search with keyword matching for improved accuracy
  • Relevance Scoring: Ranking results by similarity score and metadata relevance
4. Augmentation and Generation

Relevant Chunks + User Query → LLM Prompt → Verified Response + Citations

markdown Copy code

  • Context-Aware Prompting: Feeding retrieved chunks as context to the Large Language Model (LLM)
  • Instruction Tuning: Explicitly instructing the LLM to base responses only on provided context
  • Citation Generation: Automatically including source references in responses.
5. Response Delivery
  • Traceable Answers: Each response includes source citations
  • Confidence Scoring
  • Fallback Handling: Graceful degradation when high-quality sources aren't available
6. Suggested Queries
  • Additional follow-up questions added at the end of the response

B) Benefits of the RAG Approach

  • Accuracy: Responses grounded in verified official documents
  • Transparency: Citizens can verify information through provided citations
  • Maintainability: Knowledge updates happen by modifying source documents, not retraining models
  • Reduced Hallucinations: LLMs generate responses based on factual sources rather than internal knowledge
  • Multi-language Support: Same knowledge base can serve queries in different languages

3.5 Data Flows and Integration Pattern

A) System Architecture Overview: Key Integration Points

1. User to Metabot Communication
  • Multi-channel Input: Text via web/chat apps, voice via STT
  • Session Management: Maintaining conversation context across multiple turns
  • User Authentication: Optional identity verification for personalised services
2. Metabot to CBot Routing
  • Intent Classification: Determining which CBot should handle the query
  • Context Passing: Transferring relevant conversation history to the specialised CBot
  • Fallback Handling: When no CBot matches or multiple CBots are potential candidates
3. CBot to Collections Querying
  • Query Formulation: Converting user intent into effective search queries
  • Result Processing: Evaluating and ranking retrieved information
  • Response Generation: Creating natural, helpful responses based on source material
4. CBot to Building Block Integration
  • Information Mediator: Secure data fetching from MDA backend systems
  • Identity BB: User authentication and personalised service delivery
  • Payment BB: Transaction processing within conversation flows
  • Workflow BB: Status checks and process initiation

B) Data Security and Privacy

  • End-to-End Encryption: TLS 1.3+
  • Minimal Data Retention: Conversations anonymised after session completion
  • Access Controls: Role-based access to admin interfaces and sensitive data
  • Audit Logging: Comprehensive logging for security monitoring and compliance
  • Data Residency: Adherence to national data protection laws and sovereignty requirements

C) Performance Considerations

  • Response Time Targets:
    • < 7 seconds for text queries
    • < 12 seconds for voice interactions
  • Scalability Architecture: Horizontal scaling of CBots based on demand patterns
  • Caching Strategy: Intelligent caching of frequent queries and responses
  • Load Balancing: Distribution of requests across available CBot instances
  • Monitoring: Real-time performance metrics and alerting for service degradation
Back to top