Lead with being a scientist.
Not as background color — as the qualification itself. Below: who I am, how I work, and the research the practice rests on.
→ /assets/sean.jpg (4:5)
I'm a scientist. Scientific training is training in a specific thing: taking a system you didn't build, that nobody can fully inspect, and determining what it is actually doing rather than what it was meant to do.
That is exactly the problem an enterprise AI system presents. I come at it from the outside, with no stake in the answer being reassuring.
Two things this buys that a delivery vendor cannot claim. Classification — putting a system into a category whose behavior is already understood, so you can reason about your own system correctly. And independence — which is the whole premise of an audit. A vendor grading its own work is not an audit; an outside read with nothing to sell you is.
What Kedion is.
Kedion is an independent scientific perspective on AI in the enterprise, and the contracting entity behind this work — the name that goes on the statement of work, the rate card, the invoice, and the products. The practice is one person, and that is the asset, not something to hide.
So there is no "team," no "our engineers," no fabricated staff. When you engage Kedion, you get me — first person, first hand. Code review is the deepest expression of the practice, not the definition of it: the same judgment applies to a boardroom briefing, a roadmap, or a production system.
Down into the mess, then up into a category.
I come into a situation, trace the actual chain of events, and identify the step that is the bottleneck. Then I lift that specific problem into a general class of system whose properties are already known — so the organization can reason about their own system correctly and fix it with known tools.
That last move — down into the mess, then up into a category executives can act on — is what the whole practice turns on. The worked diagnosis shows it end to end.
Developed in the open.
The idea underneath the practice — that structure is the right level at which to understand complex systems — is something I develop in the open and publish with the same rigor I bring to a review. A framework is supposed to defend itself; putting it on arXiv is how it earns the right to be used on your system.
Writing lives on my personal site, not here — this site stays focused on the practice. Follow the research and the essays at sean-mcclure.com.