Madison Towriss
AI orchestration architect with a 12-year product design background.
Currently building: a PK/PD physics engine for mRNA-LNP therapeutics, an AI patient portal in the ONC eHignite Challenge, and AI-augmented governance for a multi-brand design system at Group 1001.
◆ Open to senior IC and staff roles at AI infrastructure companies
I build the systems behind the product.
and the orchestration behind the systems.
Three systems, one discipline: deciding what the user controls, what the engineer guarantees, and what the model is allowed to do. The work below shows what that looks like in therapeutics modeling, healthcare AI, and design system governance.
── live · PK/PD compartment topology
110 states / 22 sources
Selected systems
2024 → now
mRNA PK/PD Engine
Systems architect · research mode
A physics simulator that models how an mRNA drug moves through the human body. 13 organs today, on the way to 81. Researchers can see what affects the drug at each step and target binding rationally. 110-state ODE system, 22+ source papers, pre-validation. In conversation with universities.
- Python
- SciPy
- ODE / PBPK
- Research mode
- Claude orchestration
Multi-brand Design System
Lead designer · Group 1001
A token-and-composition system spanning multiple insurance brands at Group 1001. Three-tier token architecture, design-to-production pipeline hooked into the front-end repo, and a scoped-skill AI review loop (SkillsForge) that compressed months of human review into minutes.
- Storybook
- Figma + Code Connect
- AI orchestration
- Governance
- Multi-brand
eHignite
Lead designer · competition entry
A unified patient portal that pulls fragmented EHI exports from every provider into one place, and uses AI to translate clinical reports into something patients can actually read. Phase 1 of the ONC eHignite Challenge, awaiting judge review.
- Next.js 16
- React 19
- EHI / FHIR
- AI sourced chat
- Healthcare
Earlier product design
Senior product designer · Group 1001 / Delaware Life
One Portal Sign-In, Open-Architecture Calculator, Producer vs. Client Portal. Four years of complex regulated-industry product work. The design pedigree underneath the systems work.
- Auth
- Financial modeling
- Role-based UX
- Regulated industries
── thesis
The interface is the surface output.
Most of the work in these projects sits below the interface, in the model, the orchestration layer, and the rules about what the user can change versus what the system has to guarantee. The screen is the surface output of those decisions.
My projects span physics simulation, AI orchestration, and design system governance. In each one, the difficult problem has been the allocation question: which decisions are the user's, which are the engineer's, and which get handed to the model. Visual design follows from that allocation. It doesn't drive it.
more about how I work →