> For the complete documentation index, see [llms.txt](https://docs.scanbylens.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scanbylens.xyz/business/token/safeguards.md). # Safeguards Conflict rules, disclosure, and what the team will never do. A desk that makes public calls and is connected to a token has obvious conflicts of interest. LensAI handles them with rules that are enforced in code where possible and published where not. ## No calls on held tokens The desk never makes a call on a token that the team, the treasury, partners, market makers or related projects hold or issue. **$LENS is first on that list.** This is enforced in the call policy: a call on a blocked asset is refused at the input, and a call whose text names one is turned into a no call. ## Disclosure Before launch, LensAI will publish: * who funds the project; * team and related-project holdings, by token; * related projects and the nature of the relationship; * a personal-trading policy for the team, with blackout periods around calls. Related projects are kept out of LensAI's own traction figures, and LensAI's data will not settle any related project's markets without a published independence policy. ## What the team will never do * Trade ahead of, or against, the desk's own calls. * Delete or quietly edit a call. * Pay or reward anyone to post about LensAI or $LENS. * Hint at exchange listings. * Use $LENS to fund the free product. * Make return claims, use profit language, or publish testimonials about the token. * Ship a package or integration that asks a user for a private key. ## Before launch * Securities counsel review of the token design and the call format. * An independent audit of the token and vesting contracts. * A trademark search and a settled ticker. * Public vesting streams and the final schedule, published before any liquidity. --- # 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.scanbylens.xyz/business/token/safeguards.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.