An independent engineering practice, working across the whole stack of a system, and the regulation and money around it.
One person, the whole stack of a system.
SANIX is an independent engineering practice: one person, twenty-six, more than five of those years working professionally, across freelance work and technical leadership. The work runs from the network and the operating system to the model and the regulation on top: in energy, industry and health, where a bad decision is a clinical or regulatory consequence, not a rollback.
The home page indexes what that looks like in practice; the notes carry the engineering. This page is the shape of the practice and the tools it is built with.
Three habits, from three kinds of consequence.
Whether it can be built is the easy half.
A feature is judged by whether it should exist: how it will be maintained, how it moves risk and compliance, and whether its operating cost is justified. I read the funding and the business case, not only the backlog.
Most of this work is traceability under another name.
Proving a sample is what it claims to be at 1 kHz, that a medical change was validated before it shipped, that an industrial link was authenticated and logged. Writing the record is never the hard part; being able to trust it afterwards is.
Knowing when not to use a model is the part worth paying for.
Hosted frontier models and the open-source stack for the cases where the data cannot leave the building. Which one is an engineering and compliance decision, made before anything is built: and I say clearly when a model does not earn its place.
What the systems are built with.
What I actually use in production lives with the capabilities it serves.
The one member of the team who has never read a line of code.
My shiba: chief nap auditor, night-deploy supervisor, and the only reason I get out of the chair every few hours. He follows you with his eyes.
What this site never contains, and how to reach me.
Professional work is carried out under NDA and described at a high level everywhere on this site: no employer names, internal architectures, client details or proprietary systems. The independent systems: the public-tender system, the market digital twin, Erario and Menucesta.es: are built on public, licensed, user-supplied or synthetic data.
Open to serious technical conversations: applied AI, automation, data systems, industrial connectivity and compliance, technical product development and selected consulting. If the hard part is how the whole thing holds together, that is the work I want.