Writing
Behind the work.
Inside the decisions.
Problems encountered, trade-offs made, and lessons from building software and physical systems.
Start here
Designing idempotent payment APIs as an end-to-end contract
A payment retry is safe only when one client intent keeps the same durable identity across API acceptance, asynchronous workers, chain submission, webhooks, reconciliation, and operator recovery.
Read the essayMore notes
Orchestrating treasury without collapsing ledger, reserve, transfer, and settlement
Treasury workflows remain explainable when accounting truth, available funds, movement execution, and external settlement keep separate records while one orchestrator coordinates their evidence.
Separating planning and execution in agent systems
Operable agents need a reviewable plan, effect-bound approvals, durable execution state, checkpoint-safe retries, and independent evidence of completion.