step 1 — describe the site

Describe the site or the question

Type a rough brief in your own words. KBM extracts facts from it — it never invents any. Anything it can't find becomes a visible gap in the packet below.

step 2 — confirm the packet

The project packet — every fact carries its source

Green facts came from your brief. Blue facts KBM derived from official data. Amber facts are assumptions — confirm or correct them before relying on any result. Corrections become stated inputs only on the next live engine run.

No packet yet — describe the site above and press Extract facts.

Attach evidence

Upload actual local evidence files into KBM. Files are stored and classified by the backend; parser status and non-claim rules stay visible.

Source type

Note / reference

Files

Accepted: .pdf, .png, .jpg, .jpeg, .webp, .dxf, .dwg

Review evidence details — all candidate facts, diagnostics and confirmation queue

No evidence attached yet.

Kerala site screen — the questions that change everything

These sit outside KMBR/KPBR but can stop a permit outright. Most plots carry none of them — everything starts as “no known flag”; mark Suspected or Yes only where it applies.

What happens next

You build the packet

Fill what you know. Nothing more is needed to start.

KBM checks readiness

Shows what's missing and what can already run.

You choose a route

Preliminary feasibility, or just a rule question.

KBM runs the engine

Deterministic checks only. No noise, no guessing.

You get curated output

Clear answer, drawings, checks, and next steps.

Nothing is invented. Nothing is hidden. KBM only tells you what the rules and the data can honestly support.