> For the complete documentation index, see [llms.txt](https://methodologies.nature-value.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://methodologies.nature-value.org/readme/6-quantification/3-projectscenario.md).

# 6.3 Project Scenario

The project scenario describes the stock management practised with the project. This is in contrast to the reference scenario. Recognised models of stock management in managed forests are applied. This may include scientifically derived growth models (yield tables), recognised framework values for stock management in the mountains or other recognised models, e.g. from the area of close-to-nature forest management. In the case of yield tables, striving for the normal stock is the baseline. Only stocks above the normal stock are creditable. The normal stock is the "lower model value" of the creditable stock. With stocks above the normal stock, the risk of calamities (e.g., storm damage) increases. Stocks up to 20% above the normal stock are considered unproblematic ("upper model value") and can be credited for stock build-up and stock maintenance. In situations that are obviously low risk, higher upper model values and thus higher stocks can be credited. Stock management and stock increase above the upper model value cannot be credited due to the risk of loss.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://methodologies.nature-value.org/readme/6-quantification/3-projectscenario.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.