The Architecture Canon

Nobody sets out to build a system that lies.

They just forget to decide which part is allowed to tell the truth. Then the cache says one thing, the database says another, the search index is twelve minutes behind, and something downstream confidently explains the wrong version of reality to a customer.

That is what this is for. Eight rules I keep arriving back at, written down once, with the evidence attached: the repeatable moves that make each rule real, the systems where it held, and the ones where it did not.

It is a reference, not a book. Read the law you need and leave.

What the words mean

This site uses a few words precisely. Not jargon for its own sake, but you will hit them on the first page, so here they are in plain terms.

• Law — a claim about systems I am willing to defend, that has held up across more than one of them. There are eight.
• Pattern — a repeatable move that makes a law real in an actual design. A law says what must be true; a pattern is how you get there.
• Concept — a word used here in one exact sense, defined once, so it means the same thing on every page.
• Case study — a real system, described honestly, including where it strained.
• Reference architecture — the whole shape assembled: laws and patterns wired together.
• Projection — anything published out of this, such as book chapters, talks, and posts. They quote the canon. They do not replace it.

The eight laws

• I — Truth Has One Home — one authoritative home per fact. Every other copy is derived, and honest about being a copy.
• II — Architecture Is Constraint Management — design is choosing what you guarantee and what you give up, then making the guarantees structurally hard to violate.
• III — Security Is a Property, Not a Feature — it comes from how the system is built, through least privilege, real boundaries, and safe defaults, or it is not there at all.
• IV — Relationships Are Data — the connections between things are real data with their own attributes. Most models describe the nouns carefully and shrug at the verbs. The verbs were the point.
• V — Evidence Before Intelligence — gather the grounding first, cite it, keep it. A conclusion is worth exactly what its evidence is worth.
• VI — Platforms Exist To Remove Decisions — a platform earns its keep by the number of easily-botched choices its users no longer have to get right. Make the correct thing the default.
• VII — Systems Degrade Better Than Organizations — build things to lose function in proportion to the failure, protecting truth and safety, because people under pressure will not degrade gracefully.
• VIII — Documentation Is Architecture — the written, accurate, maintained account is the architecture in the only form that outlives the people who built it.

What is in here

187 units, cross-linked 1,260 ways, with nothing left dangling: 8 laws, 25 patterns, 114 concepts, 21 diagrams, 5 case studies, 2 reference architectures, and 12 references to the work this builds on.

Why it is built this way

The site follows its own first law. Every idea lives in exactly one place, and this is a view onto it: organized, searchable, cross-referenced, but never a second copy that can quietly drift out of agreement with the original.

If that sounds strict, it is. It is also the point. A canon that contradicts itself is just a pile of articles.