Writing
Essays on engineering for regulated, real-time, and AI-native systems. Notes from current work and past projects.
Latest
- Tokenising property and shares: what gets builtTokenising real estate or equity turns on one question: does the ledger become the legal register, or shadow one? That answer sets the build.
- Tokenising property and shares: what gets builtTokenising real estate or equity turns on one question: does the ledger become the legal register, or shadow one? That answer sets the build.
- How HFT is different in crypto marketsHigh-frequency trading in crypto isn't TradFi HFT with new tickers. 24/7 clocks, fragmented venues with no consolidated tape, and on-chain settlement rewrite the assumptions before you write a line of code.
- EU AI Act Article 12: tamper-evident logging for high-risk AI systemsEU AI Act Article 12 requires tamper-evident logging for every high-risk AI system. Deadline 2 August 2026. Here is what compliant logging actually means.
- DORA compliance without a full-time CTO: what it actually requiresDORA applied January 2025. The regulation reads like documentation work and lands like systems work. Here is what your engineers actually have to build — and what it costs.
- CLARITY Act vs MiCA: what CTOs do nowSenate Banking marks up CLARITY on 14 May 2026. If your firm is MiCA-authorised, ~80% of your engineering work already transfers to CLARITY-readiness. The mapping.
- Fractional CTO guide to MiCA CASP complianceMiCA CASP authorisation applied 30 Dec 2024. Transitional period ends 1 July 2026. Fractional CTO guide to the engineering substrate CASPs must build.
- When you actually need nanosecondsMost software never needs sub-millisecond latency. Some does. The gap between the two is an order-of-magnitude problem, not an optimisation problem — and getting it wrong burns engineering budgets faster than almost anything else a CTO can authorise.