> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund10-docs/project-onboarding/f10-milestone-reviewers-guide/what-is-not-good-evidence.md). # What is not good evidence? ## General rules * The information provided does not clearly show that the milestone has been accomplished. * The links submitted do not work, so the project's evidence cannot be effectively verified. * For E.g., Git repo is publicly accessible, which will allow for review * The evidence submitted is not in line with the Ideascale proposal * The evidence contains project description only, without any progress * Evidence is in a different language than English ## Specific evidence ### If image/video is evidence: * Quality is poor - unable to watch/see * Lack of description ### If code is evidence: * It isn’t in the Git repository * Activity in Github doesn’t match what is stated in the milestone ### If presentation/slide is evidence: * There is only a project description, no track of any progression ### If a website is the evidence: * There is no clear evidence of new features/updates on the website and their description --- # 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.projectcatalyst.io/previous-funds/fund10-docs/project-onboarding/f10-milestone-reviewers-guide/what-is-not-good-evidence.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.