How toijam-ghanashyam/drishti works
This repository combines a cadastral land-record platform with separate conflict-clustering, boundary-consensus, and evidence-ledger services. The principal workflow is importing land data, analyzing spatial conflicts, and presenting records and review tools in a dashboard; the landing page describes confidence scoring, human review, and harmonized records. Source excerpts do not establish how the main API wires those stages together, so those links are omitted. The frontend also depicts NRSC/STAC synchronization, but its excerpt simulates the result. Several backend capabilities are represented only by the file tree.
Main entry points: App.jsx Dashboard router · orchestrator.py Resolution orchestrator · api.py Platform API · IngestionHub.jsx File upload
Components 25
Dashboard and review
- Dashboard router
frontend/src/App.jsx - Ingestion hub
frontend/src/pages/dashboard/IngestionPage.jsx - File upload
frontend/src/components/dashboard/IngestionHub.jsx - Map view
frontend/src/pages/dashboard/MapPage.jsx - Analytics
frontend/src/pages/dashboard/AnalyticsPage.jsx - Land records
frontend/src/pages/dashboard/RecordsPage.jsx - Conflict review
frontend/src/pages/dashboard/ConflictsPage.jsx
Spatial data processing
- Platform API
api.py - Shapefile ingestion
ingest.py - Spatial conflict engine
conflict_engine.py - Spatial database
Conflict analysis
- Clustering API
conflict-clustering-service/app.py - Conflict clustering
conflict-clustering-service/clustering_engine.py - Cause analysis
conflict-clustering-service/cause_analyzer.py
Boundary resolution
- Consensus adapter
boundary_consensus/adapter.py - Resolution orchestrator
boundary_consensus/consensus/orchestrator.py - Stakeholder agents
boundary_consensus/agents - Proposal auction
boundary_consensus/consensus/auction.py - Consensus scoring
boundary_consensus/consensus/game_theory.py
Evidence ledger
- Ledger API
spatial-evidence-ledger-backend/app.py - Ledger operations
spatial-evidence-ledger-backend/ledger.py - Commitment generation
spatial-evidence-ledger-backend/commitment.py - Proof utilities
spatial-evidence-ledger-zk/proof.py - Ledger and audit files
Other components
- Land-data user
Connections 19
- Land-data user → Dashboard router: uses
- Dashboard router → Ingestion hub: routes to
- Dashboard router → Map view: routes to
- Dashboard router → Analytics: routes to
- Dashboard router → Land records: routes to
- Dashboard router → Conflict review: routes to
- Ingestion hub → Platform API: requests audit logs
- File upload → Platform API: uploads files
- File upload → Platform API: requests conflict run
- Shapefile ingestion → Spatial database: loads plots
- Spatial conflict engine → Spatial database: reads and writes
- Clustering API → Conflict clustering: clusters conflicts
- Conflict clustering → Cause analysis: analyzes groups
- Consensus adapter → Resolution orchestrator: delegates resolution
- Resolution orchestrator → Stakeholder agents: requests proposals
- Resolution orchestrator → Proposal auction: selects winner
- Resolution orchestrator → Consensus scoring: scores proposals
- Ledger API → Ledger and audit files: reads and writes
- Ledger API → Commitment generation: generates commitment