> For the complete documentation index, see [llms.txt](https://sacred.gitbook.io/sacred-finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sacred.gitbook.io/sacred-finance/what-is-sacred/roadmap-1.md). # Roadmap Growing the Sacred Community * Feedback Program * Launch Early Contributors Program * Grow the Sacred Team Polygon Testnet Launch * Testing Phase * Aave integrated Sacred launch * Halborn Smart Contract Audit Token Generation Event (More information coming!) * Liquidity Mining * Bonding Sacred DAO launch * Commonwealth Launch * Find DeFi partners (Yield aggregator/Optimizers, Staking platform, etc.) * Build out onboarding process & proposal mechanisms for DAO Polygon V1 Mainnet Launch * Sacred Ceremony (Public Trusted Set up Ceremony) * Incognito Mining Begins * Upgrade UX/UI designs * Develop partnerships in Polygon & Privacy Ecosystems ​ Multi-chain + More features * Onchain Claim Storage * More DeFi integrations - Yield Aggregators, Yield Optimizers, Staking, and more! --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sacred.gitbook.io/sacred-finance/what-is-sacred/roadmap-1.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.