OS for Chaos is a personal site with two layers.
The first layer is literal. I am building an event-driven operating system for my own life: a set of long-running processes that collect data, run research pipelines, manage personal finance, assist with the daily grind and experiment with trading. It is written in Python, talks over a message bus, and is developed together with AI agents that work under a written constitution. The OS section is about that: architecture, debugging stories with evidence, operations without a platform team, and what it is like to govern AI coding agents. The Trading section takes the trading experiments apart as an engineering problem: strategies as code, paper trading before real money, and the rails that keep a bot from hurting its owner. Mechanisms, never figures.
The second layer is the chaos itself. I am a physician and a father with more interests than calendar: mathematics, physics, sport, and the occasional rabbit hole. The Life section holds that side.
Travel notes and observations on modern marketing by my partner are planned as separate sections and will appear here with their own author page.
What you will not find here
- Patients. Never, not even anonymised.
- My children’s names or faces.
- Account numbers, position sizes or any other figures from my own trading.
- Hostnames, paths or configuration of the machines the system runs on.
Disclaimers
Nothing on this site is medical advice. Nothing on this site is investment advice. Opinions are my own and do not represent any employer or institution.
Contact and following
RSS: all posts, or per section (OS, Trading, Life). Code I can share lives on GitHub. I also publish on Medium; the canonical version of every post lives here.
E-mail: osforchaos@gmail.com.