> For the complete documentation index, see [llms.txt](https://rescueloyal-io.gitbook.io/rescueloyal.io-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rescueloyal-io.gitbook.io/rescueloyal.io-docs/ecosystem-and-participation/verification-framework.md). # Verification Framework Verification standards that protect the integrity of RLY recognition. ## Verification Framework Verification confirms that RescueLoyal (`RLY`) recognition reflects eligible participation. The method must match the activity, campaign risk, and sensitivity of the evidence. ### Verification standard Each campaign publishes its verification method before participation begins. The method must be proportionate, consistent, and relevant to the stated objective. ### Evidence sources Project Rescuecoin may use registration data, partner confirmation, attendance records, or participant submissions. It requests only information necessary for the stated purpose. ### Review outcomes Verification rules apply consistently within each campaign. The project may conduct additional review where activity appears incomplete, manipulated, or ineligible. Recognition is granted only where the evidence meets the published standard. A campaign may provide further review options where operationally appropriate. ### Privacy and retention Evidence is handled under the [Privacy Notice](/rescueloyal.io-docs/legal-and-disclosures/privacy-notice.md). Campaign records are retained only for the period needed to administer the campaign and meet applicable obligations. --- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://rescueloyal-io.gitbook.io/rescueloyal.io-docs/ecosystem-and-participation/verification-framework.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 `build a script that syncs our docs to a CMS` 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.