DLIMS started as a question: why does a driver's record still depend on which counter happens to have the file that day?
DLIMS doesn't ask a transport authority to change how issuance or verification work. It asks them to record the same fields — name, license number, class, dates, status — in one place that every authorized counter can read and write to. The workflow stays familiar. What changes is that the record no longer disappears into a drawer.
The project began as an independent build — one developer, one district's worth of process to study, and a decision to model the software around the physical card rather than an abstract database schema. That constraint is still the core design principle today.
"I build by working closely with AI tools to move fast without a large team — but every decision in DLIMS, from the field names to the access rules, comes from actually studying how a license counter operates. The goal isn't a clever system. It's a record that's still correct five years from now."
A working DLIMS register, built and tested against realistic sample data for a single district's counters.
Partnering with one transport authority to run DLIMS alongside the existing paper process, measuring lookup time and duplicate-record reduction.
Extending the shared register across districts, with inter-district transfer and a unified audit trail from day one.