This part answers two questions: what 9Chain is, and why it is built this way rather than another way. It does not teach you what to run or what to call — those belong to Network and nodes and Build on 9Chain.

The ten pages below follow a deliberate order, and that order is itself a statement of attitude: evidence comes before invitation. You meet the reading rules before the content, the problem before the solution, and the project's weak points before the invitation to join. A document arranged the other way round — invite first, confess later — reads far more pleasantly, and that is exactly why it should not be arranged that way.

Page	Answers which question	Read it when you want to
Before you read	How should this document be read?	Know which sentences are locked and which can still change
Context	Why does the world need another network?	Check whether the problem is real
Nine missions	What does this project actually want?	Understand the part that survives changes in technology
The 9Chain platform	How is it built?	See architecture, consensus, compliance, fault tolerance
Applications and users	Who uses it, and who cannot yet?	Find your own place in it
LOVE9 economics	Where do tokens come from and go?	Examine the part most easily overstated
Nine roles	Who may do what, and who checks whom?	Understand how power is divided
Operations and governance	Who holds the keys, who can change the rules?	Assess centralisation risk
Open questions and concerns	Where is it still weak?	Read the counter-arguments, including the project's own
Conclusion	How do I take part?	Learn which doors are open and which are still owed

Diagram

flowchart LR A["How to read four labels"] --> B["Problem and context"] B --> C["Design and mechanism"] C --> D["Weak points and rebuttals"] D --> E["Invitation and doors still owed"]

Figure 1 — The reading path: each step stands on the one before it, and the invitation comes last.

A note on tense. This entire part is written in the permanent tense: it describes design, mechanisms, and the gates a network must pass. It deliberately contains no live number — no block height, no network identity, no count of machines running. If you want to know how the network stands at the moment you are reading, that is the job of Network and nodes, and the answer there is read straight from the network rather than taken from this page.

In short: the Learn part says what the project intends to do and how; to find out how far it has actually got, do not read here — read where you can check for yourself.