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.

11 editorials 6 strands 78 cited sources 17,692 words

All Systems & Scale2 Practice & Method1 Economics & Value1 Platforms & Power2 Evidence & Evaluation1 Reliability & Consequence4

How architecture is actually done — reviews, ADRs, diagrams, documentation and the craft of deciding.

Practice & Method 10 September 2026 8 min read New

The second copy is the one that runs

The same commit trailer is required by the Linux kernel, required by Node.js, and forbidden by Kubernetes. Major projects are now writing their contribution rules down twice — once for people, once for the machine — and nothing checks that the two versions still agree.

Every serious project now keeps two copies of its contribution process, one addressed to contributors that carries the authority and one addressed to agents that carries the effect, and the second copy is a derived artefact whose derivation nothing enforces.

Read it → 9 sources agent instructionscontribution policyopen sourceprocess documentation