> For the complete documentation index, see [llms.txt](https://greenstarresources.gbca.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/green-star-buildings/v1.1/mandatory-requirements/climate-positive-pathway.md).

# Climate Positive Pathway

The Climate Positive Pathway is a select group of credits in the Positive category designed to drive carbon reduction which must be met to achieve a Green Star rating. It consists of Minimum Expectations and credit criteria that progressively increase in stringency based on project's registration date and targeted Green Star rating.

The following table outlines the Climate Positive Pathway criteria that must be achieved for each star rating based on the registration date. The year refers to 1 January of that year and indicates when the corresponding set of requirements begin. ME denotes Minimum Expectation, CA denotes Credit Achievement, EP denotes Exceptional Performance and LC denotes Leadership Challenge.

Some credits in the Climate Positive Pathway and Nature Positive Pathway have stepped points. However, to meet the Pathways, all points in the nominated performance level must be achieved (i.e. in Credit Achievement for the Energy Use credit, there are stepped points available for reductions between 10 to 20% however 5 star projects meeting the 2025 requirements must achieve a 20% reduction to comply with the Climate Positive Pathway).

<figure><img src="https://749968417-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FRL05MQuVhZhkDMQBuGrI%2Fuploads%2FPAyHdWI3fsjyvuIvNNem%2Fv1.1%20CPP.png?alt=media&amp;token=fcd8e80f-bb8b-49b1-8fed-3b13316435ac" alt=""><figcaption></figcaption></figure>


---

# 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://greenstarresources.gbca.au/greenstarresources.gbca.au_ratingtools/current-green-star-rating-tools/green-star-buildings/v1.1/mandatory-requirements/climate-positive-pathway.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.
