It started with a personal question, not a professional one. I wanted to understand something specific about a place I cared about — how a decision had actually been made, what had actually changed, who was actually involved. Nothing exotic. The kind of question any resident, any voter, any neighbor might have.
I assumed it would take an evening. It took considerably longer than that.
The records existed. That part was true almost everywhere I looked. A government agency had published something. A court had filed something. A regulator had disclosed something. A local news archive had covered something related. But none of it was connected, none of it used the same identifiers, and none of it was built to be read as a single story. It was built to be published, not to be understood.
So I did what anyone with a technical background and too much curiosity does: I started pulling the pieces together myself. Spreadsheets. Downloaded datasets. Screenshots of public portals. Notes cross-referencing one document against another. It was slow, manual, and occasionally absurd — hours of work to confirm something that, in hindsight, should have taken minutes.
What kept me going wasn't the specific answer I was after. It was what I noticed while looking for it: this wasn't a one-time inconvenience. It was a structural gap. The same gap I'd been navigating professionally for years was sitting in plain sight in public data, available to anyone with the patience to go looking — which, in practice, meant almost no one went looking at all.
That realization sent me further down a path I hadn't expected: learning how people who actually do this kind of work for a living — investigators, researchers, analysts — approach public information when the goal is to reconstruct the full picture, not just read one document at a time.