> For the complete documentation index, see [llms.txt](https://docs.cryptolegacy.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptolegacy.app/detailed-flows/cryptolegacy-example-flow-overview.md). # CryptoLegacy Example Flow Overview This section provides detailed example scenarios for using the CryptoLegacy contract. All parameters - such as the number of beneficiaries, guardians, recovery addresses, approval thresholds, delays, and distribution periods - are for illustration purposes only. You can adjust these settings based on your preferences, requirements, or desired security level. These examples illustrate how to: • Set up beneficiaries and securely encrypt their data. • Assign guardians and manage emergency approvals. • Use recovery addresses for additional security. • Trigger asset distributions securely and predictably. Feel free to customize the parameters to suit your specific needs. --- # 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://docs.cryptolegacy.app/detailed-flows/cryptolegacy-example-flow-overview.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.