The products exist. The next layer needs experienced engineering.
I am looking for a technical cofounder or founding engineer who can help harden what exists, challenge what I got wrong, and build the durable intelligence and infrastructure underneath the next stage of Nomos.
Two views of the opportunity.
The company, the flagship, and the role
A fast view of what has been built, why Munus is the flagship, what the shared thesis is, and what I need from a founding technical partner.
Technical briefWhat you would be walking into
The stacks, architectures, current systems, open risks, and the places where experienced engineering judgment matters first.
Repository walkthroughs
Coming soon. A cleaner route into the relevant repositories, dependency graphs, security notes, and current technical priorities.
The hard part is the boundary.
What should be deterministic. What can be inferred. What should be remembered. What must stay private. What needs a human decision. What an intelligent system should do when it does not know.
That is the work I want to solve with someone who can think across architecture, product, trust, and the person on the other side of the screen.
Health intelligence built around context over time.
Acesa brings symptoms, medications, appointments, history, photographs, body regions, triggers, treatments, environmental context, and recovery over time into one private family health memory.
A provisional patent application has been filed for aspects of the health intelligence layer behind Acesa Health.
The technical brief shows what is already implemented and what still needs deeper engineering review.
This is a real founding role, not a freelance rescue job.
Nomos is founder-funded and cannot offer a salary yet. Role, equity, scope, and decision rights would be agreed in writing before substantial work begins.
You would be joining a portfolio with working systems already in motion, not a blank Figma file and a promise that somebody will eventually build it.