sakbaj/jansunwaiapplication

Purpose and Runtime

LNN-Nivaaran is a municipal grievance-management demo platform: citizens submit text, audio, and image reports; AI classifies and routes them; officers manage queues; administrators view operational analytics. It is a Next.js App Router application running React 19, with Tailwind styling. The root shell and public landing entry are src/app/layout.tsx and src/app/page.tsx.

Route-Level Entry Points and Access

Primary portals are citizen submission/tracking (src/app/citizen/page.tsx), officer operations (src/app/officer/page.tsx), and administration (src/app/admin/page.tsx). Login and role gating are centered in src/app/login/page.tsx, with auth/session behavior in src/lib/auth.ts. Public informational/API documentation routes sit under src/app/help/page.tsx and src/app/api-docs/page.tsx.

Citizen Intake Pipeline

The citizen complaint UI collects complaint content, location, and attachments through src/components/citizen/ComplaintForm.tsx, embedded by src/app/citizen/page.tsx. It calls server endpoints for classification and transcription: src/app/api/classify/route.ts and src/app/api/transcribe/route.ts. Tracking and post-submission communication are represented by src/components/citizen/TrackingTimeline.tsx and src/components/citizen/AIAgentFollowUpPanel.tsx.

AI Boundary and Fallbacks

Gemini 2.5 Flash is the optional external AI service, configured through GEMINI_API_KEY. Server-side API routes isolate Gemini-backed multimodal classification and audio transcription from browser components. If unavailable, local heuristic behavior is implemented in src/lib/ai.ts, using department/keyword definitions from src/data/departments.ts; this supports offline/demo behavior rather than making AI availability a hard dependency.

Complaint State, Routing, and Hotspots

The core domain model is defined in src/types/index.ts. Complaint data and browser-side persistence/query simulation are handled in src/lib/complaints.ts, seeded from src/data/complaints.ts. This layer recomputes active complaints grouped by area and category: clusters of at least two become hotspots, receive elevated priority, and return to normal as resolved items reduce a cluster. Grievance submission has a dedicated persistence-facing API boundary at src/app/api/grievance/submit/route.ts.

Operational and Analytics Views

Officer workflows consume routed, prioritized complaint state in src/app/officer/page.tsx; this is the control point for department queues and status/resolution updates feeding citizen tracking. The administration view aggregates complaint telemetry in src/app/admin/page.tsx, with visualization logic in src/components/admin/AnalyticsCharts.tsx. Citizen-facing hotspot visualization is isolated in src/components/citizen/ComplaintHeatmap.tsx, using the Leaflet/React Leaflet GIS stack.

Infrastructure and Persistence Posture

The shipped architecture is primarily a client-side/demo state model, augmented by Next.js route handlers for AI and grievance submission. A Supabase schema exists at supabase/schema.sql, indicating an intended relational persistence backend, but the core runtime data layer currently lives under src/lib/complaints.ts. Browser APIs support geolocation and local/cross-tab session behavior; Google Gemini is the principal external service.