> For the complete documentation index, see [llms.txt](https://docs.hoard.world/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hoard.world/what-it-will-become/roadmap.md). # Roadmap Three phases: the collectible economy, credit, and the East District. One product in the interface, delivered in three phases. ## Phase 1: the collectible economy * Fixed-supply HOARD launch, 2,222 units. * Hoardlings as DN404 mirror NFTs, with deterministic art. * The Nest and the Stock Vault's reward accounting. * The canonical Uniswap v4 pool with the 3% hook. * The moving USDG Wall with permissionless rebalancing. * The seed liquidity lock and the team vesting, verifiable on-chain. ## Phase 2: credit * The HOARD/USDG oracle with live observation history. * Independent USDG lender capital in the single capped pool. * The Loan Controller with controller-owned borrower accounts. * 45% borrowing on any HOARD; 65% with a bound Hoardling. * The fee-exempt liquidation router and live keeper runs. * Conservative caps that widen only with demonstrated liquidity. Credit opens once the oracle has history, the liquidation route has run against real conditions, and the pool has depth a liquidation can clear through. ## Phase 3: the East District * The Hatchery (built; opens on deployment): Pons launches from the Hoard World UI in one transaction, the creator's opening buy locked by market cap or by time, a $20 launch fee to the Stock Vault, a card to share — see [The Hatchery](/the-world/the-hatchery.md). * Seer's Tent and the Arena: a partner's options and perpetual markets, builder fees to the Stock Vault. * Each opens once its fee route into the Stock Vault is live and accounted like the 3% fee. ## Where things stand Addresses are published on the [Addresses](/protocol/addresses.md) page as each piece goes live. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hoard.world/what-it-will-become/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.