Prototype dossier — Smart India Hackathon 2026
LAMS
Real-Time National Land Acquisition & Management System
One parcel of land, followed from proposal to possession — on a single map, in real time, whichever order each state already does its own paperwork in.
Cycling the parcel lifecycle from PRD §13.3 — this is what one `LandParcel` record lives through.
Sheet 01 / 16 — Why the platform is needed
The process today has no shared system of record
Land acquisition is state-executed and centrally guided, so every state built its own tools, at its own pace, in its own format. A file moves through thirteen conceptual steps between a District Collector's desk and the State Revenue Department — on paper, at every step. Select a stage below; the ones marked in red are named directly in the PRD's bottleneck analysis (§4).
Land Requiring Body identifies need
A highway, railway, canal or corridor project defines a land requirement and a file is opened — on paper, from day one.
Physical file prepared
Paper-based, with no standard proposal format across states — the first place a national comparison already breaks down.
Manual submission to District Collector
The file is physically carried or couriered to the District Collector's office — no digital record exists yet.
District-level verification — paper records
No shared GIS layer exists, so parcel identity is confirmed manually against paper cadastral maps.
State Revenue Dept. processing
The file physically moves between desks; the requiring body has no visibility into where it currently sits.
Preliminary notification — manual gazette
Published manually; objection records are kept on paper, so the audit trail is easy to lose.
Objection hearing, in person
Landowners must appear physically to raise or contest an objection.
Final notification
Issued once objections are resolved — again through the manual gazette process.
Award declared — manual computation
Compensation is computed in spreadsheets, disconnected from any central rate or circle-rate database.
Compensation disbursed — separate treasury system
The treasury system is disconnected from the land record. "Paid" is often known only to Finance — not the LAO, and not the citizen.
R&R assessed — separate department
A separate department, a separate database — historically the least-tracked stage nationally.
Possession taken — manual panchnama
Recorded on paper; no digital parcel-level possession flag is visible outside the district.
Handover to requiring body
The project can finally take physical possession — often years after the file was first opened.
Select any stage above — the eight flagged in red are where the PRD's bottleneck table places the specific breakdown.
Sheet 02 / 16 — The TO-BE solution lifecycle
End-to-end digitized solution workflow
LAMS replaces paper file movement with a parcel-linked workflow engine, live compensation ledger, R&R tracking, and continuous AI delay-risk evaluation (PRD §5 & §10).
1. Project Proposal Submission
2. Digital Scrutiny
3. GIS Parcel Tagging & Verification
4. Configurable Approval Engine
5. Preliminary Notification (Sec 11)
6. Digital Objection Window
7. Declaration & Final Notification (Sec 19)
8. Award Declaration
9. Compensation Assessment
10. Compensation Disbursement
11. Affected / Displaced Family Registration
12. R&R Entitlement Package Tracking
13. Parcel-Level Possession Recording
14. Handover & Project Closure
15. Continuous AI Delay-Risk Monitoring
Select any solution stage above to inspect its data inputs, outputs, SLAs, and statutory failure conditions.
Sheet 03 / 16 — System Architecture & Component Interconnect
Modular Monolith with Dedicated GIS & AI Services
LAMS runs as a clean FastAPI modular monolith with PostGIS as the single unified source of spatial and relational truth, supported by GeoServer tile serving and XGBoost ML background inference (PRD §25 & §46).
Frontend Client (Next.js + MapLibre GL)
Renders responsive dashboards, vector map tiles, and mobile offline PWA forms.
API Gateway & CDN Layer
Handles SSL termination, rate limiting, request routing, and tile caching.
Keycloak Identity & Auth
Provides OAuth2/OIDC, MFA, and embeds jurisdiction claims in JWT tokens.
FastAPI Core Application
Houses modular business logic: proposals, compensation, R&R, possession, and audit logging.
Config-Driven Workflow Engine
Executes state-specific approval templates dynamically from JSON definitions.
PostgreSQL + PostGIS Database
Unified transactional and spatial storage. Stores parcel polygons, financial ledgers, and audit logs.
Redis Cache Layer
Caches session tokens, user permissions, and materialized dashboard aggregates.
GeoServer GIS Engine
Serves spatial vector tiles (MVT) and raster overlays directly from PostGIS spatial indexes.
RabbitMQ Message Queue
Offloads async tasks: background ML inferences, notification dispatch, and PDF/MIS exports.
XGBoost Delay-Risk Service
Runs tabular delay predictions asynchronously and computes SHAP feature importance values.
S3 Document Storage
Stores uploaded gazette notices, survey reports, and photo panchnama evidence with SHA-256 checksums.
Notification Service
Dispatches SMS, Email, and in-app alerts on workflow transitions and SLA breaches.
Integration Gateway
Implements adapter pattern to interface with external land record APIs and Bhuvan services.
External Government Portals
State Land Records (Bhulekh/Dharani/Bhoomi), Bhuvan Geoportal, and PFMS Treasury APIs.
Select any architecture node above to inspect its design rationale and operational responsibility.
Component Interconnect & Data Flow Traces
Select a real-world scenario to trace data movement across Frontend, Backend, Database, GIS, and ML services:
Sheet 04 / 16 — GIS & Spatial Architecture
The Parcel Geometry is the Anchor for Every Module
GIS is not a decorative map widget in LAMS. Every financial record, family entitlement, and possession panchnama attaches to a verified `LandParcel` spatial polygon in PostGIS (PRD §12).
Spatial Storage
Stored as GEOMETRY(Polygon, 4326) with GiST spatial indexing. Supports spatial operations like ST_Within, ST_Intersects, and ST_Buffer.
High-Performance Serving
GeoServer serves Vector Tiles (MVT) and WMS layers for snappy client rendering even with millions of parcel polygons nationally.
Open-Source Map Client
Client-side vector map rendering with zero proprietary API key vendor lock-in. Directly renders state/district boundaries and parcel overlays.
Interactive GIS Layer Visualizer Simulation
Toggle spatial layers below to simulate how the LAMS Map view dynamically overlays project alignments, cadastral polygons, and status flags:
Sheet 05 / 16 — Relational & Spatial Data Model
17 Core Entities Ensuring End-to-End Auditability
LAMS links project proposals directly to physical land geometry, multi-owner equity shares, financial disbursements, social impact family records, and system-wide audit logs (PRD §13).
LAND_PARCEL
ULPIN, survey/khasra no., geometry, declared vs computed area, acquisition_status.
COMPENSATION
Owner ID, parcel ID, amount_assessed, amount_approved, amount_disbursed, status.
DISPLACED_FAMILY
Family head, household size, category, linked RRPackage, relocation status.
AUDIT_LOG
Actor ID, action, entity, before/after JSON payload, timestamp, IP address.
Parcel Lifecycle State Machine
Every parcel transitions strictly through these legal states. Every transition generates an immutable `AuditLog` entry:
Sheet 06 / 16 — Config-Driven Workflow Core
State Approval Processes as Data, Not Code Changes
State-specific land acquisition laws are accommodated by defining approval chains, SLAs, and escalation logic inside JSON data templates — zero core code edits needed to onboard a state (PRD §14).
Sheet 07 / 16 — Core Functional Engines
Six Specialized Platform Engines
Every phase of the RFCTLARR 2013 lifecycle is powered by a dedicated domain module inside the modular monolith (PRD §11 & §15-18).
Proposal & Scrutiny Engine
Digitizes proposal filing by Requiring Bodies, enforces mandatory survey documents, and provides revenue officer defect resolution toolkits.
3-Tier Compensation Ledger
Tracks compensation through Assessed → Approved → Disbursed per owner/parcel. Explicitly surfaces unpaid compensation backlogs.
R&R Entitlement Engine
Separates economically affected families from physically displaced families. Tracks housing, land-for-land, and annuity package completion.
Parcel Possession Manager
Records possession parcel-by-parcel with mandatory geo-tagged photo panchnama evidence attachments. Derived project possession %.
Document Vault (SHA-256)
Version-controlled document repository with mandatory SHA-256 cryptographic checksums preventing unauthorized file tampering.
Timeline & SLA Engine
Monitors legal statutory deadlines and automatically triggers notifications and escalations upon SLA breaches.
Sheet 08 / 16 — Role-Based Dashboards & MIS
Near-Real-Time Executive Visibility
4-level drill-down hierarchy: India (National) → State → District → Project → Parcel, powered by PostGIS materialized views (PRD §19 & §20).
Sheet 09 / 16 — AI Delay-Risk Early Warning System
XGBoost + SHAP Explainable Delay Prediction
Predicts project delays before milestones are missed using tabular feature inputs. Purely advisory — never changes legal approval status (PRD §21).
Interactive AI Delay-Risk Simulator
Adjust the project risk parameters below to calculate real-time delay probability and view SHAP explainability weights:
Estimated Completion Delay: +42 Days
Sheet 10 / 16 — Data Provenance & Honesty Framework
Full Transparency on Real vs. Synthetic Data
LAMS uses real open government datasets for administrative boundaries and DILRMP stats, while using synthetic data for personal parcel/compensation records with explicit audit tags (PRD §22).
| Dataset | Source Organization | Format | Public Availability | Prototype Strategy |
|---|---|---|---|---|
| LGD Directory | Ministry of Panchayati Raj | CSV / Web Service | Public | Used directly (Real Data) |
| Admin Boundaries | geoBoundaries / Survey of India | GeoJSON / Shapefile | Public | Used directly (Real Data) |
| DILRMP Progress | Dept of Land Resources | CSV / Portal Stats | Public | Used directly for narrative context |
| Parcel Ownership (RoR) | State Land Record Portals | Restricted API | Private PII | Synthetic Data (labeled is_synthetic=true) |
| Compensation Ledgers | State Treasury Systems | Restricted | Private Financial | Synthetic Data (circle-rate derived) |
Sheet 11 / 16 — Integration Gateway & Adapters
Adapter Pattern Isolates External Dependencies
The `IntegrationGateway` uses fixed interface contracts so core platform logic never calls external government portals directly. Production onboarding requires swapping mock adapters for live endpoints (PRD §24).
Bhulekh / Bhoomi / Dharani
Fetches parcel survey records and RoR ownership shares via state API adapters.
ISRO Bhuvan / SVAMITVA
Imports drone cadastral geometry, satellite basemaps, and administrative boundary overlays.
PFMS State Treasury
Pushes approved compensation disbursement vouchers and returns bank payment settlement receipts.
Sheet 12 / 16 — Recommended Technology Stack
Production-Grade Open-Source Stack
Chosen for high developer velocity, zero vendor billings, native spatial GIS support, and explainable ML (PRD §26 & §28).
Next.js + TypeScript
Fast SSR web app with Tailwind CSS styling.
MapLibre GL JS
Open-source client vector tile rendering.
FastAPI (Python)
Async high-performance REST API monolith.
PostgreSQL + PostGIS
Unified relational & spatial spatial database.
GeoServer
OGC compliant WMS/WFS/MVT tile server.
Custom JSON Engine
Config-driven state approval execution.
Redis
Session store & materialized view caching.
XGBoost + SHAP
Tabular delay prediction & explainability.
Sheet 13 / 16 — Security Architecture & Scalability
Jurisdiction Scoping & High-Throughput Design
Security is enforced server-side via JWT jurisdiction claims (State/District ID embedded). Scale is achieved via PostGIS MVT tiles and Redis materialized view caching (PRD §29 & §31).
Multi-Tenant Jurisdiction RBAC
Every API query checks JWT claims. A Ghaziabad district officer cannot access Lucknow parcel records even if API parameters are tampered with. TLS 1.2+ transit, AES-256 storage, and SHA-256 document checksums.
National Scale Execution
Designed for 10,000+ concurrent projects and millions of parcels. Read replicas handle dashboard aggregation loads. GeoServer MVT vector tiles prevent server strain by rendering tiles on client GPUs.
Sheet 14 / 16 — Stakeholder Permission Matrix
12 Defined User Roles Across All Levels
Every administrative level has custom tailored dashboards and strict read/write boundaries (PRD §7 & §11.3).
| Stakeholder Role | Jurisdiction Scope | Key Platform Actions | Assigned Dashboard |
|---|---|---|---|
| Central Ministry | National | View national KPIs, approve inter-state corridor policies | National Dashboard |
| State Revenue Dept | State-scoped | Configure state workflow JSON, issue gazette notifications | State Dashboard |
| District LAO / Collector | District-scoped | Scrutinize proposals, declare awards, issue possession | District Dashboard |
| Land Requiring Body (NHAI) | Project-scoped | Create project, submit land proposals, track turnaround | Project Dashboard |
| Field Officer | Assigned Parcels | Mobile GPS parcel tagging, photo panchnama capture | Mobile PWA Interface |
| Finance Officer | State / District | Approve compensation payments, disburse funds via treasury | Compensation Module |
| R&R Officer | District / Project | Register displaced families, assign R&R housing/annuities | R&R Module |
Sheet 15 / 16 — Implementation Roadmap
Phased Delivery Schedule
Structured from SIH Prototype MVP to Full Production Deployment (PRD §45).
SIH Hackathon MVP
Auth + RBAC, Project creation, Configurable Workflow Engine, PostGIS GIS Parcel Tagging, 3-tier Compensation Ledger, R&R family tracking, Possession recording, and XGBoost AI Delay model.
State Pilot & OCR
Document OCR auto-form prefilling, SMS/Email SLA auto-escalation dispatch, Bhuvan live API connection, and Native Mobile App.
National Production
Full DILRMP ULPIN national integration, multi-region DR deployment, formal CERT-In security audit, and Citizen Transparency Portal.
Sheet 16 / 16 — SIH Live Presentation Walkthrough
12-Step Judge Presentation Script & Differentiators
Step-by-step demonstration flow proving complete end-to-end functionality during hackathon judging (PRD §41 & Competitive Advantage).
The Presentation Path
- Login as State Revenue Officer → Create Highway Project
- Upload Land Proposal + mandatory survey docs
- Digital Scrutiny: reject once with deliberate defect to prove resubmission loop
- GIS Parcel Tagging: draw highway alignment & tag survey numbers
- Workflow approval: watch proposal advance through state JSON chain
- Issue Section 11 Preliminary Gazette Notification
- Declare Award & compute compensation solatium
- Compensation: move status Assessed → Approved → Disbursed
- Register Affected & Displaced Families + assign housing package
- Record Parcel Possession with geo-tagged panchnama evidence photo
- Switch to National Dashboard: show live roll-up without manual re-seed
- Open AI Delay-Risk Panel: demonstrate SHAP explanation on delayed project
Why LAMS Wins
- Parcel Digital Twin: Every dollar and family record is anchored to GIS geometry, answering "which exact parcel is delaying the project."
- Config-Driven Workflows: Solves state legal fragmentation via JSON templates, not hardcoded state logic.
- Integrated GIS: Spatial parcel tagging is a mandatory workflow gate with SLAs, not an afterthought map view.
- Honest Data Story: Explicitly labels synthetic records (
is_synthetic=true) for full credibility. - Explainable AI: Uses XGBoost + SHAP to advise decision makers *why* a project is at risk.