Insights
Notes on architecture, infrastructure, security, and AI systems — written from work I have actually shipped.
Four connectivity states, one clinic
Offline-first is usually modelled as a boolean. Building HealthOS taught me that a hospital needs at least four states, and that the user has to be able to see which one they are in.
- Architecture
- Offline-first
- Healthcare
Multi-tenancy when the tenants are hospitals
Three separations get conflated in multi-tenant systems: tenant, role, and workflow. Clinical software makes the cost of confusing them obvious.
- Architecture
- Security
What an AI agent needs before you can leave it running
Notes from taking a retrieval-and-reasoning agent from a working demo to something that runs unattended and touches a blockchain.
- AI
- Architecture
A risk score you cannot explain is noise
Modelling package dependencies as a graph for Argus Protocol, and why tracing the reason behind a score mattered more than the scoring itself.
- Security
- Architecture
Security trade-offs for small teams
The controls I put in first when there is no security budget, no dedicated team, and real consequences if something goes wrong.
- Security
- Infrastructure
When custom software is worth it
I have deployed bought systems across multiple healthcare sites and I am building a platform from scratch. The decision between the two is less about cost than about who owns the problem.
- Architecture
- Delivery
Designing systems for unstable infrastructure
What I have learned running technology across sites where neither power nor connectivity can be assumed, and how that changes the architecture rather than just the ops plan.
- Infrastructure
- Architecture