The whitepaper corpus is not one flat shelf. Some papers define the current protocol thesis, some widen one important boundary such as liability or cross-chain custody, and some describe scenario families or governance systems that must still be read with explicit maturity labels. This page turns that corpus into a usable reading order.
The Short Safe Reading Order
If you are new to the corpus, start with these four documents in this exact order.
| Read first | Why it is first | What it should answer |
|---|---|---|
| Uniqueness Whitepaper | It gives the category claim in a lighter frame before the deeper protocol papers | “Why does Z00Z claim to be a distinct system family?” |
| Main Whitepaper | It defines the baseline protocol thesis, wallet-local possession, checkpointed settlement, and present-vs-target posture | “What is Z00Z claiming as a system?” |
| Use Cases Whitepaper | It explains the six scenario families and keeps them ordered by maturity | “Where does this architecture matter first?” |
| Corpus Terminology And Abbreviations Reference | It stabilizes terms that otherwise drift across papers | “What do the recurring nouns actually mean?” |
That four-document path is enough to prevent most research mistakes. Many later papers assume you already understand the category claim, the protocol category, the scenario ordering, and the corpus vocabulary.
Core Authority Papers
These are the files most readers should treat as first-line authority.
| File | Role in the corpus | Safe reading posture |
|---|---|---|
| Main Whitepaper | Core protocol thesis, wallet-local possession, settlement-notary framing, privacy boundaries, locker direction, and maturity split | Use for baseline present-tense protocol wording |
| Use Cases Whitepaper | Six-family scenario map from offline cash through agent and machine rights | Use when comparing scenario fit or ordering market wedges |
| Corpus Terminology And Abbreviations Reference | Cross-paper vocabulary contract | Use when a term appears in multiple papers or shifts from live to target meaning |
| Privacy Threat Model And Metrics | Layered privacy, adversary classes, and disclosure boundaries | Use before making strong privacy or selective-disclosure claims |
These papers are not interchangeable. The main whitepaper gives the protocol center of gravity. The terminology reference stops noun drift. The privacy model tells you where confidentiality ends. The use-cases paper tells you how the argument is staged for readers and builders.
Companion Papers By Question
Once the core is clear, choose the companion paper that answers the question you actually have.
| If you need more depth on… | Read this file | What it adds |
|---|---|---|
| Offline fraud, bounded accountability, and reveal-on-conflict logic | Linked Liability Whitepaper | It explains how private execution can stay private in the honest path while still exposing fraud narrowly |
| External custody, trust tiers, and private rights over outside assets | Cross-Chain Integration Whitepaper | It separates internal private reassignment from external custody and redemption assumptions |
| Policy-shaped money, vouchers, and rights boundaries | Assets, Rights, And Vouchers Whitepaper and Smart Cash | They define why bounded rules live in objects rather than in a public smart-contract default |
| Useful-work rewards, review lanes, and private payout | Proof-of-Useful-Work Whitepaper | It keeps contributor rewards rule-bound and privacy-aware |
| Agent budgets, machine rights, and spendable capability objects | Agentic Offline Economy Whitepaper | It widens the architecture beyond money without pretending every extension is already live |
| Governance lanes, AI review safety, and treasury non-control | DAO Whitepaper | It explains how AI evaluation and treasury execution must remain separated |
The important discipline is that these papers deepen the corpus. They do not automatically upgrade target architecture into live protocol fact.
Authority Lane Map
Use the map to keep authority lanes separate. Core papers define present-tense framing; companion papers deepen one boundary; archive material explains provenance but should not silently override current corpus wording.
Maturity Labels To Keep Visible
Most misunderstanding comes from forgetting that different papers operate at different maturity bands.
| Maturity label | What it usually means in this corpus | Typical examples |
|---|---|---|
| Live core contract | There is already a repo-backed protocol or wallet surface strong enough for present-tense wording | Package verification, checkpoint settlement, wallet-local possession |
| Near-core extension | The concept fits the live model closely, but depends on more service or policy closure | Policy-shaped money, private external-asset rights |
| Broader deployment | The architecture is coherent, but operational rails and product layers matter more | Organizational settlement, mass distribution programs |
| Expansion vector | Strong direction, weaker present-tense deployment posture | Machine and agent rights, richer useful-work ecosystems |
When you summarize a paper, keep that label visible. It is better to say “the corpus positions this as a serious extension direction” than to silently rewrite it as a shipped feature.
How To Cite The Corpus Without Flattening It
Three habits keep the whitepaper set usable.
First, cite the narrowest authority that owns the claim. If you are discussing privacy leakage at ingress and egress, use Privacy Threat Model And Metrics, not only the main paper. If you are discussing bounded agent spending, use Agentic Offline Economy Whitepaper, not only the use-cases overview.
Second, cite one core paper plus one companion paper when the topic crosses a boundary. External-asset rights, for example, usually need both Main Whitepaper and Cross-Chain Integration Whitepaper.
Third, do not use archive-era framing as a substitute for current-corpus wording. If an older draft says something more aggressively than the newer whitepapers, the newer corpus wins unless the page explicitly says otherwise.
What This Page Does Not Treat As Current Authority
This page intentionally does not elevate archived or superseded material into the main authority lane. Older litepaper-era framing, exploratory drafts, and historical notes still matter for provenance, but they should be read through Archive, not as first-line evidence for live protocol wording.
That restraint matters because the corpus is ambitious. It wants to speak about private cash, external rights, selective disclosure, machine economies, and rule-bound useful-work programs in one family. The only way to keep that family credible is to keep the authority order strict.
Complete Corpus Inventory
The current reading map should account for every paper in content/whitepapers/, even when a reader only needs a short path. The main paper is the protocol entry point. Uniqueness.md explains the category claim for readers who need a simpler positioning frame before they read deeper protocol material. UseCases.md controls scenario selection and maturity order. Assets-Rights-Vauchers.md, Smart-Cash.md, and Linked-Liability.md form the object-boundary cluster for rights, vouchers, policy, and offline fraud accountability. Cross-Chain-Integration.md controls external custody, lockers, trust tiers, and redemption boundaries. Privacy-Threat-Model.md controls leakage, metrics, selective disclosure, and anti-patterns. OnionNet.md controls transport privacy and route construction. Tokenomics.md controls native-asset supply, fee credits, bonds, treasury compartments, and bootstrap incentives. DAO.md controls governance lanes, AI-assisted review limits, proposal classes, and treasury safety. Proof-of-Useful-Work.md controls useful-work evidence, fact consensus, value consensus, private reward authorization, and rollout discipline. Legal-Architecture.md controls public-claim boundaries, steward separation, operators, issuers, wallets, and compliance-profile language. Post-Quantum-Migration.md controls suite identity, legacy cryptographic risk, and migration sequencing. The corpus terminology reference controls shared names, abbreviations, aliases, casing, and editorial guardrails. The whitepapers index page itself is only a hub; it does not create new authority.
Short Path And Long Path
The short path for a new reader is: Uniqueness.md, then Main-Whitepaper.md, then UseCases.md, then the specific companion paper for the reader’s question. That path is intentionally conservative. It teaches the category claim, the settlement model, the scenario map, and one specialist domain without forcing a first-time reader through every appendix.
The long path is different. Start with Corpus-Terminology-Reference.md to stabilize terms, read Main-Whitepaper.md for core settlement, then read the object-boundary cluster, privacy and OnionNet, cross-chain and legal, tokenomics and DAO, PoUW, PQ migration, and only then the use-case families. That order keeps writers from producing pages that sound persuasive but cite the wrong source. It also prevents companion papers from being flattened into equal authority. A governance paragraph belongs to DAO.md; a token-supply paragraph belongs to Tokenomics.md; a private transport paragraph belongs to OnionNet.md and the privacy threat model together.
Docs Dependency Rule
Every docs page that cites a whitepaper should use it for the exact claim it owns. Protocol pages depend on the main paper and the relevant specialist paper. Use-case pages depend on UseCases.md plus a scenario-specific companion paper. Legal pages depend on Legal-Architecture.md and must not borrow stronger language from marketing or old drafts. Developer pages may cite whitepapers for concepts, but implementation claims still require live code anchors, tests, or deterministic local simulation evidence. If the docs layer cannot prove which paper owns a sentence, the sentence should be rewritten until the authority is clear.
Read Next
Read Source Authority Map before resolving cross-paper conflicts, Technical Papers for grouped companion-paper routes, and Archive when older material appears to contradict the current corpus.
Evidence and Further Reading
- Full corpus source list with section-specific authority:
Agentic-Offline-Economy.md,Assets-Rights-Vauchers.md,Corpus-Terminology-Reference.md,Cross-Chain-Integration.md,DAO.md,Legal-Architecture.md,Linked-Liability.md,Main-Whitepaper.md,OnionNet.md,Post-Quantum-Migration.md,Privacy-Threat-Model.md,Proof-of-Useful-Work.md,Smart-Cash.md,Tokenomics.md,Uniqueness.md,UseCases.md, and Whitepapers Home. - Main Whitepaper sections 1-12 are the primary source for present-tense protocol contracts, settlement boundaries, and implementation-status language.
- Use Cases Whitepaper sections 2-10 are the source for the six-family ordering and for maturity discipline across scenario pages.
- Corpus Terminology And Abbreviations Reference sections 3-9 are the authority for terms such as
AssetLeaf,RightLeaf,SettlementPath,FeeEnvelope, andRewardAuthorization. - Privacy Threat Model And Metrics sections 3-10, Linked Liability Whitepaper sections 3-7, and Cross-Chain Integration Whitepaper sections 3-8 are the main companion anchors to consult before making privacy, fraud-accountability, or external-custody claims.