Blog
Notes on contract-driven development.
Writing on portable business logic, contract governance, and why the same rule keeps getting rewritten four times.
AI agents need contracts, not just function definitions
Function calling tells an agent what a tool does. It says nothing about what has to be true before or after it runs.
Read more →Why I stopped writing the same business logic four times
The same pricing rule lived in the web app, the mobile app, the backend, and the AI pipeline. Each copy drifted.
Read more →The hidden cost of runtime assumptions
Most bugs in business logic are not logic bugs. They are assumptions about the environment that turned out to be false.
Read more →What Universal Microservices Architecture got right
UMA argued for one deployable unit that runs anywhere. Traverse is one way to build that.
Read more →What WASM actually gives you for business logic
Portability and sandboxing, not performance, is the reason WASM matters for governed business logic.
Read more →