AI-Native Architecture
The four-properties test and everything that applies it: probabilistic behavior, inference economics, the context supply chain, and model lifecycle — architecture you can fail against the frame, not just articles that mention AI.
-
You Didn't Change Anything. It Changed Anyway.
Services version on your schedule. Models drift, get deprecated, and improve on someone else's. Designing the boundary around a component you do not control, and the honest math on how much abstraction is worth paying for.
Read more → -
The Model Isn't Wrong. Your Context Is.
Retrieval, freshness, and data boundaries stop being back-office plumbing the moment a model depends on them. The context supply chain deserves the same rigor we learned to give service contracts, and it is where AI security actually lives.
Read more → -
Your Function Call Was Free. This One Isn't.
Distributed systems changed architecture because the network made a function call expensive. AI does it again, except the cost is money as well as latency. Model routing is an architectural decision, not an optimization you do later.
Read more → -
It Passed the Test. That Doesn't Mean It Works.
Every testing, monitoring, and reliability practice you own rests on one assumption: same input, same output. An LLM in the call path removes it. What replaces it is evaluation, thresholds, and verification as an explicit architectural layer with a cost and an owner.
Read more → -
From Cloud-Native to AI-Native: The Next Evolution of Enterprise Architecture
Every enterprise says it's adopting AI, the same way every enterprise once said it was in the cloud. Bolting AI features onto an existing system is the new lift-and-shift — the four-properties test for what genuinely AI-native architecture requires instead.
Read more →