Editorial

The rest of this site teaches, and teaching material has no opinion. This is where the opinion goes. Each piece starts from something that actually happened in artificial intelligence or in software architecture — a release, a result, a failure, a shift in how the work is done — and argues its way to a position: what genuinely changed, what is only being marketed as change, and what a working architect should do differently because of it. Positions are arguable on purpose, and everything they rest on is linked and dated.

2 editorials 2 strands 11 cited sources 2,991 words

All Systems & Scale1 Reliability & Consequence1

Failure, security, accountability, and what happens when a generated decision reaches production.

Reliability & Consequence 1 September 2026 7 min read New

The first load to be shed

Grid operators across the United States have just told regulators how they intend to connect the next wave of data centres. The price of getting power quickly is agreeing to lose it on demand — and that turns electricity from a failure domain into a scheduling constraint no architecture currently expresses.

Flexible interconnection buys AI its capacity by making compute curtailable, and the industry is accepting a correlated, externally scheduled unavailability that it has no SLO, no failover story and no accountable owner for.

Read it → 8 sources gridcurtailmentcapacity planningavailability