# V1 source verification log

## 2026-10-06: Lucknow standard Bigha and Mana study Nali (dataset 0.7.0)

Added two VERIFIED records: 41 records, 22 explicitly selected conventions, 19 states. All three researched originals are archived with SHA-256 manifests.

- Uttar Pradesh: [Lucknow: A Gazetteer, Volume XXXVII](https://dspace.gipe.ac.in/xmlui/bitstream/handle/10973/37272/GIPE-017953.pdf?isAllowed=y&sequence=3), government-authored by H.R. Nevill, I.C.S., printed at the United Provinces Government Press, Allahabad, 1904; digitized original hosted by GIPE. Title/date visually checked on PDF p.1. Definition and scope visually checked on PDF p.41 / printed p.37: standard Bigha 3,025 square yards, a square of 165 feet. Lucknow tahsil is explicitly named; shorter customary Lath measurements and a smaller local Bigha in Malihabad/Mohanlalganj are distinguished. Use the standard scale only, with historical scope; do not infer current statewide usage or Biswa.
- Uttarakhand: [G.B. Pant Institute Annual Report 2005-2006](https://www.gbpihed.gov.in/PDF/Annual_Reports/AR2005-06.pdf), autonomous institute of the Ministry of Environment and Forests, Government of India. Scanned original authority/period visually checked on PDF pp.1,3. PDF p.95 / printed p.89 identifies Mana/Niti valleys in Chamoli. PDF p.96 / printed p.90, Table 18 crop-production note, states one Nali = 0.02 hectare / 200 square metres for Mana village. The source does not mark this approximate; the calculator conservatively marks it approximate because this is an agricultural-study scale rather than a surveyed cadastral definition. Preserve 200, not 200.6705664, and do not infer Mutthi/Bigha or statewide applicability.
- Excluded: UJALA training presentation [current academy index](https://ujala.uk.gov.in/document-category/uttarakhand-history-en/) links the recovered original `uttarakhand-ujala-land-guide.pdf`. PDF p.21 visually inspected: Nali around 200.6706 square metres / 0.049586785162 Acres is incompatible with 1350 square feet. Mutthi and Katha/subdivision wording do not resolve it. No value is repaired or used as a production factor; publication date unconfirmed.

Validation: Lucknow independent square-yard/foot and 5/8-Acre anchors; Mana study hectare anchor, approximation and locality checks; missing units rejected. All-record provenance, archive hashes and round trips pass. Expanded suite: 31 tests. Browser and bilingual QA cover 22 conventions, mobile source-link layout and offline conversion.

## 2026-10-06: Telangana Wargal acquisition (dataset 0.6.0)

Added one VERIFIED Gunta record: 39 records, 20 explicitly selected conventions, 17 states.

Original [District Collector, Siddipet proceedings hosted by the National Green Tribunal](https://www.greentribunal.gov.in/sites/default/files/news_updates/7922_0.pdf) archived as `telangana-wargal-compensation-2021.pdf` with SHA-256 manifest. Visually checked PDF p.136 / printed 135: Government of Telangana heading, Proc.No. E1/4105/2021, date 08.11.2021, Wargal Village and Mandal industrial park acquisition. Table row 2, Sy.No.845, pairs 5.0000 Acres with 200 Guntas, giving 40 Guntas per Acre. Rates of Rs.1,000,000/Acre and Rs.25,000/Gunta support the same relationship within the same source; they are not independent evidence.

Normalize the row's stated 200 Guntas = 5 Acres using the exact standard Acre. Do not interpret other extent entries such as 0.050 (paired with 5 Guntas) as decimal Acre amounts: this table also uses mixed Acre-Gunta notation. Preserve the explicit locality/date scope and warn users to enter an amount in one selected unit. No automatic statewide applicability, Cent/Decimal/Bigha factor or mixed-notation parser is inferred.

CAG evidence for Mansoorabad remains an archival follow-up, separate from this independently verified Wargal choice. Uttarakhand research found a Champawat project page with 97.8 Nali approximately 5 Acres, which is insufficient for an exact Nali definition; it remains pending.

Validation: original-row conversion and reverse anchor, 1 Gunta = 1,089 sq ft, locality and missing-unit checks; all-record provenance, archive checksums, round trips; bilingual mobile source links and offline conversion. Dataset suite: 29 tests.

## 2026-10-06: Bihar, Gujarat and Tripura (dataset 0.5.0)

Added three VERIFIED records: 38 records, 19 explicitly selected conventions, 16 states. All three use the already archived DoLR / CoE-LAM YASHADA Glossary of Revenue Terms hosted by LBSNAA. Its stable source ID and archive filename are retained; its title and scope now describe all reviewed state sections, including existing Punjab evidence. Publication date is unconfirmed.

| New choice | Original page visually checked | Definition and boundary |
| --- | --- | --- |
| Bihar Decimal | PDF p.53 / printed p.37, sections 9.1 and 9.2 | 100 Decimals per Acre, also expressed as 1/100 Acre. Approximate 40.46 sq m figure is retained separately and excluded from normalization. Katha/Dhur/Bigha and Dismil naming are not inferred. |
| Gujarat Guntha | PDF pp.93-94 / printed pp.77-78, section 11 | Named 1/40 Acre scale. Explicit warning that local definitions may vary remains in dataset and bilingual UI. No automatic district applicability or Bigha/Vigha factor. Adjacent approximate Acre/Hectare figure is excluded. |
| Tripura Decimal | PDF p.291 / printed p.276, section 9.5.2 | 1/100 Acre in the Tripura RoR glossary. No inferred Kani/Ganda definition. MDDS p.140's incompatible Hectare/Acre statement is recorded as an excluded discrepancy; it is not relabelled as Decimal. |

Fresh research also found a Manipur Transport 2023-24 report pricing a Sangam as 0.62 Acre, a 1961 census table showing 0.63 Acre, and a state climate newsletter reporting 3 Sangams as 1.87 Acres. These appear rounded and do not justify an exact factor; Manipur remains research-only. A CAG official alternate host was tried for Telangana; it was also inaccessible. Remaining-state research is recorded in the coverage checklist without inventing factors.

Validation: exact Acre subdivision anchors, Gujarat square-yard/foot anchors and missing-unit rejection; all-record provenance, archive hashes and round trips; bilingual mobile source links and offline arithmetic. The expanded suite has 28 dataset tests.

## 2026-10-06: Odisha and Jharkhand (dataset 0.4.0)

Added two VERIFIED Decimal records in explicitly selected settlement/survey conventions: 35 records, 16 conventions, 13 states. Archived originals and SHA-256 checksums are in the evidence manifest.

- Odisha: Revenue & Disaster Management Department, Orissa Government Land Settlement (Amendment) Rules, notification dated 11 February 2010. Original PDF p.4, Schedule V clause 6(f), visually inspected: Decimal is 1/100 Acre. Scope is this Schedule's homestead land settlement definition, not current legal eligibility. The definition is independently consistent with p.3's four Decimals = 1/25 Acre and ten Decimals = 1/10 Acre.
- Jharkhand: JSLPS Baseline Survey Report on Livelihood in Jharkhand, 2015, prepared by GfK Mode and hosted on the state Forest Department site. Original p.38 Table 3.1.3 note 2 visually inspected: 100 Decimals per Acre. Title/authority checked at pp.1-2; sample scope checked at p.18: 128 villages across 16 districts. Retain the survey convention, without inferring statewide cadastral applicability, Dismil naming or Katha/Dhur factors.
- Telangana: CAG official indexed Report No.4 of 2022 printed p.31 footnote 46 identifies 40 Guntas per Acre at Mansoorabad, Saroornagar Mandal. Original full report and Chapter II downloads failed. Keep this lead research-only until original inspection; no production record added.

Normalization uses the exact canonical Acre and the explicit hundredth subdivision; 1 Decimal = 435.6 sq ft. Validation covers provenance, archive hashes, exact 100-Decimal Acre anchors, unsupported-unit rejection, all-record round trips, bilingual source links, mobile layout and offline operation.

## 2026-10-06: Andhra Pradesh, Assam and West Bengal (dataset 0.3.0)

Added six VERIFIED records in three explicitly selected conventions, bringing the dataset to 33 records, 14 conventions and 11 states. Earlier sections describe previous milestones; the remaining-state queue has been narrowed accordingly.

| Added choice | Relationship and evidence | Publication boundary |
| --- | --- | --- |
| Andhra Pradesh, MDDS 2011 | Original archived PDF p.140 visually reviewed: 40 Guntas per Acre, naming Andhra Pradesh alongside Karnataka. | Source-era state convention before bifurcation; no current district or Telangana inference. Cent/Kuncham remain research-only. Rounded metric Gunta values are not anchors. |
| Assam, AIRBMP 2022 | Original November 2022 Resettlement Policy Framework p.28, section 7.2, visually reviewed: Bigha 14,400 sq ft; Katha 2,880 sq ft; Lecha 144 sq ft. Project scope checked at p.7. | Named Brahmaputra subbasin project convention, not every Assam or Barak Valley record. MDDS p.140 has incompatible Bigha/Katha entries, preserved and excluded. |
| West Bengal, WRI&DD 2018 | Official indexed schedule conversion table: 60.50 Cottahs and 3.025 Bighas per Acre. Independently corroborated Katha 720 sq ft in archived Supreme Court order, 7 May 2025, SLP(C) 13494/2024, pp.1–2 visually reviewed. | Named engineering schedule convention, not a universal cadastral definition. Court observation concerns an Uttar Dinajpur dispute and does not independently define Bigha. Original schedule download timed out; indexed-source status is disclosed. |

The WRI&DD ratios yield Katha 720 sq ft and Bigha 14,400 sq ft using the canonical Acre; they independently imply 20 Kathas per Bigha. The adjacent indexed Acre figures/labels (4048.32 sq m and 43560 sq.m.) disagree with the canonical definition and are retained in discrepancies.json. No erroneous metric entry is silently corrected or used as a factor. Assam and West Bengal share unit identities but use separate convention factors: their Kathas are 2,880 and 720 sq ft respectively.

New originals are archived with SHA-256 checksums in the evidence manifest; the failed West Bengal schedule download is also recorded. No TLS validation was disabled. See [new-state follow-ups](../check-later/new-state-evidence.md) for archival and broader geographic checks. Exact precision here describes the documented relationship, not legal certification of an individual parcel.

Validation: all-record source chains, arithmetic, scopes and archive checksums pass; 26 dataset tests pass, including independent anchors, missing-unit rejection and round trips. Browser checks cover the new choices, state/convention gating, mobile overflow, source details and offline arithmetic.


Review date: 2026-10-06 (Asia/Calcutta). Dataset version: 0.1.0.

## Inputs and review method

The existing `initial.pdf` supplied the candidate matrix and primary-source leads. Its confidence labels were not imported automatically. The rollout's six V1 scopes took precedence over the report's broader launch suggestions. The report mentions CSV/TSV/XLSX/JSON downloads, but those artifacts are not present locally; this milestone reconstructs the V1 evidence rather than claiming to import the missing machine-readable matrix.

The audit reopened original government material where accessible, checked relevant PDF pages visually, separated relationship definitions from rounded equivalents, and recalculated normalized outputs. Official indexed page text was used transparently when direct retrieval failed. Evidence for unit usage alone was not treated as evidence of a conversion factor.

## Production decisions

| Scope | Units | Primary evidence reviewed | Decision and boundary |
| --- | --- | --- | --- |
| Maharashtra documented survey | Guntha | Jalgaon Survey paragraph and Poona Chapter 15, LAND RECORDS / Maps, from indexed official pages | VERIFIED for the named Pune/Jalgaon survey convention. No automatic statewide or contemporary cadastral inference. Publication dates remain unknown. |
| Karnataka named Acre/Gunta convention | Gunta/Guntha | Original MDDS PDF p.140, Table 1.3; matching API Setu table | VERIFIED for the explicitly named convention. Normalize its subdivision relationship, not the adjacent rounded metric figures. |
| Kerala named Acre/Cent convention | Cent | Same original MDDS table, explicitly naming Kerala | VERIFIED convention; not a claim about every historical land measure. |
| Tamil Nadu named Acre/Cent convention | Cent | Same original MDDS table, explicitly naming Tamil Nadu | VERIFIED convention; no inference about Ground, Kuzhi or other excluded units. |
| Haryana post-Bandobust | Kanal, Marla, Sarsaai | Original MDDS PDF p.141, After Bandobust section; matching API Setu table | VERIFIED for the selected 66-inch-Karam / Ghuman-Acre system. The dimensional and subdivision chains independently agree. Earlier settlement systems stay separate. |
| Rajasthan, Didwana | Bigha, Biswa | March 2020 draft Didwana wastewater due diligence report; PDF pp.47,51,55, printed pp.41,45,49 | VERIFIED project-documented definition; metric values remain approximate. Do not extrapolate to Rajasthan or all Nagaur. Source-era district names are retained without asserting current boundaries. |

### Source links and archival status

- [MDDS Demographic v1.1, 16 November 2011](https://egovstandards.gov.in/sites/default/files/MDDS_Domain_Document_structure_sample.pdf): original PDF archived. Reviewed printed/PDF pp.140-141, including the separate settlement headings. [API Setu Annexure](https://docs.apisetu.gov.in/document-central/mdds/Annexure.html): HTML archived and checked against the original. These are two presentations of the same evidence, not independent corroboration.
- [Jalgaon Gazetteer](https://gazetteers.maharashtra.gov.in/cultural.maharashtra.gov.in/english/gazetteer/JALGAON/rev_dep.html) and [Poona Gazetteer, Chapter 15](https://gazetteers.maharashtra.gov.in/cultural.maharashtra.gov.in/english/gazetteer/Poona/PART%20V/Chap%20%2815%29/Department%20of%20Land%20Records.htm): official indexed text establishes the survey relationship and district context. Direct HTTPS and redirected HTTP retrieval failed because the server certificate is expired. No full original HTML archive is claimed. Sources record `indexed_primary_page` as the verification method; archival recovery is queued.
- [Didwana report](https://lsg.urban.rajasthan.gov.in/content/dam/raj/udh/organizations/ruidp/ShortResettlementpdf/SRP-PH-IV/LD%2019%20Didwana%20DDR%20%2823%20March%202020%29%20clean-save%20as.pdf): original 59-page PDF archived using Windows certificate trust after Python certificate validation failed. Relevant tables and footnotes visually inspected. The cover identifies a draft for consultation prepared for ADB by the Rajasthan project corporation. Three footnotes agree. Parcel totals reproduce within half a square metre after source rounding. The Pathano Ka Baad schedule corroborates the report's convention; it does not enlarge the production locality allowlist.
- [NIST Handbook 44 (2026), Appendix C](https://www.nist.gov/system/files/documents/2025/12/30/appc-26-HB44-20251222.pdf): original PDF archived; PDF pp.9 and 23 visually inspected. Provides canonical international length/area definitions. These definitions normalize outputs; they do not establish where a traditional Indian convention applies.

The evidence manifest preserves successful file checksums and failed download outcomes. No TLS verification was disabled. A web-search index may contain older page text; Maharashtra's VERIFIED status applies to its documented historical survey definition, not a claim that the live site was freshly downloaded or that the definition is universally current.

## Discrepancies and deferred evidence

The MDDS table's rounded Cent/Gunta equivalents are retained in `data/discrepancies.json`, alongside an apparent Acre/square-yard error. They are not silently corrected or used as normalization anchors. Validating the explicit source relationships does not endorse every entry in that table.

A [Yavatmal gazetteer passage](https://www.gazetteers.maharashtra.gov.in/cultural.maharashtra.gov.in/english/gazetteer/YAVATMAL/bank_wt_measures.html) describes a historical Guntha relationship differing from the selected survey convention. Its historical and geographic applicability needs further research; it is preserved as a lead and reinforces the Maharashtra scope warning.

A [2014 Karnataka CAG audit](https://cag.gov.in/webroot/uploads/download_audit_report/2014/Karnataka_Report_3_2014_Chap_3.pdf), printed p.111 footnote 30, provides an indexed corroborating relationship. The original download timed out, so it is not counted as archived/fully inspected production evidence. The V1 record instead rests on the accessible MDDS original.

Delhi, Assam, West Bengal, Punjab, Bihar, Uttar Pradesh, Uttarakhand, Jharkhand, Andhra Pradesh, other Rajasthan Jarib systems and earlier Haryana settlements remain in the research queue. Except for the specifically identified newly inspected passages, queued claims retain their status as initial-report leads; this audit does not claim fresh verification of every deferred region.

## Publication gate and validation

Every production unit record identifies its unit, explicit convention, geographic/historical scope, source relationship, source authority, direct/derived origin, precision, and warnings about alternative applicability. Relationship chains resolve through stable IDs. Approximate Bigha precision propagates to Biswa. No universal traditional factor is stored in the unit catalog.

The validator rejects absent sources/scope, duplicate IDs, broken references, nonpositive/nonfinite or implausible factors, conflicting identical scopes without declarations, unresolved production conflicts, non-VERIFIED production records, arithmetic drift, broken dependencies and approximation loss. Archived source checksums are verified. It never rewrites source values.

Tests cover all nine production records, five standard outputs and nine input values, plus independent known answers and negative cases. The round-trip audit uses exact rational arithmetic; JSON recurring-output serialization is checked at relative/absolute tolerance `1e-35`. That tolerance concerns storage, not the real-world accuracy of approximate source definitions.

The data milestone is ready for calculator development within these boundaries. This is not a live-link or public-site QA sign-off. No UI, SEO pages, search-engine submission or deployment was performed.


## 2026-10-06: Himachal Pradesh and Punjab (dataset 0.2.0)

Added 18 VERIFIED records in five explicit conventions. Total: 27 records, 11 conventions, eight states.

Himachal's original 110-page Appendix XIX was recovered through the Revenue Department's current Manuals > H.P. Land Records, 1992 > Appendices index. Old WriteReadData links return 404. The new official download URL and the full PDF checksum are in the manifest. Visually reviewed PDF pp.1,15,27,53,84 (printed 759,773,785,811,842).

| Convention | Named scope in original table | Definitions used (square metres) |
| --- | --- | --- |
| Part A, 54-inch Karam | Kinnaur, Bilaspur, parts of Shimla and Solan | Bigha 752.514624; Biswa 37.6257312; Biswansi 1.88128656 |
| Part B, 56-inch Karam | Mandi, Kullu, Chamba, Lahaul & Spiti | Bigha 809.288704; Biswa 40.4644352; Biswansi 2.02322176 |
| Part C, 57.5-inch Karam | Una, Kangra, Hamirpur using this scale | Sarsahi 2.13306025; Marla 19.19754225; Kanal 383.950845; Ghumao 3071.60676 |
| Part D, 66-inch Karam | Parts of Solan, Una, Kangra, Hamirpur using this scale | Sarsahi 2.81031696; Marla 25.29285264; Kanal 505.8570528; Ghumao 4046.8564224 |

These are traditional settlement conventions, not district-wide current defaults. Modern metric records may use hectares directly. Part B's 968 sq yd label and Part C's 3674 sq yd label are rounded; the precise metric definitions agree with the square-Karam subdivisions. Both are preserved in discrepancies.json. The 57.157-inch Part E system remains deferred pending rounding and locality review.

Punjab: reviewed the indexed primary PUDA document, **Different scales used in the State of Punjab for the measurement of land**, sections B and C(i). It distinguishes the standard consolidated 66-inch scale from local 60, 57.5 and 54-inch scales. Only the standard system is promoted here. Normalize the explicit 66-inch square-Karam, nine-Sarsahi Marla, twenty-Marla Kanal, and eight-Kanal Acre relationships; do not use rounded decimal yard entries as anchors. The official host timed out on HTTPS and HTTP. No TLS checks were disabled; a separate alternate domain returned HTML and was rejected as evidence. Original archival is a tracked follow-up, and the UI discloses indexed-primary review.

The Department of Land Resources / CoE-LAM YASHADA **Glossary of Revenue Terms**, hosted by LBSNAA, is archived in full (445 pages). Visually reviewed Punjab PDF p.225 / printed 210: Murabba equals 25 acres. Publication date is unconfirmed and is not inferred from the URL timestamp. The Himachal section recognizes modern metric units but does not supply traditional factors. Kila field numbers do not establish an area factor, so Killa is not inferred.

Validation: archive checksums, arithmetic and scope checks pass; 25 dataset tests pass, including new independent anchors and all-record round trips. Browser QA covers all 11 conventions, offline operation, explicit state/convention gating, source details, both ad placeholders and mobile overflow at 320/390 pixels.


## 2026-10-06: Manipur historical valley enumeration (dataset 0.8.0)

The original Census of India 1961, Volume XXII, Manipur, Part I-A report is archived with a SHA-256 checksum. The title page gives publication year 1966. Visually inspected PDF p.21 / printed p.8, section 1.14 Household Schedules: the enumerator conversion table explicitly gives Sangam 0.63 Acre, Lourak 1.25 Acres and Pari 2.50 Acres. The narrative limits these local measures to the valley and distinguishes hill seed-rate measures.

All three factors are approximate. The table reports 3 Sangams as 1.88 Acres, while multiplying its rounded single-unit entry yields 1.89. Compound entries are preserved in the discrepancy record, excluded as normalization anchors, and no exact 0.625 factor is inferred. Sangam results use at most two significant digits; Lourak/Pari use three. This is a historical enumeration choice, not evidence of current cadastral use or hill applicability.

The official indexed ICAR advisory dated 27 October 2017 gives 1 Acre (1.6 Sangam), but kiran.nic.in currently has no A record in local/public DNS and the original could not be archived or visually inspected. Retained as a research lead; no production factor is based on it. Rounded recent procurement statements remain leads.

Validation: 44 records and 23 conventions pass provenance, arithmetic, scope and checksum checks; 32 dataset tests and English/Hindi mobile/offline browser QA pass.


## 2026-10-06: Seven standard-unit states (dataset 0.9.0)

NIC SDU Pune's NGDRS Gap Analysis was downloaded from the official NGDRS site and archived with a SHA-256 checksum. Visually inspected title/amendment pages and PDF p.61 question 7. The amendment log dates v1.0 first draft to 15 April 2016. The state responses document metre/foot usage for Arunachal Pradesh, Meghalaya and Mizoram; metre/foot/hectare/acre for Chhattisgarh; hectare/metre for Madhya Pradesh; foot for Sikkim. The existing DoLR glossary, PDF p.86 / printed p.70, visually confirms Goa's metric record units.

These seven choices use mode=standard_units and contain no traditional conversion records. Source-side usage entries and convention-side references retain the state, documented unit IDs and locator. Numeric factors remain canonical NIST definitions. All five supported standard units can be converted; evidence of reported usage is not a statement that each output is used in every state's records or that a state has no customary systems. Goa Are and mixed Hectare-Are-square-metre notation are excluded from this release.

The validator rejects local records in standard mode, undocumented defaults, mismatched usage evidence, unknown modes and unresolved choices. Existing traditional-record provenance checks remain active. The UI displays usage and definition evidence separately, chooses a documented default input, and keeps explicit state/choice gating.

Validation: 44 local records, 23 local conventions and seven standard choices; 27 states. All 33 dataset tests, all 30-choice browser checks and Hindi/English mobile/offline checks pass. Source links, standard-mode swap/copy, page locators and mobile overflow checked. Mobile Goa and NGDRS-source layouts visually inspected. Nagaland remains pending.


## 2026-10-06: Nagaland and all-state availability (dataset 0.10.0)

Visually inspected the original archived NIC NGDRS Gap Analysis, PDF p.105, List of Land Measurement Units, row 16. It explicitly lists Nagaland square-metre and square-foot usage. Added a standard-unit choice using that row's state/unit/locator evidence, a square-metre default and the existing independent NIST definitions. The NGDRS p.61 response list does not include Nagaland; its p.105 appendix supplies this evidence. No local factor or exclusive/current statewide system is inferred.

Dataset now has 44 local records, 23 local conventions and eight standard choices across all 28 states. This completes state availability, not all district/customary definitions; union territories and Goa Are/mixed notation remain separate expansions.

Validation: 33 dataset tests pass, including canonical arithmetic and rejected traditional factors in standard mode. English browser QA covers all 31 choices and Hindi/English QA covers Nagaland's default, p.105 citation, saved original, mobile layout, swap/copy and offline language preservation. Nagaland mobile screenshot visually inspected; archive checksums and git diff --check pass.