01
Clinical context
I begin with the people, handoffs, and constraints that shape a real health problem.
About and context
I move between these fields because important problems rarely stay inside one discipline.
I like translating a clinical need into a research question, a prototype, or a system that another person can inspect and improve.
My work is built around questions that connect people, science, and systems.
The name
In Hindu traditions, Manu is commonly associated with the human ancestor and with beginnings, order, and renewal. The stories vary across texts; for me, the name is a reminder to build from first principles, stay curious, and take responsibility for what I put into the world.
Projects earn my attention when they carry real uncertainty and real upside—especially when a new approach could change how a system is understood or how people experience it.
Where it began
When I was ten, I was already trying to turn a question into a system. I had started thinking about water purification when I noticed small droplets gathering around the cold outer rim of a bottle. I understood them as water vapour returning to liquid, and wondered whether the same idea could become a purification system: collect the vapour, condense it, and build a bottle around the process.
That thought became a bottle design. I took the documents to the patent office, and they were stolen. It was a difficult first lesson in how fragile an idea can feel once it leaves your hands.
More important than the loss was the question it left me with: why do people care so much about who did it, and not about who needs it more? I still return to that question when I work on research and systems. Credit matters, but usefulness, access, and the person waiting for the solution matter too.
Ways of working
Robert Frost, Stopping by Woods on a Snowy Evening
Publication is not the final step for me. It is a step that tests the initial research question, gives the work a form others can examine, and helps carry the problem toward the people who need a solution.
I want the work to stay honest about what it knows, what it does not know, and who it is meant to serve. Recognition can open a door, but usefulness is what gives the work a reason to continue.
01
I begin with the people, handoffs, and constraints that shape a real health problem.
02
I turn broad questions into studyable questions, clear measures, and claims the evidence can carry.
03
I build prototypes with explicit privacy boundaries, repeatable tests, and failure behavior another team can inspect.
Recognition
Experience
Clinical work following medical training, within routine patient-care and hospital workflows.
A stealth startup building reliable local AI infrastructure for regulated industries.
A health-tech startup developing robotic and automation infrastructure for hospital clinical workflows.
Research organization to study neuromodulation and neuroplasticity in young adults.
Education
Medical training in Mangalore, with a foundation in clinical medicine, biomedical science, patient care, and clinical research.
Public links
Where the disciplines meet
The most natural point of entry is where a user need still has to become a study question, a product brief, or a system people can examine. That intersection—between clinical judgment, evidence, and technical design—is where my work tends to be most useful.