> For the complete documentation index, see [llms.txt](https://docs.fractalvisions.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fractalvisions.io/fveco/role-guide/integrity.md). # Integrity Follow through on your word no matter how long it takes. We have been working on the development of this project since December of 2022 which has become a full time job in order to build our platform from the ground up. The team of full stack developers are highly dedicated to the project and have done an outstanding job with the MVP. Coming into the end of 2024 with the Beta version of Fractal Visions is the forefront of our ecosystem launch. We are happy to share our ultimate vision with everyone that our team helped create. There is a lot to be said about the term "Overpromise and Under Deliver" in the world of web3 and we believe there is a delicate balance for every team that relies on funding for the continuing development of their project. It is critical not to set the bar too high for yourself or your team when it comes to milestones.\ Remember it is all about quality not quantity. Use this framework of goals to help keep yourself or your team motivated. --- # 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.fractalvisions.io/fveco/role-guide/integrity.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.