This section is not a biography. It's an account — told in chapters — of the questions, the search, and the observation that led to building ALKARTIS. It starts where ALKARTIS itself started: with a letter.
That letter is reproduced below exactly as it was written. Every chapter after it goes deeper into the story behind it — before ALKARTIS, the search that came before it, and the beliefs that shaped what it became.
I did not create ALKARTIS because information was unavailable. I created it because information was everywhere — and understanding was still difficult to reach.
I have worked in environments surrounded by systems, documents, dashboards, databases, reports, maps, meetings, and subject-matter experts. I have watched smart and committed people spend days or weeks answering questions that sounded simple when they were first asked.
The problem was rarely that nothing had been recorded. The problem was that each system held only part of the story. One application knew what was submitted. Another knew what was approved. A document explained the policy. A map showed the location. A spreadsheet tracked an exception. A person understood why the process worked differently than the written instructions suggested. The answer lived somewhere between all of them.
This is not only a government problem. It exists inside companies, universities, hospitals, financial institutions, and nearly every organization that has accumulated years of technology and information. But public data makes the contradiction especially visible. We can publish millions of records and still leave people unable to answer basic questions about the places where they live, work, invest, build, vote, or raise a family.
We have treated access as though it were the same as understanding. It is not.
A CSV file is access. An API is access. A searchable portal is access. A dashboard is access. Each can be valuable. None guarantees that a person understands what happened, what is happening, why it matters, what may happen next, or what action makes sense.
Artificial intelligence changes what is possible, but it does not eliminate the responsibility to build trustworthy systems. A model cannot compensate for disconnected sources, unclear definitions, missing context, weak governance, or conclusions that cannot be explained. That is why ALKARTIS begins before the model and continues after the visualization.
We connect the records. We establish context. We identify patterns. We explain significance. We show the evidence. We help a person reach a decision.
I believe the next important category will not be defined by who publishes the most information or adds AI to the most interfaces. It will be defined by who can turn fragmented information into intelligence people trust. ALKARTIS is being built for that purpose.
For now, I want the work to lead. The products, the principles, and the problem deserve attention before the person behind them does. There will be a time to share more of the story. Until then, begin with the idea:
We do not have an information problem. We have an understanding problem.
That's where ALKARTIS started publicly. The rest of this section goes back further — to what came before it, and what led here.