Technical discipline, grounded in practical work.

My work centers on evidence-conscious systems: software that keeps source material distinguishable from interpretation, makes process visible, and gives people a better way to review how an output was produced.

What shaped the work

I did not arrive at systems design through a single, tidy job title. Hands-on trades, hospitality, operations, and software each taught the same lesson from a different angle: abstractions only matter when they hold up under actual use.

That background influences how I build. I value a clear chain from source to decision, work that explains itself, and choices that can be checked instead of merely trusted.

What I write and think about

• Original records, derivatives, annotations, and summaries as distinct layers.
• Chronology as an aid to review rather than a substitute for judgment.
• Public claims that match what is actually available.
• Provenance, accountability, and a clear path back as practical safeguards.
• The practical overlap between software architecture and skilled trades.

Boundaries matter

This is a public profile. Private work and private records stay private. Evident ICU remains in private beta; it does not provide legal advice or guarantee admissibility, authenticity, or outcomes.