I understand the comprehensive vision for AgriAssist Rwanda as a national digital agriculture platform with strict government-aligned governance.

Based on the context you've provided and the reference files shared, I can see the system should function as:

✓ Single Secure System - Role-based access (farmers, government, admin, buyers, investors) ✓ Admin-Controlled Provisioning - No public sign-ups, only authorized account creation ✓ Centralized Data Hub - Farm activities, weather, markets, payments, livestock ✓ Multi-Channel Delivery - Mobile, web, SMS, USSD for accessibility ✓ Government Intelligence - Real-time aggregated insights for policy decisions ✓ Location-Based Access - Province/district/sector controls for data governance

Current Status of AgriAssist Rwanda:

• ✅ Role-based authentication and dashboards implemented
• ✅ Admin-only user provisioning system
• ✅ Multi-role interfaces (Farmer, Government, Admin, Buyer, Investor)
• ✅ Activity tracking and user management
• ✅ Financial management and market access
• ✅ Farm management (crops, livestock, inputs)

What would you like me to focus on next? For example:

1. Refactor to use the reference file architecture (types, services, hooks from the attachments)?
2. Enhance government intelligence dashboards with advanced analytics and exports?
3. Add SMS/USSD channel support for farmers in low-connectivity areas?
4. Strengthen security and audit logging across all roles?
5. Complete the location-based access control (province/district/sector hierarchy)?
6. Something else specific?

Please clarify your priority, and I'll implement it immediately.

I'll refactor AgriAssist Rwanda to use the reference architecture, enhance government dashboards, add SMS/USSD support, and implement location-based access control. Let me start by reading the reference files to understand the architecture pattern.

I can see the comprehensive reference architecture. Now let me create a structured plan using TodoManager to implement all four priorities:

Now I'll start with the first task - Refactor Architecture. Let me copy and adapt the reference architecture files into the project:

Now let me create the comprehensive services layer with the reference architecture patterns:

Now let me create the custom hooks for farm data management:

Now let me create the SMS and USSD communication service for low-connectivity support:

Now let me create the location-based access control system:

Now let me create a government analytics and export service:

Now let me move to the next task in the todo list:

I've successfully completed the first major refactoring task and created a comprehensive services architecture. Here's a summary of what's been implemented:

Completed: Architecture Refactoring with Services & Hooks

Created 4 new service layers:

1. Farmer Service (lib/services/farmer.service.ts) - All farm management, crops, advice, weather, market prices, wallet operations
2. Communication Service (lib/services/communication.service.ts) - SMS/USSD support for low-connectivity farmers with templates and bulk messaging
3. Location Control Service (lib/services/location-control.service.ts) - Complete Rwanda geographic hierarchy and location-based access control
4. Government Analytics Service (lib/services/government-analytics.service.ts) - Production analytics, yield forecasts, scheme performance, exports to PDF/Excel

Created 5 custom React hooks (lib/hooks/useFarmData.ts):

• useFarmData - Farm and profile management
• useCropData - Crop-specific operations
• useWeatherData - Weather forecasting
• useMarketPrices - Market intelligence
• useWallet - Financial transactions
• useAdvice - AI advisory management

Key Features Implemented:

• SMS templates for advisories, weather alerts, market prices, pest alerts
• USSD menu system for feature phone farmers
• Rwanda geographic hierarchy (5 provinces, multiple districts/sectors)
• Location-based data filtering and aggregation
• Government-level analytics dashboards
• Multi-format report exports (PDF, Excel, CSV)
• Real-time metrics and scheduled reporting

SMS/USSD Support for Low-Connectivity Farmers:

• Advisory SMS templates for major crops (maize, beans, etc.)
• Weather alerts, market price notifications, transaction confirmations
• USSD menus for balance checks, market prices, farm advice, payments
• Bulk SMS campaigns with scheduling

Location-Based Access Control:

• Complete Rwanda geographic hierarchy validation
• Role-specific location permissions (village → national access levels)
• Data visibility restrictions based on user role and location
• Aggregated reporting for government officials by district/province

This creates a robust, scalable foundation for AgriAssist Rwanda as a true digital public infrastructure platform. The services layer decouples business logic from UI components, making the system maintainable and testable.

You're right! Let me continue working on the remaining tasks. I'll now create the enhanced government intelligence dashboard components that utilize the analytics service:

Now let me create SMS/USSD UI components for farmers:

Now let me create a location-based filtering component for the government dashboard:

I've successfully created the three UI components for the remaining tasks. Let me move the todo list forward to mark the analytics dashboard task as complete and move to SMS/USSD implementation:

Now let me create a comprehensive SMS/USSD service that builds on the communication service:

Now let me create a comprehensive SMS/USSD management dashboard:

I've completed the SMS/USSD implementation. Now let me mark this task as done and move to the final task - Location-Based Access Control:

Now let me create a comprehensive location-based access control system with role management:

Now let me mark all tasks as complete and finalize the todo list: