How harishb0401/mp-s3 works
This is a full-stack municipal grievance intake, triage, assignment, and resolution platform. Citizens and municipal staff use role-specific portals to submit or manage cases; the Java HTTP server routes requests to the grievance manager, which coordinates prioritization, duplicate review, department/worker assignment, status tracking, notifications, and reporting over dual-mode persistence. The README documents broader portal capabilities not fully visible in the sampled excerpts; edges for those features cite that documentation rather than implying the unsampled implementation was inspected.
Main entry points: GrievanceManager.java Grievance Orchestrator · Database.java Persistence Facade · ServerManager.java HTTP API Server · app.js Role Portals
Components 20
Web Portals
- Role Portals
frontend/js/app.js - API Client
frontend/js/api.js - Dashboard Charts
frontend/js/charts.js
Backend Operations
- HTTP API Server
backend/src/service/ServerManager.java - Grievance Orchestrator
backend/src/service/GrievanceManager.java - Data Validation
backend/src/service/DataValidator.java
Grievance Domain
- Complaint Lifecycle
backend/src/model/Complaint.java - Priority Queues
backend/src/model/DepartmentQueueManager.java - Duplicate Review
backend/src/model/DuplicateCandidate.java - Location Matching
backend/src/model/LocationNormalizer.java - Department Workload
backend/src/model/Department.java - Role Notifications
backend/src/model/Notification.java
Persistence
- Persistence Facade
backend/src/service/Database.java - Relational Repositories
backend/src/repository - MySQL Connection
backend/src/service/DatabaseConnection.java - JSON and Memory Store
backend/src/service/Database.java
Identity and Audit
- User Identity and Roles
backend/src/model/User.java - Status and Audit History
backend/src/repository/StatusUpdateRepository.java
Other components
- Citizens and Staff
- MySQL
Connections 21
- Citizens and Staff → Role Portals: uses
README.md - Role Portals → API Client: requests
README.md - API Client → HTTP API Server: calls API
README.md - HTTP API Server → Grievance Orchestrator: routes operations
backend/src/service/ServerManager.java - HTTP API Server → Persistence Facade: serves data
backend/src/service/ServerManager.java - Grievance Orchestrator → Persistence Facade: coordinates persistence
backend/src/service/GrievanceManager.java - Grievance Orchestrator → Complaint Lifecycle: updates cases
backend/src/service/GrievanceManager.java - Grievance Orchestrator → Priority Queues: queues cases
backend/src/service/GrievanceManager.java - Grievance Orchestrator → Duplicate Review: reviews candidates
backend/src/service/GrievanceManager.java - Grievance Orchestrator → Location Matching: matches locations
backend/src/service/GrievanceManager.java - Grievance Orchestrator → Department Workload: assigns workload
backend/src/service/GrievanceManager.java - Grievance Orchestrator → Role Notifications: creates alerts
backend/src/service/GrievanceManager.java - HTTP API Server → Data Validation: validates input
backend/src/service/ServerManager.java - Persistence Facade → Relational Repositories: uses repositories
backend/src/service/Database.java - Relational Repositories → MySQL Connection: opens connections
backend/src/repository/UserRepository.java - MySQL Connection → MySQL: connects
backend/src/service/DatabaseConnection.java - Persistence Facade → JSON and Memory Store: falls back to
README.md - Persistence Facade → User Identity and Roles: stores accounts
backend/src/service/Database.java - Relational Repositories → Status and Audit History: persists transitions
backend/src/repository/StatusUpdateRepository.java - Role Portals → Dashboard Charts: renders reports
README.md - Citizens and Staff → Role Notifications: receives alerts
README.md