How vinzz006/mahasetu-web works
MahaSetu is a federated government-services platform: a citizen applies once, grants consent, and tracks one application as it passes departmental verification, approval, audit, and benefit disbursement. Its frontend calls a versioned FastAPI backend; the backend coordinates workflow, canonical-data integration, consent, and audit capabilities. The README documents the broader passport, accessibility, and observability features. Several feature modules were not sampled, so their documented presence is shown without assuming internal call wiring.
Main entry points: workflow.py Workflow engine · applications.py Application records · sla_engine.py SLA monitoring · client.ts API client
Components 23
Citizen and Staff Experience
- Web application
frontend/src/App.tsx - Service application
frontend/src/pages/citizen/ApplicationFormPage.tsx - Staff dashboards
frontend/src/pages/admin/SLAMonitorPage.tsx - API client
frontend/src/api/client.ts - Citizen notifications
backend/app/events/handlers.py
API and Workflow Platform
- Versioned API
backend/app/main.py - Application records
backend/app/api/applications.py - Application state
backend/app/models/application.py - Workflow endpoints
backend/app/api/workflow.py - Workflow engine
backend/app/services/workflow.py - SLA monitoring
backend/app/api/sla_engine.py - Lifecycle events
backend/app/events/publisher.py
Department Federation
- Canonical transformation
backend/app/services/transformation.py - Department adapters
backend/app/integrations - Department systems
Trust and Operations
- Consent governance
backend/app/api/consent.py - Audit records
backend/app/services/audit.py - Audit data
backend/app/models/audit.py - Service passport
backend/app/api/export.py - PDF receipts
backend/app/services/pdf_receipt.py - SMS provider
backend/app/services/sms.py - Metrics and probes
backend/app/main.py
Other components
- Citizen or staff
Connections 27
- Citizen or staff → Web application: uses
- Web application → Service application: routes to
- Web application → Staff dashboards: routes to
- Service application → API client: submits through
- Staff dashboards → API client: requests data
- API client → Versioned API: HTTP requests
- Versioned API → Application records: dispatches
- Application records → Application state: reads and writes
- Application records → Workflow engine: advances workflow
- Workflow endpoints → Workflow engine: invokes
- Workflow engine → Application state: updates state
- Citizen or staff → Consent governance: authorizes data use
- Consent governance → Application state: records application consent
- Workflow engine → Canonical transformation: normalizes data
- Canonical transformation → Department adapters: adapts data
- Department adapters → Department systems: connects to
- Application records → Audit records: records actions
- Audit records → Audit data: persists audit
- API client → Service passport: requests passport
- Service passport → PDF receipts: generates receipt
- Staff dashboards → SLA monitoring: views SLA status
- SLA monitoring → Application state: reads applications
- SLA monitoring → Workflow engine: expedites step
- SLA monitoring → Lifecycle events: publishes event
- Lifecycle events → Citizen notifications: dispatches event
- Citizen notifications → SMS provider: sends SMS
- Versioned API → Metrics and probes: exposes probes and metrics