Law school teaches law. It does not teach the building. A junior's first filing at the High Court is not a legal problem. It is a procedural one. Which counter. Which floor. How many copies. Which stamp and for how much. What an objection slip actually means. The answers exist, but they sit with clerks and seniors, and you learn them by getting them wrong first.
LexKompass covers that gap. It maps the procedure, the place and the practice together, arranged as* F → C → D → N. Filing, Compliance, Disposal, No Repeat.*
It is not an AI lawyer. It gives no legal advice and no strategy. It tells you where to go, what to carry and what happens next. That notice sits on every screen.
Two things in it matter to me.
Rule and practice are kept separate. Every step is marked either as enforceable, meaning statute, High Court Rules or a practice direction, or as what actually happens at the counter. The ₹50 Advocate Welfare Fund stamp on the vakalatnama is a rule. Avoiding the day after a long weekend is practice. Merging the two is how a procedural app starts giving legal advice without meaning to.
Verified and draft are stated openly. Every location, route and step carries a status and a date. Where something has not been confirmed on site, it says so instead of guessing. A gap costs a junior nothing. A confident wrong answer costs him half a day at the wrong counter. The court map is switched off at the moment for that reason. The survey is not complete, so it says coming soon rather than showing a plan that looks right and is not.
Built on the High Court of Karnataka, Principal Bench, Attara Kacheri, Bengaluru. The structure is court agnostic. All content is JSON. Adding another High Court is a folder of data, not a rewrite.
Offline first. Signal inside the corridors is poor and phones are restricted, so every page is prerendered, nothing loads at runtime, and nothing typed into the app leaves the device.