I work where systems stop being abstract.
Where software meets hardware. Where autonomy meets responsibility. Where architecture has to meet reality as it is — not as we wish it to be.
Resilience starts before failure.
Weather, bandwidth, power, law, institutions, supply chains, adversaries and human behaviour are not disturbances outside the architecture. They are inputs. Reality is part of the specification whether we wrote it down or not.
A resilient system protects its purpose, not its original path.
Capability
Define what must remain possible when the perfect state disappears.
Responsibility
Make intent, authority, intervention and accountability explicit.
Sovereignty
Own the technologies, interfaces and dependencies that determine freedom to act.
05Systems
Systems, not slogans.
AI, cybersecurity, autonomous platforms, critical infrastructure and dual-use innovation are often discussed as separate topics. In practice they are coupled systems.
Their interfaces matter. Their dependencies matter. Their failure modes matter. Their governance matters.
We don’t predict the future. We architect it.
The sea keeps engineering honest.
It is open, dynamic and uninterested in our slide decks. Weather changes. Communications disappear. Sensors disagree. People improvise. A system either has a meaningful degraded mode — or it simply stops being a system.
That is why the maritime world remains one of my strongest reference points: not as decoration, but as a place where architecture meets consequence.