> For the complete documentation index, see [llms.txt](https://knowledge.aterio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.aterio.io/data-products/new-industrial-developments/faqs/how-up-to-date-is-the-dataset-and-how-are-changes-or-cancellations-handled.md). # How up-to-date is the dataset, and how are changes or cancellations handled? The dataset is continuously updated as new announcements, permit filings, imagery and utility/infrastructure data become available. Each record includes timestamps for key milestones (announcement date, construction start date, estimated activation date, etc.) and discretionary fields for cancellation/withdrawal dates where applicable. If a project is formally cancelled or withdrawn, the dataset records the withdrawal date to distinguish it from projects still in play. Because the dataset relies on public and observable sources, each record is refreshed as soon as verified information surfaces. --- # 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://knowledge.aterio.io/data-products/new-industrial-developments/faqs/how-up-to-date-is-the-dataset-and-how-are-changes-or-cancellations-handled.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.