> 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/what-do-the-likelihood-ratings-mean-and-how-should-we-interpret-them.md).

# What do the “likelihood” ratings mean and how should we interpret them?

Each project record is assigned one of three likelihood ratings - High, Medium or Low, based on its maturity, visibility and risk profile. A “High” rating indicates that land control is secured, permitting is advanced or approved, utility/infrastructure access is confirmed (power, water, transport), financing or government incentives are committed, and the developer has relevant experience. “Medium” signals that there is progress but more uncertainty remains, such as pending land acquisitions, early-stage permits, or unconfirmed infrastructure access. “Low” means substantial uncertainty exists: perhaps land or zoning is unresolved, infrastructure access is unclear, financing or partner commitments are missing or the developer lacks a proven track record. These ratings allow users to filter or weight the dataset by execution risk rather than taking all announcements as equally likely.


---

# 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/what-do-the-likelihood-ratings-mean-and-how-should-we-interpret-them.md?ask=<question>&goal=<user_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.
