Why producing working code faster with AI raises the stakes on architectural quality, and why passing tests is not the same as having sound boundaries.
AI-assisted software, built with discipline
Building serious software with AI, without outsourcing judgment.
A public learning log about architecture, trust boundaries, reviewability, state, and product judgment in AI-assisted software development.
I come from enterprise procurement and IT governance, and I write about what changes when that judgment meets hands-on software building with AI.
Recent notes from the work
Articles
Why tenant scope cannot be treated as a field that flows through the system, and what it means to establish it as a trust boundary instead.
Why OpenSpec belongs in a different category than knowledge tools—and why planning before execution is the actual constraint it addresses.
Why building a real multi-tenant SaaS stops being a feature problem and becomes a problem of trust boundaries, guarantees, and responsibility placement.
Why the biggest gain in AI-assisted development comes from durable local knowledge and disciplined workflow structure, not from keeping every external tool always active.