> 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/data-centers/our-modeling-approach/project-stage-definitions.md). # Project Stage Definitions A guide to how Aterio classifies data center projects across their development lifecycle. ***Announcement*** Project has been publicly announced, filed, permitted, or otherwise identified, but no construction activity has been confirmed. ***Construction*** Construction activity has been confirmed through satellite imagery, permits, filings, or public disclosures. This can include early-stage site clearing, grading, foundations, vertical construction, or equipment installation. ***Land Bank*** Land has been acquired or controlled for potential future data center development, but there are no confirmed near-term construction plans. ***Not Approved / Withdrawn*** Project has not received required approvals or has been withdrawn from the approval process by the developer. ***Cancelled*** Project has been formally cancelled by the developer or is no longer expected to move forward, even though initial groundwork or construction progressed. ***Delayed*** Project remains active but has experienced material delays relative to expected development timelines, based on construction progress, public disclosures, or other available evidence. ***Active*** Facility is operational or in final commissioning stages with critical infrastructure installed and capacity expected to be available for use. --- # 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/data-centers/our-modeling-approach/project-stage-definitions.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.