> For the complete documentation index, see [llms.txt](https://vigil-1.gitbook.io/vigil-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vigil-1.gitbook.io/vigil-docs/community-and-links/beta-disclaimer.md). # Beta Disclaimer Read this before using Vigil with real funds. Vigil is Closed Beta software. It may contain bugs, behave unexpectedly, or be unavailable at times. ## Trading risk Trading digital assets carries a high level of risk. You can lose some or all of your funds. * Only trade with money you can afford to lose. * Start small while you learn how Vigil reads your plans. * Don't assume any system, including Vigil, will protect you from losses. ## Vigil is not financial advice Nothing in Vigil, this documentation, the Vigil website, or any message from the Vigil team is financial, investment, legal or tax advice. Vigil is a software tool that carries out plans **you** write and approve. The decisions, the trades and the outcomes are yours. We are not a registered financial advisor, broker, dealer or fiduciary. We don't manage your money, and we don't recommend what to trade. If you need financial advice, talk to a qualified professional where you live. ## Automation risk Automated trading can fail because of fast markets, low liquidity, slippage, network congestion, exchange outages or software errors. Watches check on a cadence, not tick by tick, so a fast move can be missed. ## Token risk The Vigil token is planned, not live. When it launches: * It is a way to pay for access to Vigil, not an investment product. * Its price can go up or down, and it can lose value. Burning tokens does not guarantee any price. * Token plans, including supply, the burn split and launch timing, may change before launch. * Rules on digital tokens differ by country. Check that you're allowed to hold and use it where you live. ## Your responsibility By using Vigil, you confirm that: * You're legally allowed to use the markets you connect, where you live * You understand that all trading decisions and results are your responsibility * You won't hold Vigil or its team liable for trading losses, missed opportunities, bugs or other results of using the product * You're joining the Closed Beta by choice and at your own risk ## Reporting problems If anything looks wrong, report it right away through [Feedback and Support](/vigil-docs/closed-beta-guide/feedback-and-support.md). Fast reports help protect every Beta user. --- # 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://vigil-1.gitbook.io/vigil-docs/community-and-links/beta-disclaimer.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.