Complex Systems & Simulation
My work focuses on software systems that must remain understandable, evolvable and verifiable despite domain complexity, distributed execution and strong integration constraints.
Selected work and reflections around software architecture, simulation, model-based engineering and distributed systems.
My work focuses on software systems that must remain understandable, evolvable and verifiable despite domain complexity, distributed execution and strong integration constraints.
I use model-based approaches to connect requirements, architecture decisions and implementation constraints, with a focus on traceability and automation.
I focus on architecture as a decision-making discipline: framing trade-offs, documenting constraints, aligning teams and making systems easier to reason about.
I am interested in distributed architectures where boundaries, contracts, orchestration, observability and failure modes are first-class design concerns.
A practical guide to reducing Java, Python, and TypeScript contract drift without confusing generated types for runtime or domain guarantees.
Read article →A staged design case for containing storage, research, integration, and operational uncertainty in a deep-tech SaaS.
Read article →A proposed modular Quarkus design for making selected architectural drift visible before human review.
Read article →A MeshSync-inspired design case study for governing heterogeneous worker contracts, workflows, delivery, and change.
Read article →An MBSE-inspired reference architecture for governing, versioning, and durably executing distributed workflow definitions.
Read article →Use C4, ADRs and versioned diagram sources to maintain a structural map of a distributed system~then add the behavioural and operational evidence it cannot provide alone.
Read article →A reference architecture for keeping probabilistic AI capabilities behind explicit contracts while domain policy and operational controls bound their consequences.
Read article →Mesh-Sync explores how complex 3D asset collections can be synchronized, normalized and reasoned about across heterogeneous storage systems.
The architectural problem is to keep storage, processing and marketplace-oriented workflows explicit without collapsing them into one opaque platform.
It demonstrates an interest in traceability, contract boundaries and evolvable platform design.
View project →MIDAS explores how software engineering workflows can be orchestrated with stronger traceability, review gates and human control.
The architectural problem is to coordinate tool-driven work without losing reviewability or decision ownership.
It demonstrates a preference for explicit workflow control over opaque automation.
View project →