Writing
Long-form writing on regulator-defensible architecture, AI governance, evidence, portability, and the operating reality of modernization.
The Fable 5 shutdown showed that frontier models can become externally controlled dependencies for regulated enterprises. That changes how firms should think about sovereignty, portability, concentration risk, and operational resilience.
Frontier AI models are global, but government and regulated data remain jurisdictional. This article explains why sovereign AI is becoming the default architecture across Europe.
Most governments now have AI strategies, principles, and playbooks. The harder question is whether they have the delivery machinery to turn those documents into safe production systems.
Part 3 of the AI software engineering series: why AI adoption becomes an operating-model problem, what the emerging AI engineering stack looks like, and what leaders should ask Monday morning.
Part 2 of the AI software engineering series: AI exposes existing enterprise weaknesses, changes requirements, raises the cost of architecture mistakes, turns testing into evaluation, and moves governance into runtime.
Part 1 of a three-part field guide on how AI changes software engineering: code generation accelerates, but the bottleneck moves toward architecture, evaluation, governance, ownership, and judgment.
Why enterprise AI adoption often stalls between promising pilots and durable production: the bottleneck is usually data, governance, ownership, workflow integration, and operating model maturity rather than model quality alone.
From warehouse to lakehouse to DataOS: an architectural genealogy of enterprise data systems and why the next generation must solve sovereignty, evidence, portability, and AI governance together.
An introduction to the Sovereign Data Operating Plane (SDOP): a regulator-defensible architectural pattern composed of five elements and three differentiating pillars.
Why Tier-1 enterprises are simultaneously struggling with enterprise AI, regulator-defensible data architecture, and continuous modernization, and why current architectures solve at most one of the three.
Eleven years after BCBS 239, only two of thirty-one G-SIBs are considered fully compliant. This article examines what that failure reveals about modern enterprise data architecture.