How toijam-ghanashyam/pvt works
This repository is a cadastral land-record platform: users ingest geospatial sources, reconcile spatial data and detect conflicts, then inspect results for review and record harmonization. The frontend exposes ingestion, map, analytics, records, and conflict views. The tree also shows separate root-cause clustering, multi-agent boundary consensus, and evidence-ledger/commitment subsystems. Source excerpts confirm selected ingestion, conflict-engine, clustering, ledger, and consensus behavior; the README is empty, and unsampled integration wiring is omitted.
Main entry points: App.jsx Web app routing · api.py Backend API · orchestrator.py Consensus orchestrator · app.py Evidence ledger API
Components 24
User interface
- Web app routing
frontend/src/App.jsx - Ingestion page
frontend/src/pages/dashboard/IngestionPage.jsx - Upload and run controls
frontend/src/components/dashboard/IngestionHub.jsx - Map view
frontend/src/pages/dashboard/MapPage.jsx - Land records
frontend/src/pages/dashboard/RecordsPage.jsx - Conflict review
frontend/src/pages/dashboard/ConflictsPage.jsx - Analytics
frontend/src/pages/dashboard/AnalyticsPage.jsx
Spatial processing
- Backend API
api.py - Spatial ingestion
ingest.py - PostGIS records
- Spatial conflict engine
conflict_engine.py
Conflict resolution
- Clustering service API
conflict-clustering-service/app.py - Root-cause clustering
conflict-clustering-service/clustering_engine.py - Cause analysis
conflict-clustering-service/cause_analyzer.py - Consensus orchestrator
boundary_consensus/consensus/orchestrator.py - Proposal auction
boundary_consensus/consensus/auction.py - Consensus payoffs
boundary_consensus/consensus/game_theory.py - Stakeholder agents
boundary_consensus/agents
Evidence and audit
- Evidence ledger API
spatial-evidence-ledger-backend/app.py - Parcel ledger files
spatial-evidence-ledger-backend/ledger.py - Commitment logic
spatial-evidence-ledger-backend/commitment.py - ZK proof module
spatial-evidence-ledger-zk/proof.py - Audit events
Other components
- Land-record user
Connections 20
- Land-record user → Web app routing: uses
- Web app routing → Ingestion page: routes to
- Web app routing → Map view: routes to
- Web app routing → Land records: routes to
- Web app routing → Conflict review: routes to
- Web app routing → Analytics: routes to
- Ingestion page → Backend API: fetches audit logs
- Upload and run controls → Backend API: uploads and dispatches
- Backend API → Spatial ingestion: dispatches ingestion
- Spatial ingestion → PostGIS records: writes plots
- Backend API → Spatial conflict engine: dispatches analysis
- Spatial conflict engine → PostGIS records: reads and writes
- Clustering service API → Root-cause clustering: clusters conflicts
- Root-cause clustering → Cause analysis: analyzes clusters
- Consensus orchestrator → Stakeholder agents: requests proposals
- Consensus orchestrator → Proposal auction: selects winner
- Consensus orchestrator → Consensus payoffs: evaluates consensus
- Evidence ledger API → Parcel ledger files: reads and updates
- Evidence ledger API → Commitment logic: generates commitment
- Evidence ledger API → Audit events: records events