"It takes all the running you can do, to keep in the same place."
Here's what most readers miss about the Red Queen: she is not the cruel one.
Your May Guide Through the Strategic Architecture Constellations
The Queen of Hearts demanded perfection and screamed "Off with their heads!" at every deviation. Brittle authoritarian governance. Couldn't tolerate variation. Couldn't learn.
The Red Queen is something else entirely. She doesn't punish mistakes. She practices the running. Her insistence that you must run twice as fast to get somewhere else is not cruelty. It is the operating physics of a moving world.
Lewis Carroll wrote that line 150 years before software learned the lesson. Evolutionary biology named the Red Queen Hypothesis after it in 1973. And in 2026, with AI agents producing diff volume at multiples of human review capacity, with dependencies evolving continuously underneath you, with adversaries iterating without compliance review, resilience engineering is finally catching up to what the Queen taught Alice on the chessboard:
Stasis is decay. Motion is the baseline.
Most enterprises confuse this with two inferior aims. They confuse it with robustness, the ability to withstand a known shock without breaking. They confuse it with disaster recovery, the ability to restore after the system has already broken. Both matter. Neither is resilience engineering. Resilience is the capability of a system to keep running, keep evolving, and keep gaining ground in conditions its designers did not predict.
What you'll discover in this month's constellation guide:
♟️ Why static architectures have become anchors, not assets — The diagrams that took six months to draw describe a system that no longer exists. Architecture in 2026 is not a document. It is a practice.
🧬 Fragile, robust, antifragile — Most engineering programs aim for robust and call themselves resilient. They are not the same thing. Taleb's vocabulary becomes operational when you map it to architecture, governance, and learning loops.
🛡️ The Digital Immune System — Six capabilities running together: observability, AI-augmented testing, chaos engineering, auto-remediation, SRE, and supply chain security. Walls fail catastrophically. Immune systems fail gracefully and learn.
⚡ Fitness functions as forward-remembering memory — "It's a poor sort of memory that only works backwards," said the White Queen. Documentation remembers what was decided. Fitness functions remember what must remain true. In the agentic era, they are the only architectural review that runs at machine speed.
🔥 Chaos engineering as practiced running — You don't earn confidence by writing better runbooks. You earn it by running the runbook on a Tuesday afternoon and watching what happens.
🎯 Five steps to build the Red Queen's Court — Define steady state in customer terms. Encode the architecture in tests. Practice running on a schedule. Build deterministic enforcement at agent speed. Learn from every stress.
♟️ What survives the chessboard — The Red Queen runs the race. Next month, the Tweedles teach the system to question its own running, because motion in only one direction is still bias.
"Robustness is not enough. Disaster recovery is not enough. The systems you cannot afford to lose are the ones that practice losing every day."
Ready to build the Court?
This month's guide explores Resilience Engineering: the practice of running continuously with a moving environment so your systems gain capability under stress instead of losing it. Because in a world where your AI coding agents produce changes faster than humans can review them, where dependencies evolve underneath you, where the threat landscape iterates faster than your controls, the only architecture worth having is the one that keeps running while the chessboard moves.
How long has it been since you ran a chaos experiment in production? How many fitness functions guard your core modules? When was the last postmortem that produced a permanent encoded lesson, not just a war story?
Begin at the beginning,
Shawn McCarthy
Chief Archeologist
P.S. The Red Queen would appreciate this paradox: the organizations most confident their systems are resilient are usually the ones that have not actually tried to break them. They have written runbooks. They have approved DR plans. They have certified compliance frameworks. What they have not done is run the experiment on a Tuesday afternoon and watch what actually happens. If you stopped attending to your governance scores this quarter, would they hold steady, or would they decay until the agents you trust today no longer deserve the autonomy you have given them?
