This is the technical part of the document: how the system is built, and why this way rather than another. The six pages inside run from rules down to detail, and wherever you stop, you still hold everything above that point.

Page	Answers which question	Read it when you want to
Seven principles	What governs every technical choice?	Understand the rules before the detail — including what the project refuses to do
Architecture	What tiers make up the system?	See the same system at three increasing resolutions
Many chains, one identity	If everyone has their own chain, what connects them?	Read the core claim — and what the project still has to prove
Compliance at the protocol layer	Where are the rules enforced, and what does each layer see?	Assess what makes this different from an ordinary chain
Security and fault tolerance	How many failures does it survive, and who pays for security?	Examine the part with countable thresholds — and one question with no answer
The chain-producing machine	How does a chain come into being?	Understand why "running a blockchain" stops being an infrastructure project

Diagram

flowchart TB P["Seven principles rules governing every choice"] --> A["Architecture four tiers"] A --> I["Many chains, one identity"] A --> C["Compliance inside consensus"] A --> S["Security and fault tolerance"] A --> M["The chain-producing machine"]

Figure 15 — Principles above, architecture in the middle, four faces of detail below.

One thing to know before reading on. This part describes design and mechanism, not operating scale — that is the rule of the whole document, and it applies here too. You will find no block height, no machine count, no network identity on any page inside; for those, read Check the network yourself, where the numbers are read straight from the network rather than taken from this page.

And one easy confusion, stated up front. The name 9Chain covers three things: the shared network (a Layer 1 blockchain with the native token LOVE9), the platform that produces chains for customers (not a chain — it is what produces chains), and each chain produced (a private blockchain again). The full comparison is in Context; this part talks about all three, so when you meet the word "chain", ask which one it means.

In short: the technical part of an infrastructure project is worth reading not because it lists many components, but because it says clearly what enforces what — and calls the places where nothing enforces anything by their right name: a gate.