I'm building "Continuity Agent," a hybrid token-efficient AI routing system for the AMD Developer Hackathon ACT II (Track 1). It's an offline-first backend that helps small Ethiopian businesses keep recording sales during internet or mobile payment outages.
Β
Β
# π Continuity Agent
### *Keeping small business sales alive when the internet β or the payment network β goes down.*
---
### π Quick Links
π Live Demo β’
π API Docs β’
β‘ Quick Start β’
π§ How It Works β’
πΊοΈ Roadmap
---
## πΈ Screenshots & Demo
### Interactive Dashboard
The React dashboard provides real-time transaction monitoring, manual sync control, and a built-in code explorer.
**Note:** the React dashboard is a UI/UX concept demo. Core functionality (offline queue, hybrid AI routing, sync engine) is fully implemented and verifiable directly via the FastAPI backend at /docs (Swagger UI).
Live transaction table with AI routing status indicators
### API Documentation
FastAPI automatically generates interactive API documentation at `/docs`.
Swagger UI with all endpoints and live testing
### Hybrid Routing in Action
Watch transactions flow through the two-tier AI system:
1. **Llama 3.1 8B** classifies each transaction (simple/complex)
2. **Llama 3.1 70B** generates audit notes for flagged transactions
3. **Rule-based fallback** ensures continuity when API is unavailable
---
## π― The Problem
In Addis Ababa and across Ethiopia, small businesses β shops, restaurants, hotel front desks β depend on mobile networks and payment rails like **Telebirr** and **CBE Birr** to record every sale. When the internet drops or a payment provider goes down (a frequent, well-documented occurrence), sales simply stop being recorded. Merchants fall back to paper, memory, or lost revenue. Reconciliation is manual, error-prone, and costly.
**This isn't a hypothetical** β it's a daily operational risk for millions of small merchants across emerging markets, wherever mobile-first commerce has outrun infrastructure reliability.
### Real-World Impact
- π **Lost Revenue**: Sales during outages often go unrecorded
- π **Manual Reconciliation**: Hours spent matching paper records to digital systems
- β **Accounting Errors**: Human mistakes in manual data β¦