Skip to main content
Kevin M. Miller

Engineering · Systems · Judgment

About

I build and diagnose software systems where context matters.

My work combines engineering leadership, architecture, diagnostics, modernization, AI, security, and evidence-based decision-making.

Practice

The recurring problem is not technology. It is understanding the system well enough to change it safely.

Over more than 25 years, I have led engineering organizations, modernized enterprise platforms, built cloud and AI systems, and worked through environments where legacy software, organizational incentives, security constraints, and incomplete evidence all interact.

I approach difficult technical work diagnostically rather than ideologically. The first job is to establish what is actually happening, which assumptions are doing hidden work, what evidence supports the current explanation, and which decisions remain reversible.

That approach now shows up through Echelon Foundry and the systems around it: Ordo for explicit state and legal transitions, Praxis for governed work and evidence, Forma for presentation, Limen for browser boundaries, and related assurance and diagnostic systems.

I also write and speak about engineering judgment, failure patterns, modernization, AI adoption, and decision-making under constraint.

Operating pattern

Evidence first. Explicit constraints. Reversible moves when uncertainty is high.

  1. 01

    Diagnose

    Separate symptoms from mechanisms

    Collect enough evidence to explain why the system behaves as it does before prescribing a rewrite, reorg, or new tool.

    Writing

  2. 02

    Constrain

    Make legal behavior explicit

    Use state, types, boundaries, and governance to eliminate failure modes rather than relying on people to remember rules.

    Work

  3. 03

    Verify

    Make important claims inspectable

    Treat tests, provenance, diagnostics, and communication as evidence about the system, not ceremonial paperwork around it.

    Contact