Version: 2026-07-09

Purpose

This document is the corpus-level terminology reference for the Z00Z paper family. It is meant to be exhaustive across the explicit terminology layers in the repository docs corpus, not merely a short shared-style guide.

For this reference, “explicit terminology layers” means:

• every ## Key Terms Used In This Paper section in docs/whitepapers/*.md;
• every ## Appendix A. Glossary section and its term tables or bullet lists;
• every appendix abbreviation or symbol table used as a terminology layer, even when it lives in Appendix B rather than Appendix A.

This reference does not try to index every type, function, or code symbol named incidentally in prose. It indexes the places where the corpus explicitly says, in effect, “these are the terms this paper defines and reuses.”

1. Coverage Boundary

The current coverage set is the full docs/whitepapers/*.md paper corpus, with Assets-Rights-Vauchers.md treated as the companion object-boundary paper:

• Main-Whitepaper.md
• Litepaper.md
• Cross-Chain-Integration.md
• Agentic-Offline-Economy.md
• UseCases.md
• Uniqueness.md
• Linked-Liability.md
• OnionNet.md
• Tokenomics.md
• DAO.md
• Proof-of-Useful-Work.md
• Legal-Architecture.md
• Z00Z-HJMT-Design.md
• Z00Z-Roadmap-Blueprint.md
• Z00Z-Multi-DA-and-Checkpoint-Architecture.md
• PQ-Migration.md
• Assets-Rights-Vauchers.md

Two papers need special handling:

• Litepaper.md does not use Appendix A as a glossary. Its Appendix A is a reading map across the corpus, so its terminology layer is front-loaded in Key Terms Used In This Paper.
• Legal-Architecture.md also does not use Appendix A as a glossary. Its appendices are claims, red-line, and documentary-control appendices, so its terminology layer is also front-loaded.

One companion paper also needs special handling:

• Assets-Rights-Vauchers.md uses Appendix A for claims/non-claims plus Appendix B for a reading map, so its terminology layer is front-loaded in Key Terms Used In This Paper.

One paper stores part of its terminology layer outside Appendix A:

• Uniqueness.md puts its main glossary in Appendix A, but its abbreviation and short-symbol tables live in Appendix B and are therefore included in this reference.

2. Corpus Coverage Map

This table shows where each paper defines its local terminology and what kind of terminology layer it uses.

3. Canonical Shared Term Contract

This section normalizes the shared terms that recur across multiple papers or act as canonical boundary nouns for one major topic area.

3.1 Core Protocol And Wallet Terms

3.2 Rights, Machine, Agent, And Service Terms

3.3 Cross-Chain And External-Asset Terms

3.4 Liability, Accountability, And Recovery Terms

3.5 Economics, Governance, Useful-Work, And Legal Terms

3.6 Network, Storage, And Roadmap Terms

4. Variant, Alias, And Casing Rules

Use the preferred forms below when the same idea appears with multiple spellings or scope levels across the corpus.

5. Master Abbreviation List

This list consolidates the explicit abbreviation and shorthand tables used across the corpus. Status indicates whether the abbreviation is a broad corpus-default shorthand or a document-local shorthand that should be introduced before use.

6. Full Document Terminology Inventory

This section is the exhaustive document-by-document index for all explicit term layers covered by this reference.

6.1 Main-Whitepaper.md

• Key Terms: AssetLeaf, RightLeaf, Checkpoint, Settlement evidence, Asynchronous rights settlement, Wallet-local possession, TxPackage, Nullifier, Soft confirmation.
• Appendix A additions: ClaimTxPackage, Canonical asset path, Claim replay record, ReceiverCard, PaymentRequest, EncPack, Tag16, LockerID, Privacy threat model.
• Authority role: canonical protocol object language and wallet-versus-public settlement boundary.

6.2 Litepaper.md

• Key Terms: AssetLeaf, TxPackage, ClaimTxPackage, Checkpoint, Wallet-local possession, Linked Liability, Locker, FeeCredit, FeeEnvelope, Agent spending envelope.
• Appendix note: Appendix A is a corpus reading map and Appendix B is a claims versus non-claims appendix, so this paper does not add a separate glossary layer beyond the front key terms.
• Authority role: short public summary and corpus entry point.

6.3 Cross-Chain-Integration.md

• Key Terms: AssetDefinition, AssetLeaf, content_id, Locker, LockerID, BridgeInTx, BridgeOutTx, Attestation, DA adapter, Service layer.
• Appendix A additions: Wallet-local possession, Checkpoint, Settlement evidence, TxPackage, ClaimTxPackage, Nullifier, Claim replay record, Soft confirmation, Checkpoint artifact, deposit_id or external event ID, Release condition, Adapter route, Externally backed asset, Stable asset right, Issuer-native asset, Synthetic internal unit, Trust tier, Monitoring surface.
• Authority role: cross-chain, locker, and protocol-versus-service split.

6.4 Agentic-Offline-Economy.md

• Key Terms: Spendable right, Spendable capability object, MachineCapabilityObject, Agent spending envelope, FeeEnvelope, Offline receipt, Selective audit, Checkpointed reconciliation, Rights wallet.
• Appendix A core-protocol additions: AssetLeaf, RightLeaf, Checkpoint, Settlement evidence, Wallet-local possession, TxPackage, Nullifier, Soft confirmation.
• Appendix A machine-and-agent additions: Selective audit package, Task escrow, Payout claim, Reputation bond, Proof of agent work, EnergyCredit, RouteAccessRight, DataRelayCredit, LocalComputeCredit, EmergencyResourceRight, FeeCredit, ToolCredit, ComputeCredit, DataAccessRight.
• Authority role: rights-first machine and agent economy language, plus the canonical FeeEnvelope boundary.

6.5 UseCases.md

• Key Terms: AssetLeaf, Cash policy, External asset right, Offline check, Selective disclosure, Settlement evidence, TxPackage, Spendable capability object.
• Appendix A.1 abbreviations: B2B, IOU, UBI, VM.
• Appendix A.2 additions: Offline-first private cash, Asynchronous rights settlement, Private right over an external asset, Maturity tier.
• Authority role: use-case family taxonomy and the broader Spendable capability object framing.

6.6 Uniqueness.md

• Key Terms: Agent Spending Envelope, Anonymous Trust Score, Checkpoint settlement evidence, Emergency Resource Right, External asset right, FeeEnvelope, Liability domain, Linked Liability, Spendable Capability Object (SCO), Wallet-local possession.
• Appendix A glossary restates and stabilizes the same family around uniqueness and category-boundary language.
• Appendix B.1 abbreviations: AA, ATS, CCTP, DA, EAS, ERR, EVM, FE, LL, PoUW, SCO, UBI.
• Appendix B.2 short-symbol additions: rights-first model, public-account model, wallet-local.
• Authority role: category-boundary language and uniqueness framing for the rights-first model.

6.7 Linked-Liability.md

• Key Terms: LiabilityDomain, HiddenLiabilityCommitment, FraudProof, BondRef, PenaltyPolicy, LockRegistry, Selective Reveal, Exculpability, Future Rights Freeze, Victim Compensation.
• Appendix A.1 liability terms restate and stabilize the same family.
• Appendix A.2 reputation extension terms: Anonymous Trust Score, Private reputation receipt, Trust tier proof.
• Appendix A.3 symbols: R, LID, C_L, B_ref, P_pol, S_1, S_2, FP, LR, U_proof.
• Authority role: fraud, freeze, slashing, lock, and compensation semantics.

6.8 OnionNet.md

• Key Terms: Public membership registry, Eligible set, Active set, Lane contract, Compatibility generation, Client-owned route construction, Bounded topology disclosure, Route witness, Epoch witness bundle, Adjacency ticket, Contact capsule, Double-envelope packet, Ingress decryptor, Replay ledger, Shadow traffic, Privacy floor, Break-glass authority.
• Appendix A abbreviation and term additions: AAD, AEAD, ASN, Bucket, DA, Epoch view, Ingress recipient key, PMTU, QUIC, SDK, Shadow-only handling, STF, Thin lane, TLS.
• Authority role: route, lane, ingress, privacy-floor, and metadata-hardening vocabulary.

6.9 Tokenomics.md

• Key Terms: Z00Z, FeeCredit, Bootstrap Reserve, Protocol Treasury, Stewardship Endowment, Operator Bond, Liability Bond, Accepted Reserve Basket, Launch Capsule, PoUW.
• Appendix A.1 native-asset additions: fee lane, Reserve Sink.
• Appendix A.2 treasury additions: Spend caps, Challenge Window, Emergency Override, Prohibited Treasury Uses.
• Appendix A.3 incentive additions: Security Tier, Stage Labels.
• Authority role: native asset, treasury constitution, fee lane, and operator bond vocabulary.

6.10 DAO.md

• Key Terms: Constitutional proposal, Policy proposal, Operational proposal, Signaling vote, Rated signaling vote, Rule-bound treasury, Challenge window, Proof of Non-Control, Technical impossibility, Do-not-operate zone, AI reviewer, Model registry, Private reward claim, Attestation lane, Compliance-profile wallet.
• Appendix A.1 governance additions: Signaling proposal, Delegation, Quorum, Veto path, Timelock.
• Appendix A.2 AI-DAO additions: Evidence agent, Valuation agent, Evaluation lane, Rating lane, Routing lane, Execution lane, Evaluation right, Transfer right.
• Authority role: governance-lane, evaluator-registry, and treasury-control vocabulary.

6.11 Proof-of-Useful-Work.md

• Key Terms: Proof-of-Useful-Work (PoUW), Useful outcome, WorkPackage, WorkReceipt, RewardAuthorization, Private reward claim, ClaimNullifier, Challenge window, Negative value, Rule-bound treasury, Steward, Optional ecosystem coordination layer.
• Appendix A.1 abbreviations: PoUW, KPI, SLA, N-of-M, EAS, RLN, NMT, SMT, VRF, SPV, CPA, CPM, DA.
• Appendix A.2 additions: pre-scoped grant, open useful work, fact consensus, value consensus, selective disclosure, Evidence Package, Corporate Archive, Passport gate, RLN or Semaphore rate limit, Ack note, retro-microgrant, Growth Oracle.
• Authority role: useful-work, challengeable evaluation, and review-to-payout vocabulary.

6.12 Legal-Architecture.md

• Key Terms: Neutral protocol, Steward, Rule-bound treasury, Technical impossibility, Proof of Non-Control, Independent issuer, Compliance-profile wallet, Evidence Package, Corporate Archive, Bad-use isolation.
• Appendix note: Appendix A-C are Claims Matrix, Red-Line Checklist, and Required Governance And Legal Documents, not local glossary appendices.
• Authority role: legal boundary formulas, neutral-protocol posture, and non-control language.

6.13 Z00Z-HJMT-Design.md

• Key Terms: AssetLeaf, RightLeaf, SettlementPath, AssetPath, AssetStateRoot, SettlementStateRoot, Definition, Serial bucket, Fixed bucket, Bucketed root-chained JMT forest, Parent root leaf, Path index, Forest commit journal, Proof envelope, FeeEnvelope, Compatibility backend.
• Appendix A additions: Asset JMT, AssetPathProof, asset_id, backend_root, Bucket JMT, bucket_bits, bucket_hash_domain, bucket_id, bucket_id_width, bucket_policy_id, Bucket policy, BucketRootLeaf, Canonical encoding, CheckRoot, Checkpoint evidence, ChildrenCommitted, Child root, Commit digest, Compatibility generation, Definition JMT, DefinitionRootLeaf, Deletion proof, Fail closed, Forest backend, ForestCommitJournalEntry, Golden test, Inclusion proof, Journal status, leaf_count, max_target_leaf_count, min_bucket_count, Non-existence proof, Parent root, ParentsCommitted, PathIndexRec, Physical root, Prepared, ProofBlob, Proof family, Root binding, RootPublished, Semantic root, Spendable capability object, serial_id, Serial JMT, SerialRootLeaf, Agent spending envelope, Target forest.
• Authority role: storage, root, path, bucket, and proof-contract vocabulary.

6.14 Z00Z-Roadmap-Blueprint.md

• Key Terms: Live core contract, In-progress subsystem, Reserved boundary, Workstream, Planning record, Maturity gate, Authority plane.
• Appendix A.1 maturity additions restate the same family with examples.
• Appendix A.2 core object and service additions: TxPackage, ClaimTxPackage, ClaimNullifier, CheckpointExecInput, CheckpointArtifact, CheckpointLink, SettlementTheorem, OwnedAssetPayload, recv_range(...), StealthOutputScanner, WorkItem, PublicationRequest, PublishedBatch, SoftConfirmation, Verdict, ObservationSnapshot, DaAdapter, NodeMode.
• Authority role: maturity labels, sequencing, and workstream dependency vocabulary.

6.15 Z00Z-Multi-DA-and-Checkpoint-Architecture.md

• Key Terms: Checkpoint, DA commitment, Anchor, ZTS, Anchor calendar, Meta-anchor.
• Appendix A additions: Checkpoint anchor, DA provider path, Provider receipt, Watcher evidence, Recovery record, ZTS batch, ZTS proof, External meta-anchor, Audit receipt, Disclosure package, SettlementTheorem.
• Authority role: checkpoint, DA, timestamp, audit-receipt, and external-witness vocabulary without moving settlement authority outside the checkpoint theorem.

6.16 PQ-Migration.md

• Key Terms: PQ-friendly boundary, Legacy lane, Migration lane, Hybrid suite, Integrity firewall, Rewrap, Confidential amount frontier.
• Appendix A additions: Active authorization failure, Amount integrity failure, Cryptographic suite identity, ECC, Fixed-denomination lane, KEM, Legacy cutoff, ML-DSA, ML-KEM, Passive harvest-now-decryption-later, SLH-DSA, Suite registry, Transcript binding.
• Authority role: post-quantum migration and crypto-agility vocabulary while preserving the non-claim that current transaction cryptography is not end-to-end post-quantum secure.

6.17 Assets-Rights-Vauchers.md

• Key Terms: Asset, Voucher, Right, CashPolicy, VoucherPolicy, RightPolicy, ActionPool, FeeEnvelope, Fully backed voucher, Checkpoint, Settlement evidence, Soft confirmation, SettlementStateRoot, SettlementPath, Typed Object View.
• Appendix handling: no glossary appendix; Appendix A is claims/non-claims and Appendix B is a corpus reading map.
• Authority role: final value versus conditional value versus authority split; voucher trust tiers; typed object tree boundary framed under the live SettlementStateRoot / SettlementPath HJMT contract; explicit wallet -> aggregator -> validator -> watcher role path for object transitions; separate fee-support boundary and per-object storage split.

7. Glossary And Appendix Convention

Use the following corpus conventions when editing or adding long-form docs:

• Keep ## Key Terms Used In This Paper near the front of a long-form paper.
• Prefer ## Appendix A. Glossary when the document uses Appendix A as a term appendix.
• If Appendix A is reserved for a different function, the front matter should say so clearly and should point readers to this corpus reference or to a reading map.
• If a paper needs an abbreviation table for real reader navigation, placing it in Appendix A is preferred, but Appendix B is acceptable if Appendix A is already serving a glossary role.
• Companion papers outside the Z00Z-* filename pattern may still join the corpus authority set when they define stable shared vocabulary and follow the same terminology-layer discipline.
• Document-local shorthands such as FE, LL, or SCO should never be assumed to be corpus-default shorthand unless another paper reintroduces them.
• When a concept has both a live-core noun and a future-architecture noun, prefer the live-core noun unless the paper is explicitly discussing target architecture.

8. Cross-Paper Authority Map

Use this map when a wording dispute exists between two papers or when a new document needs to know where to inherit its shared definitions from.

Figure 8.1 - Corpus authority landscape. The terminology reference is the reader-facing vocabulary guardrail, while authority over each concept family still lives in the paper that owns that domain boundary.

9. Editorial Guardrails

When two phrasings sound close, prefer the one that preserves the corpus boundary more honestly and more narrowly.

• Prefer asset-centric live core over language that implies the generalized rights runtime has already landed.
• Prefer independent issuer, external integrator, and reference wallet over language that implies project-sponsored market or service operation.
• Prefer privacy-preserving, limited public observability, and optional disclosure over absolutist claims such as untraceable or regulation-proof.
• Prefer checkpointed settlement evidence and wallet-local possession over vague claims that “everything important is off-chain.”
• Keep the boundary between the right itself and the fee path explicit: FeeEnvelope and FeeCredit are support surfaces, not silent expansions of the right object itself.

Appendix A. Research-Derived Term Additions

These terms translate selected research ideas into the Z00Z corpus. They are not automatically live APIs. A term becomes code-backed only when a later spec, implementation, and roadmap maturity gate promote it.