TLCTC has exactly ten Clusters (= ten Definitions, one per cluster), exactly ten Axioms, and exactly ten Principles on the Logical Foundations page. The three counts were arrived at independently, at different times, for different reasons. Only one of them was aimed at the number ten — the other two just landed there. Noticing the coincidence was an afterthought. The framework doesn't care about the number; the number just happens to fit the cognitive shape of what each pillar was trying to do.
The Observation
I was drafting the Logical Foundations page and listing the principles that carry the framework. Ten of them lined up naturally. That is when I looked up and realized the framework already had two other ten-counts staring at me: ten Clusters (which means ten Definitions, since every cluster has exactly one canonical definition), and ten Axioms. Three pillars. Three independent counts. Three tens.
Not planned. Not engineered. I did not sit down at any point and say "let there be ten Axioms." They just came out at ten when the job was done.
The Three Pillars
Pillar 1 — 10 Clusters = 10 Definitions
This one is by construction. The thought experiment — imagining the entire IT landscape as a single object and asking "in how many fundamentally distinct ways can this object be exploited?" — returns ten aspects. Designed functionality, server-side code, client-side code, identity, communication channels, finite capacity, code execution, physical form, human operators, third-party trust. Ten aspects, ten generic vulnerabilities, ten clusters. Each cluster carries exactly one canonical definition, so the count collapses: Clusters and Definitions are the same set, described twice.
This is the only one of the three tens that is load-bearing. Change this number and the framework changes. The other two are decorative by comparison.
Pillar 2 — 10 Axioms
The Axioms emerged during the V2.0 formalization. I was trying to write down the non-negotiable structural commitments of TLCTC — the things from which every classification rule falls out — and the list kept growing until it covered what needed to be covered. Then it stopped. It happened to stop at ten. There is no Axiom XI that was cut for being redundant, and there is no Axiom IX that was invented to reach a target. The shape of the thing being axiomatized produced exactly this many commitments, and the writer was not counting.
Pillar 3 — 10 Principles
The Principles were written for a blog. Their job is to communicate the logical foundations of the framework in a form a reader can hold in one sitting — causal separation, actor–threat separation, the thought experiment, partition logic, attack paths, SRE vs DRE, credential duality, falsifiability, technological invariance, causal direction. Ten landed as the natural cut. One fewer and something important goes missing. One more and the reader loses the arc.
This is the most explicitly "authorial" of the three counts — I did choose where to stop. But I was optimizing for coverage and readability, not for ten.
Why It Keeps Being Ten
There is no mystery. Ten is what you get when you try to partition a complex domain at a granularity that a human can still hold in working memory:
- Five or six is too coarse — real distinctions get merged and the taxonomy is unfalsifiable.
- Twenty or thirty is too fine — you lose the overview and the categories start to overlap.
- Seven plus or minus two (Miller's classic working-memory window) is where humans feel comfortable, and ten sits right at the upper edge — enough to cover, few enough to remember.
Decimal also happens to be the number system our species chose — initially because we carry ten fingers, but deeply cemented by our arithmetic notation and cultural conditioning. While we increasingly build systems based on binary logic, ten remains the default "complete" feeling in human cognition. It is not surprising that three independent attempts to cover a complex domain completely and communicably all terminated at the same round number.
Ten is not magic. Ten is where "enough to partition" and "few enough to hold" intersect.
Interactive: Granularity & The Sweet Spot
Drag the slider to partition the complex domain. Notice how dividing the same area into more categories forces you to explain things with more attributes, increasing visual granularity until overview is lost.
(7±2)
(10)
The Triangle
Three pillars, each numbering ten, sit naturally as the vertices of a triangle:
- 🔺 Top — Principles: the meta layer. Why the whole thing holds up as an engineering artifact.
- ◢ Bottom-left — Axioms: the rules of the framework. Why the content is shaped the way it is.
- ◣ Bottom-right — Clusters / Definitions: the content of the framework. What threats exist.
Content, rules, meta. Ten, ten, ten. Multiplied together, they do not give you 1000 — they give you TLCTC. That is the real joke: the product of the three pillars is not a number but the framework itself. Ten Clusters, ten Axioms, ten Principles, one TLCTC — which is exactly what falls out when three independent "tens" line up on the same object.
This Is Not a Design Claim
To be clear: the 10 × 10 × 10 shape is not an argument for TLCTC being correct. Correctness rests on the partition holding, the axioms being consistent, and the classification rules being falsifiable. The triple-ten is a coincidence that shows up after the real work is done. It is the kind of pattern you only notice once you stop looking.
But it is a pleasing one. Frameworks that grow organically and still end up numerically tidy tend to be the ones where the shape of the problem was doing most of the work.
Closing
The 10 Clusters were forced by the domain. The 10 Axioms were forced by consistency. The 10 Principles were forced by what a reader can hold. Three different forces, one identical outcome.
Not designed. Just ended up that way. Which is, in the end, the best thing you can say about a framework.