Answers a clerk’s typed or spoken question on the M.P. Bhumi Vikas Rules in English or Hindi with the rule number and quoted text, plus a 3D view of the plot.
The problem
A building-permission clerk at Bhopal Municipal Corporation has to answer people's questions about the 108-page M.P. Bhumi Vikas Rules, 2012 within a minute. This tool gives a correct answer with the rule number to show the citizen, plus a 3D view of the plot. That was Track 1 of Bhopal Impact Lab 2026.
How it works
Bhumi Rule checker lets a Bhopal Municipal Corporation building-permission clerk get answers from the M.P. Bhumi Vikas Rules, 2012 in seconds instead of searching a 108-page rulebook.
The clerk can type or speak a question in English or Hindi, for example "My plot is 200 sq m on a 9 m road. What front setback, how many floors, what fee?" The tool answers in the same language. Each answer gives the rule number, the exact quoted rule text and an "Open Document" link to the source page. If the rules don't cover the question, it plainly says "not found" instead of guessing. Each answer also comes with a 3D view of the plot and building showing the setbacks and height limits. In the Draw plot tab, an architect or citizen can sketch their own layout and check it against the rules before submitting plans.
Why it can be trusted: the AI model never produces a number. Every number (setbacks, FAR, fees, heights) comes from deterministic Rust code that parses the rule tables. The model (Cerebras inference) does only two things: it understands the question and it writes the answer. Without an API key, the tool still runs on its deterministic core. It is tested against the official sample questions and 25 example scenarios. It is built in Rust and is open source, ready to hand to MPSeDC.
How Claude was used
Claude Code was our main developer for the whole build, working in the terminal. 7 of our 12 commits are co-authored by Claude. We used it to:
- read the problem statement and the 105 split rules, then design the "grounding rule": the AI never produces a number, code does.
- write the Rust backend: rule retrieval, table parsing for setbacks, FAR and fees, and the English/Hindi question parsing.
- build the web UI: the 3D plot viewer, the Draw plot rule checker, the Document viewer with "Open Document" links on every citation, and voice input.
- write and run tests against the official sample questions and 25 example scenarios, then fix failures until they passed.
- polish the UI and handle follow-up changes, like answering in the language the question was asked in, and renaming the project.
Team
Atalix