About
Software that extends
human expertise.
Digital Extensions is a software studio building tools for professionals who work directly with complex source material — and for developers navigating an AI-first world. We believe the best software makes an expert faster and more certain, without ever taking the judgment out of their hands.
Our Philosophy
The expert stays in control. The software keeps the receipts.
A lot of modern software is built to decide for you. That is exactly the wrong posture for work where the reasoning has to hold up — a legal chronology, an expert opinion, a graded assessment. When the stakes are real, you need to be able to point at where every conclusion came from.
So we build the opposite kind of tool: local-first, transparent, and honest about provenance. Your files stay yours. AI earns its place by extending your understanding — never by concluding on your behalf. Every output traces back to the source it came from.
Precision & Provenance
Every assertion traceable to its origin. Every annotation tied to its exact source location — because in this work, ambiguity carries real cost.
Local-First & Transparent
Your data stays on your machine. Original files remain pristine. AI runs locally when it can, and reaches the cloud only under a policy you set — no hidden inference, no conclusions drawn on your behalf.
Expert-Driven
Interpretation belongs to the expert. The software supports careful reasoning — it does not replace it, automate it, or quietly introduce assumptions.
Who's Behind It
Paramedic first. Engineer second. Both show up in the software.

Digital Extensions was founded by Kent Merrell. He was a paramedic before he was an engineer — first an EMT with the volunteer fire department in Cave Junction, Oregon, then paramedicine at BYU-Idaho, hospital rotations at EIRMC, a summer at Grady, and two years running calls with North Country EMS near Mount St. Helens. Those were years spent writing the kind of timestamped record an attorney reads later, and they left a durable respect for records that can be traced, checked, and understood by someone who wasn't there.
Then roughly thirty years of enterprise software — healthcare claims and reporting systems at Ingenix / UnitedHealth Group, platform and documentation work for NIH/NIAID. Years on the charting side of clinical documentation, followed by years on the tooling side of it.
Those two halves meet in the sourced chronology: a medical-record chronology where every entry carries its exact source, so any reader can get from the event back to the supporting page without a hunt. The method comes first — it can be kept by hand in a document or a spreadsheet. Corpus Chronology exists to make the discipline easier to keep: gather the record set, read with the cite attached, mark the events that matter, see the shape of treatment, and export something that traces back.
The boundary is worth stating plainly. Kent is not a nurse and has not worked the legal side of a case. He builds the tools and teaches the provenance discipline; the nursing and legal-practice judgment stays with the professionals using them.
If you write in through the form below, you're reaching the person making the software — not a support queue.
Get in Touch
Questions, feedback, or a hard case?
Whether you're evaluating Corpus Review for a matter or curious about Corpus Chronology — send a note and we'll get back to you.
Working sessions and onboarding are arranged here too. There's no booking calendar to wrestle with: tell us roughly when you're free and we'll settle the time by email.