From HP-UX and Solaris through Kubernetes, OpenShift, and modern AI runtime work.
IBM / eu-LISA, Poste Italiane, and TIM shape the reliability baseline.
Value-Shore platform work plus independent product building and systems research.
Apple Silicon, macOS companions, and controlled multi-provider routing by default.
Selected systems
A few systems that show the actual shape of the work.
Not a product zoo. Just enough proof to show the pattern: explicit contracts, local control, careful boundaries, and runtime clarity.
01
SmoothOperator / agents
Private multi-tenant AI orchestration platform with workflow controls, document layers, artifact delivery, tenant isolation, and multi-provider execution.
02
cdx
Capability distillation system that turns durable agent doctrine into reusable skills and operating rules.
03
er_guaina
Local-first agent operating system with one authoritative daemon, durable continuity, and governed execution.
04
the-seven
Privacy-first multi-model council for hard questions, designed around structure instead of chat sprawl.
05
Veneer
Native macOS privacy helper for AI copy/paste workflows and controlled restoration of sensitive text.
Supporting: local-doc-studio voices mac-local-image ai-rgap cloudflare-publish
Career arc
Long path. Consistent pattern.
Operational truth first, architecture second, AI systems built on top of both.
1999 → 2007
Unix / Linux administrator
HP-UX, Solaris, Linux, clustering, hardening, backup, recovery, and learning to respect the substrate.
2008 → 2015
Systems engineer
Virtualization, storage, middleware, and turning infrastructure into something repeatable rather than improvised.
2016 → 2024
Solution / platform architect
Kubernetes, OpenShift, reliability, isolation, and platform boundaries shaped around real operational constraints.
2025 → now
AI systems builder
Agent runtimes, orchestration planes, multimodal tools, and local-first products built with operator-grade discipline.
Operating principles
Short rules that survive contact with production.
Reliability
Design for predictable degradation, not heroic rescue.
Operator clarity
Logs, controls, and contracts are part of the product surface.
Privacy-first
Keep data, models, and control close to the operator when the product allows it.
One canonical path
Competing implementations are drift, not optionality.
Evidence over hype
If a system cannot be explained and verified, it is not finished.
Contact
If the problem is messy, send the mess.
I work best on systems that need clarity, reliability, and a calm operating model.